Missed and skipped frames due to rendering/encoding lag

D

DyslexicApricot

New Member
I have been getting missed and skipped frames due to rendering and encoding lag for a few months now and it randomly started happening up until about 3 months ago I didn't have this issue and I haven't changed any of my obs settings at all and I need help fixing it as the error still persists even after a gpu upgrade going from a 1660 ti to a 3060 here is the log that I just got: https://obsproject.com/logs/EwRGDfBSFYbCLQOq
 
R

rockbottom

Active Member
Tons of SE errors should be addressed. The other issue I see is your monitors. 75HZ Refresh Rate spec & you're running them out of spec @ 100HZ, how's that working out for ya? Rendering lag/GPU overload. Set them @ 60.

00:37:03.323: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 552 (12.9%)
00:37:03.323: Video stopped, number of skipped frames due to encoding lag: 552/4168 (13.2%)
 
D

DyslexicApricot

New Member
rockbottom said:
Tons of SE errors should be addressed. The other issue I see is your monitors. 75HZ Refresh Rate spec & you're running them out of spec @ 100HZ, how's that working out for ya? Rendering lag/GPU overload. Set them @ 60.

00:37:03.323: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 552 (12.9%)
00:37:03.323: Video stopped, number of skipped frames due to encoding lag: 552/4168 (13.2%)
Click to expand...
So what all do you recommend to fix these things set the monitor refresh rate to 60? The monitors are rated to go up to 100hz also I don't use streamelemts for anything so idk why there's SE errors
 
R

rockbottom

Active Member
Yeah, your monitors should be @ 60HZ when using OBS. Not at some refresh rate they don't support.

As far as SE goes, it's all your browser sources. Look at the log, not hard to figure out what they are. If you still have rendering lag after switching the monitors to 60HZ, it's most likely one or more of them causing it.
 
D

DyslexicApricot

New Member
rockbottom said:
Yeah, your monitors should be @ 60HZ when using OBS. Not at some refresh rate they don't support.

As far as SE goes, it's all your browser sources. Look at the log, not hard to figure out what they are. If you still have rendering lag after switching the monitors to 60HZ, it's most likely one or more of them causing it.
Click to expand...
I changed the refresh rate and got rid of the only thing that could have been an SE browser source and the missed and skipped frames still persists here's the new log https://obsproject.com/logs/z0XoJNfbOeFnXC1t
 
R

rockbottom

Active Member
Nice, the log is looking better. There are still some browser errors, that may or may not be contributing to the lag.

21:33:05.721: [obs-browser: 'Blerp'] Error: BLOOM-URL [object URL] s2suvsvyirvm SOURCE normal Mon Aug 05 2024 21:33:05 GMT-0500 (Central Daylight Time) (https://obs.blerp.com/pwn/s2suvsvyirvm:1817)

21:33:05.727: [obs-browser: 'Blerp'] Error: SOCKET_BLERP_VERSION 30 "5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.134 OBS/30.2.2 Safari/537.36" "Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.134 OBS/30.2.2 Safari/537.36" (https://obs.blerp.com/pwn/s2suvsvyirvm:1845)

21:33:06.297: [obs-browser: 'Blerp'] Error: CONNECTION_SUCCESS oS6M22omMvB4mBzwHtxG s2suvsvyirvm (https://obs.blerp.com/pwn/s2suvsvyirvm:1872)

21:34:41.480: [obs-browser: 'Blerp'] Error: heart_beat_check_server_client_callback s2suvsvyirvm (https://obs.blerp.com/pwn/s2suvsvyirvm:1925)

21:33:01.538: Game Mode: Off > On

Fix this Scene, there should only be (1) Display, Game or Window Capture
21:33:04.334: - scene 'PC Game':
21:33:04.334: - source: 'Game' (window_capture)
21:33:04.334: - source: 'Valorant' (game_capture)
21:33:04.334: - source: 'Death Counters' (group)
21:33:04.334: - source: 'Deaths' (text_gdiplus_v3)
21:33:04.334: - source: 'Death Counter' (text_gdiplus_v3)
21:33:04.334: - source: 'Mouse and key overlays' (group)
21:33:04.334: - source: 'Keyboard' (input-overlay)
21:33:04.334: - source: 'Mouse' (input-overlay)
21:33:04.334: - source: 'Xbox Controller' (input-overlay)
21:33:04.334: warning: Could not update timestamps for skipped samples.
21:33:04.334: - source: 'Elgato Cam' (dshow_input)
21:33:04.334: - source: 'PC Game Scene' (browser_source)
21:33:04.334: - source: 'Guru Shoutout' (browser_source)
21:33:04.334: - monitoring: monitor and output
21:33:04.334: - source: 'Emote Wall' (browser_source)
21:33:04.334: - source: 'Audio Sources' (group)
21:33:04.334: - source: 'Blerp' (browser_source)
21:33:04.334: - source: 'Sound Alerts' (browser_source)
21:33:04.334: - source: 'Alert Source' (browser_source)

There is a sample-rate mis-match & associated lag. This may also indicate that your CPU is getting slightly overloaded.
21:33:04.387: [DShow Device: 'Xbox'] settings updated:
21:33:04.387: video device: EVGA XR1 Pro Capture Box Video
21:33:04.387: video path: \\?\usb#vid_3842&pid_310b&mi_00#7&2ae59d05&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global
21:33:04.387: resolution: 1280x720
21:33:04.387: flip: 0
21:33:04.387: fps: 30.00 (interval: 333333)
21:33:04.387: format: NV12
21:33:04.387: buffering: disabled
21:33:04.387: hardware decode: disabled
21:33:04.503: using video device audio: no
21:33:04.503: separate audio filter
21:33:04.503: sample rate: 44100
21:33:04.503: channels: 2
21:33:04.503: audio type: Capture
21:34:11.706: adding 341 milliseconds of audio buffering, total audio buffering is now 384 milliseconds (source: Xbox)

I normally don't recommend running OBS as ADMIN but you may have to.

After you finish the next test, close/re-open OBS & post the previous log. Easier to spot where the lag is happening with a complete log.
 
R

rockbottom

Active Member
Another possible issue is a Nvidia driver conflict. The old driver should have been removed prior to the 1660TI being removed from the system. Even if it was, if the PC was still connected to the internet when the PC was turned back on after the 3060 install, Winblowz most likely installed a driver & it wasn't v560.70.
 
D

DyslexicApricot

New Member
rockbottom said:
Nice, the log is looking better. There are still some browser errors, that may or may not be contributing to the lag.

21:33:05.721: [obs-browser: 'Blerp'] Error: BLOOM-URL [object URL] s2suvsvyirvm SOURCE normal Mon Aug 05 2024 21:33:05 GMT-0500 (Central Daylight Time) (https://obs.blerp.com/pwn/s2suvsvyirvm:1817)

21:33:05.727: [obs-browser: 'Blerp'] Error: SOCKET_BLERP_VERSION 30 "5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.134 OBS/30.2.2 Safari/537.36" "Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.134 OBS/30.2.2 Safari/537.36" (https://obs.blerp.com/pwn/s2suvsvyirvm:1845)

21:33:06.297: [obs-browser: 'Blerp'] Error: CONNECTION_SUCCESS oS6M22omMvB4mBzwHtxG s2suvsvyirvm (https://obs.blerp.com/pwn/s2suvsvyirvm:1872)

21:34:41.480: [obs-browser: 'Blerp'] Error: heart_beat_check_server_client_callback s2suvsvyirvm (https://obs.blerp.com/pwn/s2suvsvyirvm:1925)

21:33:01.538: Game Mode: Off > On

Fix this Scene, there should only be (1) Display, Game or Window Capture
21:33:04.334: - scene 'PC Game':
21:33:04.334: - source: 'Game' (window_capture)
21:33:04.334: - source: 'Valorant' (game_capture)
21:33:04.334: - source: 'Death Counters' (group)
21:33:04.334: - source: 'Deaths' (text_gdiplus_v3)
21:33:04.334: - source: 'Death Counter' (text_gdiplus_v3)
21:33:04.334: - source: 'Mouse and key overlays' (group)
21:33:04.334: - source: 'Keyboard' (input-overlay)
21:33:04.334: - source: 'Mouse' (input-overlay)
21:33:04.334: - source: 'Xbox Controller' (input-overlay)
21:33:04.334: warning: Could not update timestamps for skipped samples.
21:33:04.334: - source: 'Elgato Cam' (dshow_input)
21:33:04.334: - source: 'PC Game Scene' (browser_source)
21:33:04.334: - source: 'Guru Shoutout' (browser_source)
21:33:04.334: - monitoring: monitor and output
21:33:04.334: - source: 'Emote Wall' (browser_source)
21:33:04.334: - source: 'Audio Sources' (group)
21:33:04.334: - source: 'Blerp' (browser_source)
21:33:04.334: - source: 'Sound Alerts' (browser_source)
21:33:04.334: - source: 'Alert Source' (browser_source)

There is a sample-rate mis-match & associated lag. This may also indicate that your CPU is getting slightly overloaded.
21:33:04.387: [DShow Device: 'Xbox'] settings updated:
21:33:04.387: video device: EVGA XR1 Pro Capture Box Video
21:33:04.387: video path: \\?\usb#vid_3842&pid_310b&mi_00#7&2ae59d05&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global
21:33:04.387: resolution: 1280x720
21:33:04.387: flip: 0
21:33:04.387: fps: 30.00 (interval: 333333)
21:33:04.387: format: NV12
21:33:04.387: buffering: disabled
21:33:04.387: hardware decode: disabled
21:33:04.503: using video device audio: no
21:33:04.503: separate audio filter
21:33:04.503: sample rate: 44100
21:33:04.503: channels: 2
21:33:04.503: audio type: Capture
21:34:11.706: adding 341 milliseconds of audio buffering, total audio buffering is now 384 milliseconds (source: Xbox)

I normally don't recommend running OBS as ADMIN but you may have to.

After you finish the next test, close/re-open OBS & post the previous log. Easier to spot where the lag is happening with a complete log.
Click to expand...
Here is the new log after doing everything you recommended and the issue still persists: https://obsproject.com/logs/BulfxFL5DJnBnrkY

I would turn game mode on but last time I did the issue got significantly worse and how do I check to see if there is a previous NVIDIA driver installed and if there is how do I remove it?
 
You must log in or register to reply here.
Top