Possible CPU hog and fix (steps in thread) if using a old media source

FortuN

Member
So, i have not made a new scene profile in quite a while. Noticed that my CPU usage was higher than when i made a new scene profile. So i tested just making an empty scene in my old scene profile. I was still using more CPU even though it was completly empty i was around 7-10% in usage with my 9900K. So i figured something must be wrong and haven't gone smoothly through the updates. So i started testing inactivating every source i had and after a while i figured its the
"Media Source" that is the reason. Probably its having some issues between updates so its not working completly if you have updated your OBS from older one using the older Scene profile with old Media Source.

So what i did was removing all my "Media Source" sources and then adding new "Media Source" source. This fixed the CPU usage when your not wathcing that scene. It seems to be activated in background even if your in another scene, is still uses your CPU since its kinda bugged it seems. It doesen't help to inactivate them either. It still uses the CPU even if switching scene.

so TLDR

If you have updated OBS from a older version and using old scene profiles, remove all your "Media Sources" and add them again. This will fix most of the CPU usage. It has to be all old "media sources" that you have in that scene profile.


Also there is kinda no way of knowing if its using the "new" media source or the "old" media source. My cpu usage on a empty scene went down to around 0,5-2% after doing this. Considering im using a high end CPU this could be much more favorable for those who does not.
 

FortuN

Member
Its probably with that update they did. It was inactivated when i tested in "old" one. All settings were same for comparison.
 

_AgentCobra

Member
Removing and re-adding is still a huge cpu gain fix today. js
it took me 30mins + to recreate media sources because i have a big production - the change was 45% to 19-25%
 
Top