Question / Help Obs causing huge cpu spikes up to 65% use

i did change to performance power setting is windows and disabled cool n quite as well but still its the same, its something to with obs itself since when this spike happens its obs spiking up to ridiculous cpu usage, i mean im no expert or programmer or anything but i really dont know what else could be wrong with my settings/hardware
http://www.twitch.tv/sad_samurai/videos
 
Just btw: There were problems with people using AMD FX cpus few months ago. Not sure if the problems are fully fixed or not.
 
i even tried the test build now but still the same it come out after 2-4 mins and after that its like a clockwork the only thing i dont understand that as i said before in planetside 2 it was fine without any of the current tweaks and then the next day it wasnt, strange but i really want to use obs its awesome and free and i wont pay for xsplit when i cant even use it without dxtory since xspilt wont work with 7xxx radeons still after 1.5 years...
 
Not just the power setting is windows. the only reason you see spikes in cpu usage is because the cpu it self is not running at 4.5 ghz when that happens check the bios and disable any power saving features/options.
 
It's at 4.4 ghz because you're constantly pushing the cpu with prime 95 while it's not the case with obs. Try the preset "fast" and 60 fps and post a vod.
 
Ive been on this build for the majority of today but that custom setting seem to be working so far with veryfast so im happy (tho it crashed windows now :D ) we'll see i feel we are on good tracks now thx again !
 
First, Planetside 2 is an extremely CPU-bound game. Its easy and frequent to drop below 60 FPS without streaming in it, with streaming or running Fraps, it gets even worse. Its going to negatively effect your stream and your gameplay.

hilalpro said:
threads=16 is a line you should add in the custom settings from the obs's advanced settings tab.
Click to expand...

If OBS behaves anything like Handbrake, you don't want to do this. The default number of threads is, if I recall correctly, 1.5 x the number of cores. This setting (threads=16) will go even higher than that, and basically make the OS do more work load balancing because you're never going to be able to keep all the threads fed. You should instead try setting threads=6 or less, certainly not more, not if you're gaming and streaming on the same CPU.

Which leads me to my next suggestion. For CPU-bound games like Planetside 2, I think the only realistic solution is to either use Quicksync, or do what I do: use a second PC and a video capture card. But for problems with non-CPU-bound games, I don't have any more to add, I'm not sure why you'd have problems.
 
Well thing is as i mentioned earlier i had no problem streaming ps2 @720p60fps until yesterday and i didnt even have any of the tweaks for the cpu power and still had cool n' quite on and so on and so forth so you see i really dont know what could have happened. but i dont use threads=16 anymore i tried it once in multiple settings it didnt help so i scraped it
 
Boildown said:
If OBS behaves anything like Handbrake, you don't want to do this. The default number of threads is, if I recall correctly, 1.5 x the number of cores. This setting (threads=16) will go even higher than that, and basically make the OS do more work load balancing because you're never going to be able to keep all the threads fed. You should instead try setting threads=6 or less, certainly not more, not if you're gaming and streaming on the same CPU.
Click to expand...

the defaults behavior for the encoder is to potentially utilize all the threads available even when only utilizing 75% of them for frame work the rest of the threads will still be utilized as lookahead threads.

disable opencl=true and add rc-lookahead=1 with the default preset.
 
It crashed for a lot of people at 10 but haven't with rc-lookahead=1 i believe that it has something to do with the created latency.
 
You must log in or register to reply here.
Back
Top