100% CPU every time I run OBS.

L

lompad

New Member
Every time I launch OBS Studio, the program indicates that the CPU is loaded at 68%. Windows Task Manager shows that OBS is using 98% of the CPU. The OBS internal task manager knows nothing about such a CPU load and everything appears fine there. I've reinstalled the program, but the issue persists. Please help.

Log file: https://obsproject.com/logs/mffEfLDA4CyULKJl

1740343289078.png

​

 
A

AaronD

Active Member
Task Manager reports the entire system load. OBS can't see all of that, and so it reports lower. Use the Task Manager's number, not OBS's.

Anyway, in the Source Profiler screenshot, what are "Intermission" and the other big one that I'm not going to retype?
 
L

lompad

New Member
AaronD said:
Task Manager reports the entire system load. OBS can't see all of that, and so it reports lower. Use the Task Manager's number, not OBS's.

Anyway, in the Source Profiler screenshot, what are "Intermission" and the other big one that I'm not going to retype?
Click to expand...
Iintermission is my main OBS scene. Here is a screenshot from the task manager.

1740391272476.png


1740391333766.png
 
koala

koala

Active Member
It's probably some faulty/improperly used source the reason.
Here is a way how to determine which source it is.
  1. Create a copy of your current scene collection with Scene Collection > Duplicate
  2. In the copy, remove one source after the other, one scene after the other, until the CPU usage disappears.
  3. The last source you just removed is the reason. Load the original scene collection and remove that source in that collection.
 
L

lompad

New Member
koala said:
It's probably some faulty/improperly used source the reason.
Here is a way how to determine which source it is.
  1. Create a copy of your current scene collection with Scene Collection > Duplicate
  2. In the copy, remove one source after the other, one scene after the other, until the CPU usage disappears.
  3. The last source you just removed is the reason. Load the original scene collection and remove that source in that collection.
Click to expand...
Thanks! I'll try and be back with result!
 
L

lompad

New Member
koala said:
It's probably some faulty/improperly used source the reason.
Here is a way how to determine which source it is.
  1. Create a copy of your current scene collection with Scene Collection > Duplicate
  2. In the copy, remove one source after the other, one scene after the other, until the CPU usage disappears.
  3. The last source you just removed is the reason. Load the original scene collection and remove that source in that collection.
Click to expand...
I found out what the reason is. This was the RX Dialogue Isolate plugin, inside the KV Element FX plugin (in the microphone processing chain). Thank you very much!
 
You must log in or register to reply here.
Top