High CPU on NVENC (need extra solutions)

[MeltedhandTTV]

As I've stated I've got high CPU usage minutes after starting a stream. I'm running an i5 quad core (don't remember exactly) and 1050 graphics in a laptop.
-I've gone through all my scenes and closed them when inactive.
- I've closed nonessential startups and processes
- I'm running NVENC on HIGH priority
- IM ONLY USING THE PC FOR STREAMING. NO OTHER PROGRAMS OR WINDOWS ARE OPEN. RUNNING USB CAPTURE FROM XBOX SERIES X.
I've read through these forums and done almost everything I can think of to fix this. I can start the stream fine but after 10-15 minutes or so my CPU goes from 40-50% to 85-95%. I'm trying to achieve 720p60 and I can do 720p30 with less than 40% steady for hours. I understand 60 is a hard achievement but it is doing this anywhere above 30. Any thoughts would be mighty helpful. I'm thinking of just streaming in 480p60 at this point.

 

[MeltedhandTTV]

I will also add that I'm not suffering from frame drops or anything. The stream itself starts suffering. CPU hits 80+ then frames cannot maintain 60. Bounces around 40-58. Also render lag starts getting bad

 

[konsolenritter]

Please open the taskmanager on its detailed page and sort by cpu usage. Start a test streaming and have the taskmanager in foreground. Don't touch anything. Then, when the issue arises, have a look then which programs took part in using most of the cpu. Maybe its another thing than obs.

 

[MeltedhandTTV]

Please open the taskmanager on its detailed page and sort by cpu usage. Start a test streaming and have the taskmanager in foreground. Don't touch anything. Then, when the issue arises, have a look then which programs took part in using most of the cpu. Maybe its another thing than obs.

I did do this already and thank you for responding. I was running throttlestop and task manager to figure all that out. BASICALLY what I figured out is the video preview is causing the cpu to think too much because it has to make up for a second screen essentially. Once I stop the preview CPU drops back to 60% average. It will spike sometimes and frames dip but almost immediately corrects itself and I just did a 3 hour stream with no noticeable issue with this method. It sucks that I can't run the preview as I like seeing what my stream is doing but ultimately this is the best option for now. Any future peeps be aware with any issues like this....TRY WITHOUT THE PREVIEW. I spent way to many hours figuring this out LOL

 

[konsolenritter]

What exactly do you mean with " the video preview [...] has to make up for a second screen essentially. " Are you doubling the preview window by using a projector to an external monitor? What if you double the program window instead? Same outcome?

Its a little bit unusual due to using NVENC means that you should have powerful GPU. Does belong the second screen/monitor to the same GPU? To ask again: What said the taskmanager, is it clearly obs eating most of the cpu ressources really?

Maybe you can provide an obs-log that consists of such recording or streaming session...

 

[MeltedhandTTV]

I can do that when I'm at my computer. The stream preview that shows you everything the viewers see is what was eating my cpu. I don't have a second monitor or anything. Basically if I close that preview window the cpu drops. I just did another stream tonight with no issues. I do see frameskips but I believe that is just network related on my end (I did have a stream disconnect tonight)

 

[MeltedhandTTV]

And yes only OBS and Spotify are running while I stream. OBS is taking on average 70% while I stream....when I was running throttlestop I noticed that POWER kept showing up while OBS is running which means it was hitting its limits. I am on a laptop

 

[konsolenritter]

Still unclear to me, sorry. Are we talking about the studio mode of OBS?
The "preview that shows you everything the viewers see" is named "program", the view positioned to the upper right. The "preview" instead is on the upper left where you can see what you are preparing for the stream after activation, so the stream viewers can't see before its activation of the prepared scene.

You should (as mentioned on the pinned threads) upload an obs-log please and post the link here:

Please post a log with your issue! Here's how...

OBS Studio creates a log file each time you run it which contains very useful diagnostic information. Without a log file, it's much harder for any support volunteers to figure out problems and your post may be ignored. To upload a log file, go to the Help menu > Log Files > Upload Last Log...

obsproject.com

The log should contain the isse (thus a streaming test at least). Please make such test, then close obs, then re-open it, then upload via the menu the "last log".