Question / Help High Encoding from nowhere on OBS Studio

Danka

New Member
Hello.

I've been streaming with OBS Studio for 2 weeks now, and yesterday when I started my stream on Twitch, I had lots of "Consider changing your specs" and dropped frames. I didn't switch any of my settings before it so it started from nowhere and I don't know how to fix it.

I've read lots of tutorials on this forum and changed some of my settings, but It didn't solve it.

Here's the log:

https://gist.github.com/anonymous/09a55d5a60aadad783fc5e1cdfd50872
 

RytoEX

Forum Admin
Forum Moderator
Developer
You changed your x264 encoder from the veryfast preset to faster, to veryslow, to faster. Please change it back to veryfast, if you're going to use x264.

Code:
23:49:14.385: base resolution: 1600x900
23:49:14.385: output resolution: 1200x674
Why are you using 1200x674 (AR 1.7804~) instead of 1200x675 (AR 1.7778~)?

Code:
00:00:22.562: Output 'adv_file_output': Number of skipped frames due to encoding lag: 14952 (77.2%)
00:00:22.562: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 1210 (6.1%)
00:00:22.563: ==== Recording Stop ================================================
[...]
00:00:23.857: Output 'adv_stream': Number of skipped frames due to encoding lag: 14990 (77.2%)
00:00:23.857: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 1214 (6.1%)
00:00:23.857: Output 'adv_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 347 (1.8%)
00:00:23.859: ==== Streaming Stop ================================================
Your problem seems to be encoding and rendering, not bandwidth. Start by going back to x264 veryfast and posting a fresh clean log with a single recording/streaming session. If that does not help, then there are further steps we can take, such as switching to NVENC for your recording encoder.
 

RytoEX

Forum Admin
Forum Moderator
Developer
Rytoex

I stream on 1600x900, but my monitor resolution is 1440x900. If I stream on this native resolution, there will be black bars bordering the video. So I must use 1200x675 on the output resolution? I'll do it.

I changed to veryfast again, but it stills the same thing.

https://gist.github.com/anonymous/72cea97c32358c6b4c2b826dc8674a1e
I'm not saying you have to use 1200x675 as your output resolution. However, if your base canvas resolution is 1600x900, then 1200x674 isn't the same aspect ratio, so it would make sense to use 1200x675 instead.

Also, changing your base canvas to larger than your monitor may be making more work for your system. I missed that the first time. If you're making the base canvas larger, what are you doing to your sources? Are you stretching them to fit?


Code:
21:32:42.730: Output 'adv_stream': Number of skipped frames due to encoding lag: 766 (36.9%)
21:32:42.730: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 24 (1.2%)
21:32:42.754: ==== Streaming Stop ================================================
[...]
21:32:43.485: Output 'adv_file_output': Number of skipped frames due to encoding lag: 766 (37.0%)
21:32:43.485: Output 'adv_file_output': Number of lagged frames due to rendering lag/stalls: 24 (1.2%)
21:32:43.485: ==== Recording Stop ================================================

This is less skipped/lagged frame than before, but chances are your CPU can't handle recording and streaming on top of its existing tasks. Try setting your streaming x264 encoder to superfast or ultrafast.

You may also want to consider trying this in a fresh Scene Collection to make sure that your other scenes aren't causing the slowdown.

After those entries in your log, you adjusted your output resolution to 1280x720, and your encoder started to choke. After that, there are a bunch of adjustments and retries, and then the log gets cut off. Please try to only do a single recording/streaming attempt with a single set of settings. Making lots of changes and multiple attempts clutters the log and makes it hard to see where the issues are occurring. Please also make sure to upload complete logs that show the start and end of your streaming/recording sessions.
 

Danka

New Member
I made my layout on 1600x900, and I stretch my game client to fit it. It works fine.

Before I keep doing this tests, I'm going to change the thermal grease from my CPU today. I have this i5 since 2012 and I never changed. My friend who studies CPU stuff, told me to use a software called HW Monitor and do some stress tests on it, and maybe he found the problem. My i5 is overheating a lot.

7371b2884369eb211fa3c305c889c238.png


I'm going to get a MX-4 Thermal Grease later today. After changing it, I'll post again.
 

RytoEX

Forum Admin
Forum Moderator
Developer
WHOA.

Yes, overheating can affect performance. Your temperatures are way too high. Idle CPU temperatures should be closer to 25-35 °C. Normal CPU temperatures should be around 50-62 °C. The max CPU temperature for your CPU should be about 67 °C. This site has a decent reference table for CPU temperatures.

Your CPU and system hardware are reaching temperatures where water boils.


I made my layout on 1600x900, and I stretch my game client to fit it. It works fine.
If you're still having issues after you cool down your CPU... If you're stretching/skewing sources anyway, why don't you set your canvas size to the size you're going to downscale to (1280x720 or 1200x675 or something else)? You're basically creating more work for your system by setting a higher canvas size and then downscaling it. Why not just start at the downscaled size in this case?
 
Top