Question / Help RTX 2070 Super - skipped frames in recording

D

dul2burg

New Member
Hi,

I have been experimenting with various OBS settings, turning Game Mode on and off, running OBS in Admin mode and keep getting skipped frames in RECORDING no matter what.

09:49:30.843: Video stopped, number of skipped frames due to encoding lag: 1481/174540 (0.8%)
16:58:08.668: Video stopped, number of skipped frames due to encoding lag: 923/189924 (0.5%)

Specs:
Ryzen 5 2600X
RTX 2070 Super
16 GB 3200Mhz
144hz Monitor
Win10 Home

Same issue with CS:GO and GTA 5.

With CS:GO GPU never used more than 60%, CPU is always at 30-40% - All maxed out settings in 1080p.
With GTA 5 GPU is almost maxed out, CPU is usually around 50-60% at ultra settings in 1080p.

FPS in game is always good, dont even feel OBS working while gaming.

Attached log is for CSGO recording.

I would assume that I should have enough HW power to record in 1080p.

Any help is appreciated.
 

Attachments

I might have cracked it...

I got two monitors, one 60hz the other is 144hz, both connected to the same card. Saw somewhere in this forum that there is an issue with Windows 10, OBS and two monitors that are running in different speeds.

Disabled the second monitor and it seems to be fine, no skipped frames so far in 10 minutes play of CSGO and GTA 5.

Will continue testing and report back.
 
Poor performance in WIndows while using two monitors running at different refresh rates but connected to a single GPU is a known issue. Workarounds include either disconnecting one monitor, or setting both monitors to the same refresh rate.
 
So I am still seeing some drops even though I configured windows to have only one display working.

Do I actually have to disconnect it from the PC even though the other monitor is off?
 
15:14:31.893: Video stopped, number of skipped frames due to encoding lag: 82/8077 (1.0%)
20:05:33.862: Video stopped, number of skipped frames due to encoding lag: 856/160071 (0.5%)
20:48:45.717: Video stopped, number of skipped frames due to encoding lag: 514/141797 (0.4%)
21:35:27.728: Video stopped, number of skipped frames due to encoding lag: 1245/166631 (0.7%)
16:15:26.880: Video stopped, number of skipped frames due to encoding lag: 1020/196875 (0.5%)


The log only registers one display, so that's not your issue. That issue is not reported in OBS' lag statistics in any case.

The log only shows pretty minor encoding lag. If the one display you left connected is 144hz, then the likely stutter you see is the inevitable result of downsampling to 60hz, since those rates do not divide evenly.

The tell would be whether this encoding lag is very variable-- happening, for instance, during exceptionally demanding frames-- or constantly, a handful of missing frames over regular periods.

15:12:00.823: - scene 'Scene':
15:12:00.823: - source: 'Game Capture' (game_capture)
15:12:00.823: - source: 'Display Capture' (monitor_capture)

Combining game and monitor captures (both of which expect to be full screen) is not performant or recommended, and can cause interference.

You'd also be better off with CQP rate control than VBR if you're recording for editing.
 
So I have been experimenting with OBS settings and I am still getting skipped frames:
number of skipped frames due to encoding lag: 479/30889 (1.6%)

Full log

My monitor is 144hz, Ive tried putting 60hz, tried different recording formats and settings and the result is always the same.

Strangely enough, I do not have any skipped frames when I stream. I can stream and record or just stream and there is 0 skipped frames.

I get skipped frames in all games during regular recording. 0 skipped when streaming.

Any help is appreciated.
 
Because unlike other features of the NVENC encoder, it consumes GPU resources. You're still getting small amounts of both rendering and encoding lag. Other workarounds are reducing resolution/FPS, framerate capping your application.
 
My CPU and/or GPU are never maxed out. There is gotta be some sort of an error in my config or a bug.

Why would streaming the same game would result in 0 drops. Streaming AND recording at the same time is also 0 drops. That doesn't make any sense. If anything, streaming and recording should produce even more drops since the system would be under a heavier load.
 
If you use the stream encoder when simultaneously recording and streaming, that's no more load than doing just one.

Without a logfile that shows that happening, I can't say for sure.

As for your config:

13:44:04.040: - source: 'Game Capture' (game_capture)
13:44:04.040: - filter: 'Color Correction' (color_filter)
13:44:04.040: - source: 'Display Capture' (monitor_capture)
13:44:04.040: - filter: 'Crop/Pad' (crop_filter)

You shouldn't have game and display captures in the same scene, as this is nonperformant, even if one is hidden. This can reduce performance and cause interference.

13:44:04.040: - scene 'Record':
13:44:04.040: - source: 'Standoff' (game_capture)
13:44:04.040: - source: 'Full Screen Game' (game_capture)

Similarly, having multiple game captures in a single scene can also cause performance/stability issues, as both expect to be exclusive and fullscreen.

13:46:21.521: rate_control: VBR
13:46:21.521: bitrate: 40000

Generally speaking there are few reasons to use VBR when local recording. Use CQP rate control and a quality setting between 14 (very good) and 23 (pretty good).

I also believe that encoding lag counts any frames dropped due to slow media, so if you're recording to a spinning disk rather than an SSD and that device can't keep up your selected bitrate, this might also register as dropped frames.
 
Thanks for your update.

You got an interesting point regarding recording media. I am recording to a regular HDD (not SSD), this would explain why Stream never has any dropped frames while recording to an HDD does. Seems like my internet connection is faster than my HDD :D

I will try testing with an SSD and report back.
 
Quick update...

Changed recording location to an SSD and not seeing any skipped frames anymore.

Thanks for your help!
 
You must log in or register to reply here.
Back
Top