Eno represents TeamSpeak 3, while Eno1 represents TeamSpeak 5. In TeamSpeak 5, the microphone indicator remains constantly lit even when no one is speaking. When I adjust the sound card frequency to 44.1kHz, it behaves normally, but at 192kHz, the indicator remains constantly lit.
I am pretty sure the problem is not with the sample rate, but the fact that it is a virtual microphone (at least to windows). There is a bug that settings for virtual mics are not saved properly in TS5. You should be able to disable and enable VAD in the settings for it to work properly again. But you will need to do this every time you start the client.
I tried it myself, but it doesn’t work. I can’t disable VAD. When I disable it and switch tabs, then return to the audio settings, VAD is still enabled, and I can’t disable it.
Is this a unique issue with TeamSpeak 5? TS3 doesn’t have this problem.
Hi,
I’m using the 5.0.0-beta77 version and if I go to Audio settings and under the Voice Activity Detection (VAT) option I switch L Mode from Automatic to Hybrid or Volume Gate it only keeps the setting until I stay in Audio settings. If I click to another application or server it sets the L Mode back to Automatic.
Could you help me?
In the TS5 client, when used automatic VAD once, you are no longer able to switch back to Volume-Gate.
I have the same issue that I reported:
https://community.teamspeak.com/t/cant-switch-l-mode/50299
And as I see, it doesn’t save any changes in Audio Processing Settings too.
I was having this issue. I found it was an audio driver that was causing my problem.
I am also having this issue on Linux with Pipewire. Its really annoying
Every time I open team speak 5, I have to go into my settings and toggle Voice Activity Detection for it to actually properly filter my mic input. By default without doing this, even though I keep the setting turned on, my mic is completely open when I join channels. Is there a fix for this, or do I just wait for the next ts update in the next eon?
The problem is can occur when using virtual audio devices and the program changes the ID the name stays the same.
You can find a few possible solutions for this problem in this thread:
My Audio Setting do not Save
Every time i connect to a Server my Audio keeps sending even without me talking
Speech detection is on but until i retoggle it i keeps sending Audio
But it wont save the changed settings
same for me
Same Problem using TeamSpeak 6.0.0-beta2 on Windows 11 Enterprise 24H2 (26100.2894).
Same issue for mac version: 6.0.0-beta2 buildnumber: 1737468425
I also tried to reset and delete every cache & config, but no luck there
fresh install but still same problem
Version: 6.0.0-beta2
Build Number:1737468425
Chromium Version:130.0.6723.117
I had the same version since the latest TS5 beta (so 5+ months) and its sadly not fixed yet.
Version: 6.0.0-beta2
Build Number: 1737468425
Build Date: 1/21/2025, 3:07:05 PM
Chromium Version: 130.0.6723.117
OS: Latest Arch Linux KDE 6 (from AUR)
Workaround possible:
Microphone VAD settings do get saved, until you open the Settings > Audio page in TS6 again, by doing the following:
- Make sure you have the correct microphone already selected.
- Disable VAD.
- Set VAD mode to
Automaticin dropdown. - Set VAD mode to
Hybrid. - Set the desired threshold levels.
- Once done. Go to another settings page, to avoid opening Audio settings again when clicking on settings.
- The settings should now stay until the next restart, unless you open the
Audio-Settings page again.
I use TS for my work and this is the most annoying thing I’ve encountered in my two decades of using this program. If I want to talk with a co-worker I have to hot mic or use PTT. Not ideal for my situation.
When I make the change to Volume Gate it will reset as soon as I leave the tab. Nothing makes it save. I’m at a loss on what to do next with it.
MacOS 14.4.1
Macbook Pro M2
Teamspeak 5 - latest client versions, issue has been active for a while across multiple previous versions.
Hey, friend got same problem, any fix?
Are you using virtual audio devices? If so this is a common issue:
In the following post there are possible / temporary solutions to solve the issue.
There is currently no solution to this issue. It seems to happen when the virtual audio devices changes its ID but name stays the same. Sorry.
Users should be provided with an option to choose whether to include the device ID as part of new device recognition.
