-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High CPU Load When ATEM Mini Pro Is Connected #127
Comments
Nobody? Companion is eating my MacBook alive and I am the only one with that problem? |
I am running companion of Linux not Mac, but am only seeing an increase of about 2-4%. What version of companion are you running? This could be related to nrkno/sofie-atem-connection#96 |
It does run better on Linux, I can confirm that:
On Mac, I am running v2.1.2 |
I have just taken a quick look at this on an M1 mac, and looks better in the 2.2 betas. If I run up a connection outside of companion it is about ~5% cpu. I don't have any ideas right now on where the extra cpu is going, I shall pick this up another day to try and figure out why |
Thanks for being persistent with the problem! Tbh, for something like connecting to the ATEM and sending a command every once in a while, I would expect to see companion in the output of |
For what it’s worth, I’m also seeing exactly this: M1 Mac Mini running Big Sur No curious log items or unexpected behaviors — all seems to work, just with bafflingly-high CPU usage specifically related to the ATEM module being enabled. |
Apparently, smoking up a 3rd of a mac book pro isn't much of a deal for most folks here 😂 |
Same issue here, fresh install of latest companion brings 35% CPU load for companion process only. Making my fans spin like crazy if I open additional apps... Can this issue be fixed soon, please?!? MacOS BigSur 11.6 on 2020 Macbook Pro 13" |
The CPU load caused by companion is around 1-2% when there's not device connected. As soon as I add the ATEM Mini Pro, CPU load rockets to a bit above 30% and stays there forever.
I am not sure if there's a legit reason for that or it should be considered a bug.
The text was updated successfully, but these errors were encountered: