Encoding overload???

C

Castro1477

New Member
I’m not sure where to start with fixing the issue but the past week or two while streaming I’ve been getting messages saying encoding overload and my fps has been dropping and my time to render frames is high. I’ve also been getting a lot of frames dropped due to encoding lag/ rendering lag. I had not had these issues in the past year and a half only recently. Does anyone know how I may be able to fix this or adjust my settings?

I stream at 1080 and record at 1080 I use restream through obs if there’s anymore information that is needed I can give it.

My pc is a I9-13900k rtx 4090 asus z790-e 64 gb of DDR5 ram 4 2TB Samsung 980 pro ssd 1 2TB 970 pro ssd
 
qhobbes

qhobbes

Active Member

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 obsproject.com
 
C

Castro1477

New Member
Castro1477 said:
I’m not sure where to start with fixing the issue but the past week or two while streaming I’ve been getting messages saying encoding overload and my fps has been dropping and my time to render frames is high. I’ve also been getting a lot of frames dropped due to encoding lag/ rendering lag. I had not had these issues in the past year and a half only recently. Does anyone know how I may be able to fix this or adjust my settings?

I stream at 1080 and record at 1080 I use restream through obs if there’s anymore information that is needed I can give it.

My pc is a I9-13900k rtx 4090 asus z790-e 64 gb of DDR5 ram 4 2TB Samsung 980 pro ssd 1 2TB 970 pro ssd
Click to expand...
https://obsproject.com/logs/zrqBq6aqcgGEXJHO here is my last log file
 
Xsoulsin

Xsoulsin

Member
Don't use Game Capture and Display Capture in the same scene. They can cause issues.

Analyzer | OBS

OBS (Open Broadcaster Software) is free and open source software for video recording and live streaming. Stream to Twitch, YouTube and many other providers or record your own videos with high quality H264 / AAC encoding.
obsproject.com obsproject.com
 
qhobbes

qhobbes

Active Member
Do that^ and
1. You want output FPS, input FPS and refresh rate to be even multiples of each other. It looks like your input is 165. If possible, set the refresh rate to 120 and cap your games at 120/enable v/g-sync. If doesn't work on the first monitor, try the others.
2. Your base is 2560x1440 so change the resolution on your Logitech BRIO from 4096x2160 to something around it's size in the scene. Avoid resizing/stretching/shrinking in scene. Ok to crop.
3. If you receive input on your 4K60 Pro when the resolution is set to 60 instead of 59.94, then set it to 60.
4. Your log contains no streaming session. Results of this log analysis are limited. Please post a link to a clean log file.
To make a clean log file, please follow these steps:

1) Restart OBS.
2) Start your stream for at least 30 seconds. Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc.
3) Stop your stream.
4) Select Help > Log Files > Upload Current Log File. Send that link here.
 
C

Castro1477

New Member
qhobbes said:
Do that^ and
1. You want output FPS, input FPS and refresh rate to be even multiples of each other. It looks like your input is 165. If possible, set the refresh rate to 120 and cap your games at 120/enable v/g-sync. If doesn't work on the first monitor, try the others.
2. Your base is 2560x1440 so change the resolution on your Logitech BRIO from 4096x2160 to something around it's size in the scene. Avoid resizing/stretching/shrinking in scene. Ok to crop.
3. If you receive input on your 4K60 Pro when the resolution is set to 60 instead of 59.94, then set it to 60.
4. Your log contains no streaming session. Results of this log analysis are limited. Please post a link to a clean log file.
To make a clean log file, please follow these steps:

1) Restart OBS.
2) Start your stream for at least 30 seconds. Make sure you replicate any issues as best you can, which means having any games/apps open and captured, etc.
3) Stop your stream.
4) Select Help > Log Files > Upload Current Log File. Send that link here.
Click to expand...
Im not sure why the log is showing like that if it was from my stream yesterday that was recorded and streamed. I also have the display capture and game capture on the same scene but I dont use them together. I only use display capture for CSGO. I also dont have issues with the capture card because thats only used when im on console.

My main monitor is running at 165 htz my other two monitors run at 144 but I only play on my 165 htz monitor. I appreaciate all the recomendations though and will upload a new log shortly.
 
A

AzurTheDragon

New Member
I reverted back to 30.1.1 and I didn't have so far "encoding overload" and dropped frames anymore. There's definitely an issue with 30.1.2
 
R

rockbottom

Active Member
The Scene "In Game" still has both a Game & Display capture. This needs to be fixed.

Rendering lag is GPU overload. If you run your monitors @ 120HZ as noted above, your recordings won't stutter & it should reduce or even eliminate that lag. For the encoding lag, change your Presets to P5. Currently you're using P6 & P7, both are too slow for H264.
Bandwidth appears to be an issue as well.
03:44:45.560: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 58408 (8.0%)
03:44:45.560: Output 'adv_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 856 (0.1%)
03:44:45.560: Video stopped, number of skipped frames due to encoding lag: 58424/1465718 (4.0%)

Uncheck rescale output on both the Recording & Streaming Tabs, neither are needed.

Something to keep on eye on, may improve as system load is reduced.
21:54:11.127: Max audio buffering reached!
21:54:11.127: adding 960 milliseconds of audio buffering, total audio buffering is now 960 milliseconds (source: Desktop Audio)
21:54:11.127:
22:05:55.347: User added source 'Chat' (browser_source) to scene 'In-Game'
22:07:24.782: User Removed source 'Chat' (browser_source) from scene 'In-Game'
00:14:56.461: Source Desktop Audio audio is lagging (over by 176280.38 ms) at max audio buffering. Restarting source audio.

There's some more in the log but test with the changes above & see how it goes.
 
qhobbes

qhobbes

Active Member
You need to make more adjustments:
1. In Windows, we recommend that "Game Mode" be enabled. Game Mode can be enabled via the Windows "Settings" app, under Gaming > Game Mode.
2. Display and Game Capture Sources interfere with each other. NEVER put them in the same scene (In-Game).
3. In the Output Encoder Settings for Streaming, disable Psycho Visual Tuning and set Multipass Mode to Single Pass. For Recording, do the same but also disable Look-ahead. Those use additional GPU.
4. Your base resolution is 2560x1440 so change the resolution on your Logitech BRIO from 4096x2160 to something around it's size in the scene. Avoid resizing/stretching/shrinking in scene. Ok to crop.
5. If you receive input on your 4K60 Pro when the fps is set to 60 instead of 59.94, then set it to 60.
 
R

rockbottom

Active Member
Until you tame the rendering lag, you'll get nothing but crap in > crap out. Adjustments made did diddly.

23:53:53.523: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 23809 (7.3%)
23:53:53.523: Output 'adv_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 36 (0.0%)
23:53:53.523: Video stopped, number of skipped frames due to encoding lag: 23809/677470 (3.5%)

Encoding Performance Troubleshooting | OBS

OBS Knowledge Base. Learn best practices to solve encoding performance issues
obsproject.com obsproject.com
 
R

rockbottom

Active Member
22:33:54.213: Webroot SecureAnywhere: enabled (AV)

22:33:54.512: Available Video Adapters:
22:33:54.514: Adapter 0: NVIDIA GeForce RTX 4090
22:33:54.514: Dedicated VRAM: 25314721792 (23.6 GiB)
22:33:54.514: Shared VRAM: 34223888384 (31.9 GiB)
22:33:54.514: PCI ID: 10de:2684
22:33:54.514: HAGS Status: Disabled (Default: No, Driver status: Supported)
22:33:54.514: Driver Version: 31.0.15.5222
22:33:54.515: output 0:
22:33:54.515: name=DELL S2721DGF
22:33:54.515: pos={0, 0}
22:33:54.515: size={2560, 1440}
22:33:54.515: attached=true
22:33:54.515: refresh=165
22:33:54.515: bits_per_color=8
22:33:54.515: space=RGB_FULL_G22_NONE_P709
22:33:54.515: primaries=[r=(0.685547, 0.308594), g=(0.264648, 0.667969), b=(0.150391, 0.057617), wp=(0.313477, 0.329102)]
22:33:54.515: relative_gamut_area=[709=1.329573, P3=0.980123, 2020=0.703173]
22:33:54.515: sdr_white_nits=80
22:33:54.515: nit_range=[min=0.500000, max=270.000000, max_full_frame=270.000000]
22:33:54.515: dpi=96 (100%)
22:33:54.515: id=\\?\DISPLAY#DEL41D9#5&1e91530&0&UID4357#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
22:33:54.515: alt_id=\\.\DISPLAY1
22:33:54.516: output 1:
22:33:54.516: name=LG ULTRAGEAR
22:33:54.516: pos={2560, -764}
22:33:54.516: size={1440, 2560}
22:33:54.516: attached=true
22:33:54.516: refresh=144
22:33:54.516: bits_per_color=8
22:33:54.516: space=RGB_FULL_G22_NONE_P709
22:33:54.516: primaries=[r=(0.685547, 0.308594), g=(0.264648, 0.667969), b=(0.150391, 0.057617), wp=(0.313477, 0.329102)]
22:33:54.516: relative_gamut_area=[709=1.329573, P3=0.980123, 2020=0.703173]
22:33:54.516: sdr_white_nits=80
22:33:54.516: nit_range=[min=0.249600, max=351.276398, max_full_frame=351.276398]
22:33:54.516: dpi=96 (100%)
22:33:54.516: id=\\?\DISPLAY#GSM5BB4#5&1e91530&0&UID4355#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
22:33:54.516: alt_id=\\.\DISPLAY2
22:33:54.517: output 2:
22:33:54.517: name=Dell S2716DG
22:33:54.517: pos={-1440, -769}
22:33:54.517: size={1440, 2560}
22:33:54.517: attached=true
22:33:54.517: refresh=144
22:33:54.517: bits_per_color=8
22:33:54.517: space=RGB_FULL_G22_NONE_P709
22:33:54.517: primaries=[r=(0.639648, 0.330078), g=(0.299805, 0.599609), b=(0.150391, 0.059570), wp=(0.312500, 0.329102)]
22:33:54.517: relative_gamut_area=[709=0.998664, P3=0.736186, 2020=0.528164]
22:33:54.517: sdr_white_nits=80
22:33:54.517: nit_range=[min=0.500000, max=270.000000, max_full_frame=270.000000]
22:33:54.517: dpi=96 (100%)
22:33:54.517: id=\\?\DISPLAY#DELA0D1#5&1e91530&0&UID4353#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
22:33:54.517: alt_id=\\.\DISPLAY3

22:33:57.013: Could not parse stylesheet of object QFrame(0x1f0df7d5570, name = "streamelements_central_widget_frame")
22:33:57.013: Could not parse stylesheet of object QFrame(0x1f0df7d5570, name = "streamelements_central_widget_frame")
22:33:57.013: QMainWindow::addDockWidget: invalid 'area' argument
22:33:57.020: QDockWidgetLayout::addItem(): please use QDockWidgetLayout::setWidget()
22:33:57.021: QMainWindow::addDockWidget: invalid 'area' argument
22:33:57.042: QWidget::setTabOrder: 'first' and 'second' must be in the same window

SE Errors
22:33:57.962: obs-streamelements: detected obs-streamelements-core version: 20240130000097
22:33:57.962: obs-streamelements: ShowStatusBarMessage: No software update available.
22:33:59.051: [obs-browser: 'Alert Box'] Error: Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://www.youtube.com') does not match the recipient window's origin ('https://streamlabs.com'). (https://www.youtube.com/s/player/edea0cc6/www-widgetapi.vflset/www-widgetapi.js:1261)

22:33:59.959: [obs-browser: 'Alert Box'] Error: Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://www.youtube.com') does not match the recipient window's origin ('https://streamlabs.com'). (https://www.youtube.com/s/player/edea0cc6/www-widgetapi.vflset/www-widgetapi.js:1261)
22:33:59.968: [obs-browser: 'Alert Box'] Error: Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://www.youtube.com') does not match the recipient window's origin ('https://streamlabs.com'). (https://www.youtube.com/s/player/edea0cc6/www-widgetapi.vflset/www-widgetapi.js:1261)
22:33:59.969: [obs-browser: 'Alert Box'] Error: Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('https://www.youtube.com') does not match the recipient window's origin ('https://streamlabs.com'). (https://www.youtube.com/s/player/edea0cc6/www-widgetapi.vflset/www-widgetapi.js:1261)

Still checked
22:34:32.658: encoder 'advanced_video_stream': Scaled resolution matches output resolution, scaling disabled
22:34:32.658: encoder 'advanced_video_recording': Scaled resolution matches output resolution, scaling disabled

Still lagging....
22:34:38.140: Max audio buffering reached!
22:34:38.140: adding 960 milliseconds of audio buffering, total audio buffering is now 960 milliseconds (source: Desktop Audio)
22:34:38.140:
22:34:38.160: Source Desktop Audio audio is lagging (over by 21077.71 ms) at max audio buffering. Restarting source audio.

Known issues (EEE) with Intel 2.5GbE NIC, update your driver.
22:36:14.303: [rtmp stream: 'adv_stream'] Interface: Intel(R) Ethernet Controller I226-V (ethernet, 1000↓/1000↑ mbps)
22:36:14.303: [rtmp stream: 'adv_stream'] Interface has non-zero error counters (678/0 errors, 672/0 discards)

22:36:14.223: preset: p6
22:36:14.303: preset: p7
 
You must log in or register to reply here.
Top