Question / Help Getting High Encoding but not with OBS-MP

X

Xode

New Member
Hey there, basically the title. For some reason, lately on my OBS I've been getting "WARNING: High Encoding" when I record with local. It's making my videos stutter and they're basically unwatchable. This wasn't a problem earlier but now I noticed it happening.

As I'm recording with OBS I look at my CPU usage and it's between 20-30% and it never spikes up so I don't know what the problem is.

To try to see if this was hardware related, I installed OBS Multi-platform and set up my settings exactly how they're in the original OBS and I have 0 stutter problems and record just fine. However, the problem with OBS-MP is that my mic volume is extremely low for some reason even when I have it set to full volume, this doesn't happen with the original OBS.

So I either need to fix my original OBS to record locally without any stuttering problems or I need to find a way to fix this mic issue with OBS-MP.

Any help is appreciated!
 

Attachments

Generally speaking, for recording locally you want to follow the recommendations here: https://obsproject.com/forum/resources/how-to-make-high-quality-local-recordings.16

Get rid of "vbv-maxrate=0000 vbv-bufsize=0000" from your custom x264 settings.
Set your Scene Buffering Time to 700
Set your max bitrate to 1000 but keep custom buffer enabled and set to 0.
Set CBR to disabled.
Set the preset to SuperFast
Set Constant Frame Rate to On / Yes.

Make those changes, and if you're still having problems, do a 5 minute or longer encode with as much high action video as your game has to offer, and post that session's OBS log file.
 
If you're looking for lossless recording, you should use "qp=0" in your custom x264 settings. It forces x264 to encode every frame losslessly. Doing this also automatically disables the buffer system, so you don't have to set the buffer to 0 if you use qp=0.

Also, the CPU preset doesn't really matter for local recording. A slower CPU preset doesn't give better quality for the most part, it just produces a smaller file at the cost of more CPU usage. Just use the fastest one that gives you an acceptable filesize. (Faster also means less lag)
 
WilliamBarrows said:
If you're looking for lossless recording, you should use "qp=0" in your custom x264 settings. It forces x264 to encode every frame losslessly. Doing this also automatically disables the buffer system, so you don't have to set the buffer to 0 if you use qp=0.

Also, the CPU preset doesn't really matter for local recording. A slower CPU preset doesn't give better quality for the most part, it just produces a smaller file at the cost of more CPU usage. Just use the fastest one that gives you an acceptable filesize. (Faster also means less lag)
Click to expand...

Hmm, he didn't mention anything about lossless, so I would hesitate to do that. It can make editing your video files afterwards a total biotch.

About the preset not mattering for local recording, not entirely true. UltraFast does some things that can't really be overcome with more bitrate. Might be hard to notice, but it happens. That's why I recommend SuperFast.
 
Boildown said:
About the preset not mattering for local recording, not entirely true. UltraFast does some things that can't really be overcome with more bitrate. Might be hard to notice, but it happens. That's why I recommend SuperFast.
Click to expand...

It's true for lossless (correct me if I'm wrong). I don't work much in non-lossless, so it's possible that there's a difference there. However, I've stopped using pure ultrafast anyway, and now use ultrafast with "rc-lookahead=10" for everything that isn't lossless. Doesn't use much more CPU and can help with quality/bitrate stability. Maybe I should try using superfast if my CPU can handle it.
 
I really have no idea why your hexacore is performing so poorly in those logs. Something is off but I have no idea what. I personally blame Windows 10 but I really have no idea.
 
Windows 10 *does* kinda suck. I've heard alot of people had problem with sound, maybe it's got issues with CPU-coordination aswell. Although Xode said OBS MP works, so it's something only affecting the original OBS apparently.
 
You must log in or register to reply here.
Back
Top