TeamSpeak 6.0.0-beta3 - Foundation I Update

If I (Windows 11 AMD cpu Nvidia GPU) screenshare to a friend (intel-based mac), they don’t see anything if audio capture is enabled. Turning it off (or using webcam) works perfectly fine

client dont start anymore. delete cache.

Ryzen 5600 + RTX3080

After updating from beta2 to beta3, all contacts are archived.

My contacts can write to me but I can’t reply.

Why is this, and how can I change it back?

Delete your cache in %localappdata%/TeamSpeak/Cache/Default

3 Likes

it didn’t work

Send me a PM please

3 Likes

the DPI issue, related to change in window size has not been resolved. but gladly we can now stream with HW acceleration.

i dont get this. why dont you fix the most visible bug, it has? have you ever heard of ASD? pleople with those diagnoses might end up hospitized.

no wonder why TeamSpeak looses the ‘online communication race’. people tend not to use visually buggy and non-intuitive designs.

In the Linux version, the problem with assigning keys has not gone anywhere… I can’t assign a key to activate the microphone, and I don’t know where to go at all.

On Wayland, hotkeys behave quite differently and sometimes have to be passed through manually, like on hyprland.

We are exploring hotkey support on Wayland, but no timeline there.

4 Likes

But I can’t even specify a button to activate the microphone..

If you start the window in an x11 session, or force it to run under x11-wayland (or wayland-x11?), then global hotkeys should work again.

2 Likes

Is the no audio capture issue on Linux acknowledged ? How bad does it look ?

So is this a Wayland problem?

Yes it’s a wayland-specific issue. It’s on the roadmap and will be tackled at one point.

3 Likes

Audio capturing is not yet implemented on Linux, it’s also on our roadmap and will be tackled.

5 Likes

This is a Wayland design decision. For security reasons, Wayland does not allow applications to globally capture keyboard input, as that would enable potential keylogging.

That’s why global hotkeys or push-to-talk bindings outside the focused window are not supported by default, unless the dedicated GlobalShortcut API is properly used, which is already implemented in Chromium, KDE and Gnome.

2 Likes

it would be helpful if stuff like that was shown in app!
I spent a bit trying different workarounds to see if I might be able to get it to work

The current tooltip ‘This app does not support audio capture’ is very ambiguous and suggests that there’s something wrong with the app you’re trying to capture.

1 Like

You are absolutely right! We will do so in the next update.

8 Likes

Is there any idea why is stream way more smooth on Discord than on latest TS6 3.2 beta?

I’m streaming for example CS2, and it feels like game is freezing, I have 300 fps+ in the game. It’s pretty interesting that I feel freezing on the left monitor if I watch my own stream on the left monitor. Today we watched football match on screenshare and ball was not that smooth, like FPS are dropping - and we didn’t receive any notice that is bad stream quality.

We’re all on optic fibre, good computers. Is there any internal case on it. I can record if it would help to you.

CPU: Intel Ultra 9 285K
Memory: 64GB DDR5 6000MHz
GPU: RTX 5070 Ti
Optic fibre: 500/500 Mbit/s

Hope this gets improved, image quality is insane, only “smothness” needs to be improved.

Great update, especially on Linux!
What is the difference between the flathub https://flathub.org/en/apps/com.teamspeak.TeamSpeak version of teamspeak and the one found on TeamSpeak Downloads | TeamSpeak ?

The flathub version has a lot of issues for me, the one from teamspeak.com works great tho!