There wasn't a related change. Permissions needed to run the server never changed.
There wasn't a related change. Permissions needed to run the server never changed.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
As a person who has been involved with sound for some 35 years, I found positive as a teamspeak user that there was a codec like speex ultra wideband the quality was pure and less use of kb's than opus that everybody runs away with nowadays.
Recordings made with ultra speex wideband and analyzed in various programs showed that the bandwidth in terms of sound is better and over a wider frequency range than that entire opus codec. Apparently, people who write the codecs for the teamspeak project are just creators than analysts, otherwise one would not make the decision in the future version project to get speex out of it.
What I and more have against me at discord is that the sound quality is not good, and that is precisely what you want to follow now.
I predict that this will drastically reduce the use of Teamspeak.
Consider again and analyze the audio really well, I think you will come back to get the codec ultra speex wideband from future versions.
Thank you for the feedback. I will share that one with our audio specialist.
------------------------
For us there is a big difference between both codecs and Opus wins.
Even their own Team wrote "Opus is better than Speex in all aspects, users are encouraged to switch".
You said Speex has a wider frequency range? Speex has a range from 8 - 32kHz while Opus supports up to 48 kHz.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
Just tested both for 5 min on my server and the Opus sound clearly better. Especially with "O"-tones/sounds like a long "Hellooooo". Guess it has something to do with limited frequency range.
And that was only the speex-ultrawideband codec. The other two are even worse because of more narrow ranges.
I see zero reasons to go back to that. Especially if there is a superior codec out for free.
And any argument along the lines of "but it sounds only 5% more crappy and instead will use 20% less bandwidth" is bullshit nowadays. Bandwidth in that single digit kbps range is completely negligible. Especially for online gamers that need a good connections anyways.
Hi,
i want to update my server to the latest version.
I saw this in the changelog:
Changed: Updated default license to be valid until the 31st of January 2020.
What does that mean?
I'm a little bit concerned that this will affect my NPL license.
Updated default license to be valid until the 31st of January 2020. - That means free 32 slots license will be not available anymore in 31st of January 2020.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
Yes. But I'm sure in 2019 this server version is no longer supported because a new version was released already and the date for the default license was updated again.
The default license is used in the server when no other license was added.
It's limits are 32 slots on one server and does not allow any commercial use (afaik).
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
any ideea?Code:terminating with uncaught exception of type boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::system::system_error> >: set_option: Bad file descriptor ts3server has crashed. A crashdump has been generated at "/opt/sell/teamspeak20870/crashdumps/ts3server_3_7_0_linux_amd64_43eb-389c-99df-401f.dmp" Aborted
Hello,
since we updated to 3.7.0 we have the problem, that we have some laggs and a very high cpu usage if 80 players switch the channel on the same time (which happens every 4 hours because or our gameserver). With 3.6.x and lower it was totally fine.
Do you need any logs?
Last edited by dante696; April 21st, 2019 at 10:35 AM. Reason: merged
Hi,
I'm running TeamSpeak server in version 3.7.1 on Ubuntu 16.04. It just crashed with following messages:
I'm not sure what caused the crash. If it helps I can provided the logged memory map and/or the crash dump.Code:teamspeak[565]: *** Error in `./ts3server': double free or corruption (out): 0x00007f3c000110e0 *** teamspeak[565]: ======= Backtrace: ========= teamspeak[565]: /lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f3c38d7b7e5] teamspeak[565]: /lib/x86_64-linux-gnu/libc.so.6(+0x8037a)[0x7f3c38d8437a] teamspeak[565]: /lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f3c38d8853c] teamspeak[565]: /lib/x86_64-linux-gnu/libc.so.6(fclose+0x103)[0x7f3c38d71363] teamspeak[565]: ./ts3server[0x41259f] teamspeak[565]: ./ts3server[0x8a32eb] teamspeak[565]: ./ts3server[0x5b9a8d] teamspeak[565]: ./ts3server[0x5bd349] teamspeak[565]: ./ts3server[0x4a1944] teamspeak[565]: ./ts3server[0x4a1424] teamspeak[565]: ./ts3server[0x5baf92] teamspeak[565]: /lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x7f3c390d56ba] teamspeak[565]: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f3c38e0b41d]
Last edited by dante696; April 23rd, 2019 at 08:57 AM. Reason: merged
We need your crash dump or else we see nothing.
Yes the server 3.7.x will use more CPU when you interact with clients. That's intended but shouldn't be so high that server becomes unusable.
What we need is a comparison / measurement from older version on your machine compared to the new version.
We need your crash dump or else we see nothing.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
There are currently 1 users browsing this thread. (0 members and 1 guests)