Sadly it has nothing to do with the auto gain control setting, it happens regardless of whether it’s on or off.
Yes, unfortunately, I have also confirmed that this error appears in different versions of the application and with different settings.
the teamspeak 3.5.6 is 100% ok
if now a person comes to your channel and get a version above 3.5.6 so 3.6.0 or 3.6.1 or 3.6.2 blabla
than you hear the soundbug, that the user is 400% loud and comes fast back to normal. and this repeat and repeat if the user is quite and speak again 
so all users have to install 3.5.6 and than its all ok 
and dont click on update xD
greetz
edit:
https://files.teamspeak-services.com/releases/client/3.5.6/TeamSpeak3-Client-win64-3.5.6.exe
@teamspeak team - is there any update on this?
Just now, a friend sneezed while we were in a call, and even though my headset was set to under 50% volume, the sound absolutely blasted through. It was so loud it genuinely hurt my ears - this isn’t just annoying, it’s physically painful.
Please, this needs to be addressed as soon as possible. Sudden volume spikes like this are dangerous. There has to be a way to normalize or limit peak volumes. It’s insane that this can still happen.
Teamspeak 6.0.0-beta2 (1737468425) (Linux)
Bug still exists. We have people with 6.0.0-beta2 and 3.6.2 in the channel. Each and everyone sometimes has this bug appearing when he starts speaking. At one time it was so loud I had a slight ear ringing afterwards. Totally unacceptable.
We probably will roll back to 3.5.6 now together. Really bad that this bug seems to exist for years now with no fix in sight.
EDIT: Immediatly after joining the channel with 3.5.6 people even claimed that my voice was clearer and more crisp. Settings are kinda the same in both versions with a Logitech Blue Yeti.
Trying out the TS6 Server Beta with some friends and everyone hears everyone else’s audio peak at the beginning and sometimes the end when they speak. Tried changing the codec and disabling automatic gain control on the client side, but that doesn’t seem to resolve it. Am I missing something or is there a bug here?
Bug still present. Automatic gain disabled on both clients. I hear the loud start but my friend doesn’t.
6.0.0-beta5 server
1737468425 client build number
is there a difference which codec you use ? Voice or Music ?
sometimes we can fix it a bit with change codec, at our ts server.
but the version that 100% works is the “ts3 client 3.5.6”
greetz
Coming back to this thread after hearing about ts6 server since I forgot any versions newer than 3.5.6 even exist.
It is concerning that this bug still hasn’t been addressed. To be honest, no matter how well polished the new ts6 features become, if the voice chat performance has those issues there is no point in upgrading.
Is this issue still being tracked, or has it vanished into the depths?
We still have that on our list and are working on it once possible.
6 Likes
A similar issue on my end. A loud hurting sound when someone starts talking:
Example clip: https://www.youtube.com/watch?v=XL5ztiuqQBg
Edit: After switching to version 3.5.6, it’s much better/solved. My brother has switched too, but I’m not sure if it’s necessary on his end.
(Have to use my brothers account to post here, because somehow logging in my account (Laserlord) doesnt work and only results in “Critical backend Interaction Error”)
2 Likes
I’d genuinely like to see it bumped up in priority as well.
4 Likes
Just bumping this one up as well from our community’s side.
1 Like
So, We noticed a significant reduction in peaking (basically gone) if the speaker Fully disables Microphone VAD. The only issue is Teamspeaks voice settings without VAD enabled arent customizable enough to properly remove mouse click and background noise. Also with VAD disabled the speaker will constantly have there microphone light up even though they arent speaking. Can someone test this to see if its not just placebo on our end.
Any news on this issue?
We’ve seen two TeamSpeak 6 updates in December, yet there was no mention of this problem and more importantly, no fix. This is a severe issue that can be genuinely painful and potentially harmful to hearing, and it has now been reported for a very long time.
Could the TeamSpeak team please clarify the current status? Is this issue still actively being worked on? If possible, referencing an internal ticket or tracking ID would help reassure affected users.
Alternatively, if this is no longer planned to be addressed, it would be appreciated to have that stated clearly (e.g. marked as won’t fix), so communities can make informed decisions going forward.
As mentioned in previous posts, this is still on our list of things that need to be fixed. However, as mentioned a couple of times before, we simply couldn’t fix it due to the size of our team and other things that are being prioritised.
4 Likes
Thank you for the transparent update, that clarification is genuinely appreciated and reassuring. Knowing that the issue is still tracked and not forgotten helps a lot for us and the wider community.
We fully understand the realities of a small team and competing priorities from hosting services for more than a decade, that’s something many of us can relate to. At the same time, given the severity of this issue (sudden peaking, painful audio spikes, and potential hearing risk), we sincerely hope it can be prioritized when possible, as it directly affects day-to-day usability and user safety rather than just feature completeness.
Thanks for keeping us in the loop. 
1 Like
Thank you for your answer LeonMarcelHD, really.
While i can understand that a small team has to prioritize their workforce on a specific roadmap and the future of their product, but this issue exists since Teamspeak 3.6.0 and my first email from this thread is from 16.06.2023, so around 2½ years. It was introduced with a Qt Update and was migrated from the TS5 alpha/beta back then, if i remember correctly, and the only possible fix was and still is downgrading to the 3.5.6 and that is way too long. You ARE loosing users with such an annoying and severe bug still present.
And i fear, that even IF you can and will fix this, it wont reach the old core TS users anymore. Those like me and my community that don’t like or want any electron/webapp and prefer the stable TS3 server/client combo - we’re here since the first days of TS2.
2 Likes
The issue exists longer than that. I originally created a thread about this for the TS Beta Sound issues when someone starts talking (February 2022) so about 4 years now.
Why there is not the option to just fix it in TS6 so you can at least give people a solution for this?
I have the same issue only with the music codec. However, I never really considered it a problem, because when a client plays music, everything works correctly. I have the music bot in a separate channel with the music codec, and if someone wants to listen to it, they hear the bot via whisper.