We have identified critical audio processing issues that currently prevent full migration:
The primary issue is inconsistent volume normalization. While TeamSpeak 6 includes
gain control, it fails to properly regulate audio levels in practice. When participants
speak at varying volumes, the mixing becomes unusable, high-volume speakers effectively
suppress others, making communication difficult.
The gain control feature does not effectively maintain consistent output levels across
speakers, creating an experience significantly worse than Discord’s automatic
normalization. This single audio quality issue is the main blocker preventing our squad
from fully committing to TeamSpeak 6.
Could you provide an ETA or roadmap for fixes to the gain control implementation and
overall audio processing pipeline?
Hey @LeonMarcelHD, it’s been roughly 6 months since your reply in December — any updates on this?
With 6.0.0-beta4 dropping on April 28, 2026, I was really hoping to finally see this addressed, but there’s no mention of the audio peaking / volume normalization issue in the changelog whatsoever. The problem is still very much alive and kicking — literally hurting our ears every time someone speaks after a moment of silence.
Could we get at least a small status update — is this still on the radar, is it being actively worked on, or is there a spot for it on the roadmap? Even a short “we know, it’s coming” would mean a lot at this point.
We genuinely want TeamSpeak to succeed, we’re just struggling to recommend it to others while this keeps getting skipped over.
I reviewed the internal history on this issue and found that several fixes and attempts have been made over the years to address the audio peaking problem.
That said, the issue is still happening, which we can confirm from our side as well. We have recently reopened the internal ticket so we can take another look at it, so it’s definitely still on our radar. However, I can’t provide an ETA at this time.
For future reference, the internal ticket ID is: #TS6-513
Thanks for the update @SYOX. If there’s anything affected users can provide to help with #TS6-513 — logs, recordings, hardware configs, etc. — I’d be happy to help.
