How is this not fixed for TeamSpeak 6? I had the issue on TeamSpeak 5 so went back to TS3 and now decided to try TS6 but still has this issue…back to TS3 I go.
1 Like
Today i noticed that the Problem is only there while using VoiceMetter Banana for Audio Routing
Can still confirm this for NixOS too. Even without an extra filter chain in PipeWire the problem occured to me. Only with the automatically available connected devices, without special devices like a GO XLR. Broken for NixOS package, Flatpak and the official TS6 beta download from website. The type of packaging doesn’t matter, it occurs across the board if you are affected by it.
Because nothing else helped, I also deleted the audio_settings in the ~/.config/TeamSpeak/Default/settings.db SQLite database. After switching the audio devices back and forth and changing the mode to Volume Gate for them, it eventually retained the setting.
I can only speculate, but perhaps a partial transfer of the settings from the TS5 beta was not entirely successful or because the audio devices were initially picked up via Alsa and not PulseAudio (currently using the PulseAudio bridge provided by PipeWire).
1 Like
My Problems with Teamspeak Settings not Saving are solved
Deaktivated a lot of the Inputs and Outputs of Voicemeeter Banana
It doesn’t just affect the Microsoft Store version. Teamspeak 6 is just completely bugged in regards to saving audio settings. It’ll save the audio device, but nothing else (Automatic Gain Control, VAD, Echo Cancellation, etc)
1 Like
It doesn’t just affect the Microsoft Store version. Teamspeak 6 is just completely bugged in regards to saving audio settings. It’ll save the audio device, but nothing else (Automatic Gain Control, VAD, Echo Cancellation, etc)
Actually It’s a thing only happening in the Microsoft Store version, if you install TS6 using normal installer it should save it again…
Did you not just read what I said? It affects all versions. I wouldn’t have said that if it didn’t happen. I installed via the MSI right off the website. Doesn’t save anything.
1 Like
Did you not just read what I said? It affects all versions. I wouldn’t have said that if it didn’t happen. I installed via the MSI right off the website. Doesn’t save anything.
It works for me tho…
@Shaknunic @StrikerTheHedgefox your both talking about a different issue…
Audio settings which are not saved are present on normal installed clients.
All setting don’t save were present in your MS store installation.
5 Likes
I already has posted the workaround earlier in this topic 
Second way : Can not save audio settings on audio device since b65 - #62 by W4RdZ
Admin says : Can not save audio settings on audio device since b65 - #75 by Clarkycal
Tested multiple times. Also reinstalled the application. Version 6.0.0-beta2 build 1737468425
I want to change audio capture - voice activity detection mode from automatic to hybrid. I do so in the menu. The settings apply instantly. When I then either switch the settings menu to any other settings area or just close the settings area. The settings I just changed do not apply any more and do not get saved. So I go back to audio and the settings are reset to VAD automatic. This bug applies for most audio settings.
Hello,
Just to talk about something i’ve found yesterday,
The automatic control gain can’t be set on false :
If you just go back to other menu and go back it will always set on ON
In the new "6.0.0 Beta 2 " Client i cant switch to volume gate anymore.
In the old 5 client it didnt work either but i was able to “trick” it by switching it off and on again.
Now it stands on Auto and if i want to make ANY changes it switches back to Auto.
Cant use Teamspeak anymore. for me its a “game breaking” bug that makes it unusable…
any suggestions ?
And when will there be a fix? The problem has been known for 3.5 years. It affects a core function of the software and occurs with a setup that is not unusual. It cannot and must not be the goal to offer the end user only a solution that requires tinkering with the database. Especially if you have friends who are not so tech-savvy, you don’t need to start explaining this to them. They’ll say screw it, I’ll just use something else.
This absolutely has to be fixed.
1 Like
So, I was using TS5 just fine no issues whatsoever,
but eventually, after several updates, Idk exactly when because I’ve been using Discord with some friends a lot lately, since they refuse to use TS. and when I went back to TS6
Suddenly the microphone light was constantly on and ppl said they could not hear me in TS.
I thought “ahh it’s just windows changing my settings again, i’l just check windows settings and TS settings and it’s good” but no, still the issue presist.
I ended up reinstalling TS6 without success. I opened TS3 next to TS6 and made sure the settings were exactly the same, and yet it works in TS3 but not TS6. It’s so annoying. Does anyone know what might be wrong? It’s not a super big deal as long as my TS3 works, but I kind of liked the new TeamSpeak, so I would like to get it working again.
Can you please attach a picture of all audio settings?
1 Like
One of them works, the other does not.
Also, btw, in TS6 for some reason, the volume gate setting keeps resetting by itself to automatic all the time. idk what that’s about.
and it’s strange because when I speak into the mic in the settings I can see the bar move. But when I listen to playback or try to speak to someone they can’t hear me.
I am so confused, it used to work fine in the TS5 beta.
This is a known issue we’re the settings keep resetting them self when using virtual audio devices. It may help using the default capture device instead of selecting the specific microphone.
If this still does not work, then I do not have a better solution for your right now.
I’ve brought this issue up again internally last week and hopefully we can get it fixed with an upcoming update, but at this time I can not promises that as we don’t have a 100% how-to for it, without using different audio equipment.
3 Likes
Certain audio devices have proven broken on TS6. You go to Microphone settings, do your adjustments and as soon as you leave that page and go back to it, it resets itself. When you try using it as is, the microphone stays open all the time, encoding anything including all unwanted noise.
There is not much in the log files, only that it is opening an audio device
[2025-04-11 16:45:59.027] [info] Notifications_Windows ctor
[2025-04-11 16:45:59.048] [info] TeamSpeak Client 6.0.0-beta2 (2025-01-21 14:07:05)
[2025-04-11 16:45:59.048] [info] SystemInformation: Windows 11 (26100) x64 (AMD or Intel) Binary: 64bit
[2025-04-11 16:45:59.286] [warning] calling clientlib functions on uninitialized clientLib
[2025-04-11 16:45:59.286] [warning] calling clientlib functions on uninitialized clientLib
[2025-04-11 16:45:59.286] [warning] calling clientlib functions on uninitialized clientLib
[2025-04-11 16:45:59.286] [warning] calling clientlib functions on uninitialized clientLib
[2025-04-11 16:46:01.309] [info] Initialized with 2 channels in 32bit, 48kHz. - OUT 1-2 (BEHRINGER UMC 204HD 192k)
[2025-04-11 16:46:03.379] [warning] Server at URL https://clientapi.myteamspeak.com/tschat responded: 400
[2025-04-11 16:46:03.379] [warning] failed to get allowed identifier list - connection error: 1 - All servers failed
[2025-04-11 16:46:29.044] [info] starting download for http://update.teamspeak.com/windows/x64/latest/info.json
[2025-04-11 16:46:29.543] [info] connected to push system.
[2025-04-11 16:46:53.098] [info] Initialized with 1 channels in 32bit, 48kHz. - IN 1 (BEHRINGER UMC 204HD 192k)
[2025-04-11 16:47:15.984] [info] Initialized with 1 channels in 32bit, 48kHz. - IN 1 (BEHRINGER UMC 204HD 192k)
[2025-04-11 16:50:26.675] [info] Initialized with 1 channels in 32bit, 48kHz. - IN 1 (BEHRINGER UMC 204HD 192k)
[2025-04-11 16:50:43.954] [info] Initialized with 1 channels in 32bit, 48kHz. - IN 1 (BEHRINGER UMC 204HD 192k)
[2025-04-11 16:51:02.854] [info] Initialized with 1 channels in 32bit, 48kHz. - IN 1 (BEHRINGER UMC 204HD 192k)
[2025-04-11 16:55:01.744] [info] Notifications_Windows dtor
Here’s the audio driver that’s running.
Running on
I fear this is not gonna be only instance of an audio device being incompatible with this client, but happens to be what I am using at the moment. It’s been quite a long time and I haven’t had any luck fixing it. If clean Windows install can’t fix it, I don’t know what else. I hope all nessessary information is given.
Thanks for merging! Haven’t found this until you pointed me here.
1 Like