Apologies for reviving the thread, I have a similar problem on calls (across Zoom, Teams and Discord) on Slackware. @iamef Where you by any chance able to fix this? @feesh & @jbch Could you please point me to other resources to do this for myself? Or can you share your config/settings file for the same?
this is a tough topic in general. the short answer is: you need hardware acceleration enabled in whichever app you use for calls.
zoom (the app) should have hardware acceleration because it’s essentially something that downloads and streams videos using system libraries. this possibly applies to other non-electron apps (e.g. skype but not discord)
browser-based calls are hardware-accelerated if and only if you managed to configure hardware acceleration for your browser. firefox has a few flags you need to set (i used the arch linux guide). to test this just search for your favourite 4k video on youtube (costa rica 4k? ) and monitor intel_gpu_top and check for video activity.
similar tutorials could be used for chromium, personally i didn’t manage to do the same on chrome. potentially chromium flags could be exported to electron apps, e.g. slack or discord, but i don’t use these much for calls so i haven’t tried.
I have this enabled on Zoom, but I continue to face the problem. Without thermald installed, Zoom would take about 15% of CPU and with thermald it goes upto 25%. RAM usage is farily low at around 2%. Electron apps or otherwise seem to make no difference when it comes to issues with video calls.
I have already followed this guide and don’t have a problem with videos within Firefox.
One thing is that Intel and AMD silicon run hot when doing any kind of workload. While it is commonplace for us today, video and audio calling is CPU and GPU intensive. It does not surprise me that you are needing thermal cooling in order to keep temps down while video conferencing. I don’t believe you will see a great difference when using any other kind of video conferencing. Especially if that video conferencing is trying to use the full 1080p of the webcam.
I do hope you find some method to reach a middle ground with this though. Out of all of the OSes Linux is the most malleable in this regard, while also being, at times, the most inefficient due to poor drivers and support. (other times it is the absolute best at this.)
This is the challenge, finding the middle ground with these issues. As a person moving from a fairly stable MacOS (where I did not have these challenges while on video calls from the same software), having to tweak around to find the sweet spot is a new task. It is unsruprising that most of the times these are due to inefficient drivers/support or application incompataiblity rather than the fault of the Linux distribution (Slackware) or the laptop vendor (Framework in this case uses hardware from other folks right).
are you sure videos are HW accelerated? did you do that test? i have no heating issues with calls. if you are positive that HW acceleration is enabled and working then maybe the issue is somwhere else.
vainfo seems to suggest so, is there something I am missing? Or is there a way I can check when I am on a video call if it is enabled? Also realised most of these troubles are related to Wayland, and when I logged in with xorg, much lesser trouble for everything. I don’t know if that is related though.
on my laptop you should see the video bar jump from zero to 10% and stay there as long as the video is playing. i have experienced the video bar going up for one second and then going to zero (this means it’s not working).
if you’re using stable firefox (older than 102 i guess) you need to enable MOZ_DISABLE_RDD_SANDBOX=1 (blah blah security risk blah blah so make sure you get rid of it once you’re on 102).
Thank you for the patience, apaologies I missed out the intel_gpu_top comment. Intel_gpu_top now shows upto 10% on video and Render/3D drops down to 20-25% (from the previous 100% without the settings that I had already followed from ArchWiki). This is specifically for the costa rica 4k video you had mentioned too.
I switched to xorg from Wayland and most of these problems seems to have vanished. So I will stick to it for now, maybe check Wayland in a year or two :-). Maybe I was doing something wrong with Wayland.