Hi,
is gpu encoding for screen and camera sharing in the scope of screen sharing? It is very cpu intensive and would be useful. ![]()
Hi,
in the past, me and a friend of mine decided to test and experiment with the WebRTC protocol.
We belive in fact that they are basically doing the same thing as us, but instead of relying on a server to connect multiple people, they are making P2P connections between clients.
After some experimenting, we found out (and this is more of a suggestion/input to the dev team) that changing the codecs parameters to:
mimeType: "video/H264",
parameters: {
"profile-level-id": "42001f"
}
since the profile level id 42001f is the one that we observed, made best use of GPU encoding.
Without GPU Encoding and Server Sharing (instead of P2P) the new feature is absolutely useless in my opinion.
-Who wants CPU Usage of 40% during gaming when screen share is active?
-Why should I pay for a community Server when I can only use P2P Screen Share? I have 40mbit upload. This is not enough to send a good quality stream to more than 3 users without getting packet loss ingame.
-Why is it not possible to choose the codec (Av1, HVEC, H264)?
If they can fix these things, we will switch back from Discord to TS!
Itās only in Beta so chill you will have to wait till its added.
There will be more releases in the near Future.
I am totally relaxed. But it is unecessary to find these things out on myself. I miss some clear communication.
These are the goals for the upcoming updates. Take a look here:
Thanks. I haven“t seen this post!
So after a couple of days of using the screensharing and camera features, Iāve started to notice that while doing anything like playing a game or working in production software or even just watching YouTube, it makes you realize how bad the performance of this update is. I hadnāt checked Task Manager until I started to notice it lagging very badly. While having my friends camera pulled up, it used nearly 7% of my CPU just for that. When I had my camera on and started screensharing FL Studio, Teamspeak was using 30% of my CPU. This is awful. The more people you have connected the worse it gets as well. In no world should doing these tasks result in this kind of performance.
When testing the exact same thing on Discord, my usage was around 3-5% total with the exact same scenario. Iāll be honest, this either needs to get fixed immediately or I will never be using this feature on TS.Something is very badly wrong. If others can perform some of the same tests and let me know, I would love to hear. My friend was also experiencing the same lag that I was as well.
CPU - Ryzen 7 7700X
GPU - 4070 Ti
32 GB Ram
Hello!
Iāve been streaming quiet a lot on TeamSpeak 6, me and my friend are watching football matches and I get warning that FPS are not that high as it set target (60 FPS).
My PC specs:
- AMD Ryzen 5900X
- Nvdia RTX 3060
- 32GB RAM
- Internet connection: 500/500 Mbit/s
Load while Iām streaming:
- CPU: between 15-25 %
- GPU: 25-30 %
I tried different variations:
- Full HD, 8000 bitrate, 60 FPS
- Source (2K), 10.000 bitrate, 60 FPS
FPS are never 60, always between 28-36. My friend has also good PC and optic fibre, so internet is not an issue. Is this problem related because of P2P sharing, or is it hardware acceleration issue? Iām streaming football match (my providerās online TV stream).
I hope that I provided enough information.
Thx!
People still cant connect to my stream
But i connected to friends and they had fps drops and they felt performance issues ![]()
Thanks for the provided information. We are aware of performance issues, primarily due to the lack of hardware encoding. But also the P2P connection is putting strain on your computer.
Like already mentioned in the feedback thread we are working towards improving the overall screen share experience.
Thanks, just wanted to give feedback, so that you can forward to the right department. Thatās why I gave all specs, because I think my specs are good enough to deliver max. FPS.
Hello,
a friend wanted to stream via P2P TS6 for two people but the moment he activated the stream his own ingame FPS suddenly dropped to around 30-35 fps down from 60 fps.
He got a 7800x3d and a 4090 so hardware shouldnāt be any problem. Discord streaming doesnāt cause any issues.
His ingame resolution was 4k and he was streaming to 1080p 10mbit upload per Client. He has a big enough Internet connection also.
When he set his ingame resolution to 1080p then he had 60fps ingame. But without streaming he would have 60 fps with 4k ingame resolution so that canāt be the problem.
Maybe it has to do with scaling down from 4k to 1080p? We will try to test 4k to 4k streaming later if that also decreases fps.
Thanks
Teamspeak screenshare doesnāt has hardware acceleration atm, thats the reason
Similar topic to this: TeamSpeak 6 screenshare performance
As @ImScheinox said, itās hardware acceleration issue probably. When we will get hardware acceleration and server sided screenshare I think itās gonna work really good.
A small feedback to dev team.
I streamed football again and I realized that I have FPS issues when I stream application (Chrome).
If I choose āscreen 0ā, source (2K), 60 FPS, 10K bitrate, I have much less FPS / resolution drops.
The TS6 screenshare footprint is HUGE! With a webcam feed and game feed running at 480p and 720p with conservative bitrates I have seen it use up to 10% ~ 30% CPU utilization on a 13th Gen Intel i7-13700K.
I think that the TeamSpeak demographic is going to be using this on computers that have access to GPUs and there NEEDS to be a hardware encode/decode options. Itās so intense I can FEEL the difference in performance when screen sharing. While yes, itās cool and exciting that this is coming - at the moment itās unusable.
when i stop screen sharing my desktop my gpu utilization drops from 20% to 10% instead of going back down to .1% like when i first start the app
Are you still watching a stream?
As already mentioned in some of the announcement posts:
We are making great progress in therms of full hardware acceleration and once that is released, please retest and let me know if the issue persists.

