![]() ![]() USB capture cards can eat a lot of CPU as well, but in my experience, there’s not much you can do about that. Browser sources can also hog resources, especially if they’re loading heavy or animated pages. Changing the camera’s Video Format might also help, though it may affect image quality or framerate. Quicksync obs dropping free#If you’re using a camera that doesn’t take up your entire scene, you can reduce the resolution from the source’s Properties to free up some resources. ![]() If you’re no longer skipping frames, a source on your original scene is probably the culprit. The easiest way to check for misbehaving sources is to create a clean scene collection, from Scene Collections > New, and test with nothing but your primary capture source. This is usually because your CPU is too weak to handle the encoding settings you’re using, but other misbehaving programs or sources can also cause this. If you’re using x264, the default encoder, skipped frames occur when your CPU maxes out and can’t encode the video fast enough. Otherwise, tackle these starting with the highest percentage first. If a problem affected less than 0.1% of frames, it’s usually a non-issue. The number and percentage at the end of the line shows how many frames were affected. If none of these lines are present, then your test didn’t have any problems, and you’ll need to do another one to get any information.Įach line corresponds to a different problem affecting the video. 00:01:45.904: Output 'simple_stream': Number of skipped frames due to encoding lag: 4 (0.0%)Ġ0:01:45.904: Output 'simple_stream': Number of lagged frames due to rendering lag/stalls: 154 (0.0%)Ġ0:01:45.904: Output 'simple_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 30 (0.0%) ![]() You should see a few lines that look something like this-don’t worry if one or two are missing, or they don’t look exactly the same. Go to Help > Log Files > View Current Log. Once your test session is done, stop the recording and/or stream, and leave OBS open. You want your problem to occur in this session, so that you can check the log for anything out of the ordinary: if your stutters are rare, you might need to wait for a while. Close OBS, then open it up again and start a recording or streaming session. The first step in diagnosis is a clean log. But if you’re running into issues with choppy or hitching video, this is an okay place to start. It’s not complete by any means: there are a lot of ways you can fuck up your settings to produce shitty video, and if I could cover them all here, there would probably be an official guide by now. This is a quick guide I threw together to take people through some basic troubleshooting on their own. With that said, if you can only describe your issue with “OBS is lagging”, you’re gonna have a shitty time searching through the support forums. OBS problems are actually pretty easy to diagnose once you know your way around. When in doubt, use the autoconfig wizard! These days, most of what you need to know can be found under View > Stats.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |