nvidia's official guide for turing leads to enconding overloads recording @ CQP level 15

hash

New Member
Following this Official Nvidia guide for RTX(turing enc) on obs newer than v23
recording using those specific settings as per their screenshots leads to 10% skipped frames and overloads encoder
expected behavior : zero frames skipped, smooth recording @ CQ level 15 (very nice looking footage)
observed behavior : encoding overload

System specs:
asrock x470 taichi mb
ryzen 2700x
2x8GB gskill 3200 cl14 ram
msi rtx 2080 gaming x trio
windows 10 19042.630 (20H2)

task manager while recording footage shows gpu not fully utilized for 3d work and barely touched regarding video encoding.
no screenshot available here but the cpu was barely hitting 50% on two cores if that's of any relevance.
game recorded was ryse son of rome (same problem with guildwars2 and any other game)
final result: Youtube Vid (looks worse with youtube processing on top, of course)

- windows task manager when recording
1606507775146.png


obs window -
obs.jpg


obs settings:
obs settings.png


logfile: (last entry, rest are different attempts) 2020-11-27 21-33-07.txt
 

Attachments

  • 2020-11-27 21-33-07.txt
    37 KB · Views: 54

rockbottom

Active Member
I personally wouldn't have my monitors set @ 75HZ.

Uncheck Lookahead & Psycho Visual Tuning. Set Keyframe Interval to 2 & B-Frames to 2.

Also, what is your F Drive, HDD, SSD or USB? Believe it or not, if your drive can't keep up, it WILL cause encoding lag.
 
Last edited:

rockbottom

Active Member
Fix these Scenes too, having Game & Monitor sources in the same scene can cause flickering.

- scene 'Game':
21:33:09.641: - source: 'Display Capture' (monitor_capture)
21:33:09.641: - source: 'Game Capture 2' (game_capture)
21:33:09.641: - source: 'Media Source' (ffmpeg_source)
21:33:09.641: - source: 'https://chat.restream.io/embed?token=7ec777dd-5b07-4b52-b92e-3919f9ee733c' (browser_source)
21:33:09.641: - source: 'GZ Logo' (group)
21:33:09.641: - filter: 'Scroll' (scroll_filter)
21:33:09.641: - filter: 'Color Correction' (color_filter)
21:33:09.641: - source: 'PWD by Gamezon' (image_source)
21:33:09.641: - source: 'powered by gamezon.io' (text_gdiplus_v2)
21:33:09.641: - source: 'Video Capture Device' (dshow_input)
21:33:09.641: - filter: 'Color Correction' (color_filter)
21:33:09.641: - filter: 'Sharpen' (sharpness_filter)
21:33:09.641: - scene 'Standby':
21:33:09.641: - source: 'Game Capture 2' (game_capture)
21:33:09.641: - source: 'Display Capture 2' (monitor_capture)
21:33:09.641: - source: 'Text (GDI+)' (text_gdiplus_v2)
21:33:09.641: - filter: 'Scroll' (scroll_filter)
 

hash

New Member
I personally wouldn't have my monitors set @ 75HZ.

Uncheck Lookahead & Psycho Visual Tuning. Set Keyframe Interval to 2 & B-Frames to 2.

Also, what is your F Drive, HDD, SSD or USB? Believe it or not, if your drive can't keep up, it WILL cause encoding lag.
I dont have higher refresh rate monitors.
would uncheck however the point in fact here was following the official nvidia compiled guide. did you read that ? its linked by me and is on their official website.
Storage can keep up. seriously who couldnt keep up at 50-70mbit ? a thumb drive can keep up at that.
Storage is an nvme intel 1tb ssd just to clarify.

And turn off HAGS.
Yes, I've heard that before however i am specifically pointing out that the official nvidia guide mentions it - specifically it specifies that they worked with obs on this so it "just works" which it apparently doesnt and was looking for some input from someone on the obs team regarding this issue.

Fix these Scenes too, having Game & Monitor sources in the same scene can cause flickering.

- scene 'Game':
21:33:09.641: - source: 'Display Capture' (monitor_capture)
21:33:09.641: - source: 'Game Capture 2' (game_capture)
21:33:09.641: - source: 'Media Source' (ffmpeg_source)
21:33:09.641: - source: 'https://chat.restream.io/embed?token=7ec777dd-5b07-4b52-b92e-3919f9ee733c' (browser_source)
21:33:09.641: - source: 'GZ Logo' (group)
21:33:09.641: - filter: 'Scroll' (scroll_filter)
21:33:09.641: - filter: 'Color Correction' (color_filter)
21:33:09.641: - source: 'PWD by Gamezon' (image_source)
21:33:09.641: - source: 'powered by gamezon.io' (text_gdiplus_v2)
21:33:09.641: - source: 'Video Capture Device' (dshow_input)
21:33:09.641: - filter: 'Color Correction' (color_filter)
21:33:09.641: - filter: 'Sharpen' (sharpness_filter)
21:33:09.641: - scene 'Standby':
21:33:09.641: - source: 'Game Capture 2' (game_capture)
21:33:09.641: - source: 'Display Capture 2' (monitor_capture)
21:33:09.641: - source: 'Text (GDI+)' (text_gdiplus_v2)
21:33:09.641: - filter: 'Scroll' (scroll_filter)

flickering was never an issue and the desktop source is disabled, it even shows the disabled icon in the screenshot.
 

hash

New Member
Applying all that was suggested didnt improve the situation however since you mentioned storage i found something quite baffling.
I let it record to a usb thumb drive (usb 3.1 128GB drive that can sustain 300MB/s writes) and in 10 minutes of recording only 30 frames were skipped.
I am baffled. What's going on here ?
 

carlmmii

Active Member
As mentioned, the drive that OBS is recording to can be a bottleneck that gets reported as encoding lag.

Total throughput isn't the actual metric of interest. It's latency for block writing. If your SSD controller can't keep up, then it won't meet frame timing. This can be especially problematic if an SSD is full, or in the case of... say... a QLC intel 660p above 50% capacity, it's having to re-write blocks in 4-bit precision mode.
 

hash

New Member
intel drive is indeed qlc but i seriously doubt it can't sustain an average of 50mbit/s write stream.
that aside, i have another nvme drive from kingston, a 500GB drive and these are the bench results.
recording to this drive causes overloads just like before
kingston-nvme.png


now comes the really baffling part:
I decided to try to record to my old sata boot drive (120gb adata sata ssd)
recorded for over 10 minutes, about 50.000 + frames with zero frames skipped. no overloading.
perfect record.

I know this no longer relates to obs but what's going on here ?
 

rockbottom

Active Member
Cool, now that you're sorted out take a look at the links below. CoreAudio upgrade & even more flexibility with your GPU/NVENC via StreamFX.

BTW, you should still fix those scenes.


 

hash

New Member
Cool, now that you're sorted out take a look at the links below. CoreAudio upgrade & even more flexibility with your GPU/NVENC via StreamFX.

BTW, you should still fix those scenes.


thanks a lot, didnt know about those !
 
Top