For anyone who has experienced the same issue as above… I managed to find a work-around that is fairly solid…
To avoid almost any CPU usage no matter how heavy is your setup… ( I currently have 2 GoPros 1 MackBook Pro webcam and a full HD external cam, all running at the same time during the entire stream session and countless layers and effects including multiple external audio sources) simply minimize the application while streaming.
In my case, I do use StreamDeck which has made the process even smoother as I can control MimoLive fully from my StreamDeck but this (minimizing the software) has definitely solved the CPU usage spike by 90%… that 10% or less use surely what’s required to run it which is fair enough.
I think the main culprit isn’t even MimoLive but the WindowServer which is a required MAC OS app that draws the front-end of any app… with the multiple cameras on and the keepalive settings etc, surely this requires strong resources.
Following this setup/steps… I managed to do a Livestream while mixing music using software on the same MBP that I’m using to stream for over 3 hours while the CPU usage never went above 14%… pretty good hein!!!
Can you explain what you did exactly? I’m having incredible CPU spikes (from like 70% to like 220%), especially when I use a video slide show source or a browser window source. Minimizing mimoLive using the yellow button on the app does nothing to the CPU spike; are you doing something else?
Could you also close the output video preview… like mentioned above, I use StreamDeck to control scenes. I think it’s worth closing the video output preview (can also be minimised within the mimolive app) and then minimise the mimolive app itself should solve your issues.
I never used slideshow or browser capture on mimolive to be fair, these layers would surely use lot of ressources especially the screen capture on the browser.
I discovered Cpu spikes using windows capture mainly appears when you capture area is bigger than document size.
Simply resize down the browser windows and the cpu usage will down a lot
This makes sense. Unfortunately if I resize the browser window I can no longer see the image (and I can’t control resolution in the external window). But I might make the entire document bigger and see if that helps.
it’s a URL for an overlay via streamelements; there’s very little actual stuff to render most of the time, which makes it stranger that it’s hitting the CPU so hard … StreamElements
Edit - I should add that some of the content is dynamically generated, so the black box off to the side will fill with chat, and some emojis will be drawn and bounce around the screen. But I’m getting the CPU hit even when there is no dynamic content being generated.
