60FPS recording looks "laggy/stuttery" / using 120FPS to supplement that

W

wadahailman

New Member
This issue has been happening to me for almost half a decade.

My first PC was a 5800x3d with a GTX 1080.
I'd be able to record 60FPS smoothly with no problems. It was smooth.

My second PC is a 7800x3d with a RTX 3070. From this point on, 60FPS recordings did not look smooth at all.
I had to change the recordings to 120FPS to make it look smooth.
I had a friend record on his PC, I7-13700k with a RTX 2070 Super. His 60FPS recording in the same game looked smooth.
He said my recordings were unwatchable. It looked like I was recording at 30FPS.

I recently upgrade my PC again.
I changed the ram and upgraded my GPU to a 5070ti.
The 60FPS still looks absolutely horrible.
I have tried the newest version of OBS and 27.2.2 which I prefer the basic layout, both not making a difference.
---
Setup
Games = Any game
Game FPS = I play uncapped, capping it does not change anything
OBS = Recording 1920x1080 - CQP 16 - Everything else default
GPU = RTX 5070ti - I was wondering if it was VRAM related so I upgraded because I was planning to anyways, no changes
CPU = AMD 7800X3D - Surely it's not CPU related?
RAM = DDR5 6000 - have tried a different pair of sticks, no luck
Using triple monitors but I've tried it with single and double with the same issue so I don't think it's monitor related

EXPO is enabled
PBO is enabled
Game mode is enabled
HAGS is enabled

I think I have tried every variant of those settings enabled and disabled with no luck.
I may have tried other things but these are the main things that I've touched and tried.

This is all I listed because I don't know what else could be causing the issue parts / setting wise.
---
I'd like to be able to record in 60FPS and have it look nice.
120FPS works but there is this occasional hiccup where OBS would just freeze when it's trying to stop the recording.
I'd lose all progress of whatever is recorded, even in MKV.

Does this issue ring a bell to anyone? It's kind of weird, I see similar issues but nothing to this exact extent.
 
Please review and follow directions on the pinned posts on this forum.
Also, make sure to watch the recorded video with a good video player like VLC.
 
0. Use the newest available version of OBS.
1. Display, Game and Window Capture all interfere with each other. Never put them in the same scene (Game, Desktop and TFT).
2. Multiple Game Capture sources are usually not needed, and can sometimes interfere with each other (Game). You can use the same Game Capture for all your games. If you change games often, try out the hotkey mode, which lets you press a key to select your active game. If you play games in fullscreen, use 'Capture any fullscreen application' mode.

Watch the video on your 60 Hz monitor.
 
qhobbes said:
0. Use the newest available version of OBS.
1. Display, Game and Window Capture all interfere with each other. Never put them in the same scene (Game, Desktop and TFT).
2. Multiple Game Capture sources are usually not needed, and can sometimes interfere with each other (Game). You can use the same Game Capture for all your games. If you change games often, try out the hotkey mode, which lets you press a key to select your active game. If you play games in fullscreen, use 'Capture any fullscreen application' mode.

Watch the video on your 60 Hz monitor.
Click to expand...
Same problem on newest version of OBS.
Video looks the same on 60hz monitor and also on laptop.

Let me try the second solution and deleting everything out except for one game capture.
---
Finished deleting all the other capture sources out.
60FPS recording still looks off for some reason. I'm not sure if it's my eyes messing with me but it looks a little choppy.
 
Last edited:
Please provide a new log file from the newest OBS version you have installed.
The older version isn't supported anymore as the codec have changed to support newest GPUs like the one you own.
Make sure to uninstall all the plugins that are not updated and/or compatible with latest version of OBS.
 
On top of the issues stated above, the monitor connected to your mobo (XG259QN) needs to be connected to the 5070. That monitor should also be running @ 60HZ not 240......

23:53:17.177: Initializing D3D11...
23:53:17.177: Available Video Adapters:
23:53:17.191: Adapter 0: NVIDIA GeForce RTX 5070 Ti
23:53:17.191: Dedicated VRAM: 3887071232
23:53:17.191: Shared VRAM: 3813664768
23:53:17.191: PCI ID: 10de:2c05
23:53:17.191: Driver Version: 32.0.15.9597
23:53:17.191: output 0:
23:53:17.191: name=25G64
23:53:17.191: pos={0, 0}
23:53:17.191: size={1920, 1080}
23:53:17.191: attached=true
23:53:17.191: refresh=240
23:53:17.191: space=RGB_FULL_G22_NONE_P709
23:53:17.191: sdr_white_nits=80
23:53:17.191: nit_range=[min=0.000000, max=603.698425, max_full_frame=603.698425]
23:53:17.191: output 1:
23:53:17.191: name=24B2H2
23:53:17.191: pos={-1920, 0}
23:53:17.191: size={1920, 1080}
23:53:17.191: attached=true
23:53:17.191: refresh=60
23:53:17.191: space=RGB_FULL_G22_NONE_P709
23:53:17.191: sdr_white_nits=80
23:53:17.191: nit_range=[min=0.500000, max=270.000000, max_full_frame=270.000000]
23:53:17.192: Adapter 1: AMD Radeon(TM) Graphics
23:53:17.192: Dedicated VRAM: 509464576
23:53:17.192: Shared VRAM: 3813664768
23:53:17.192: PCI ID: 1002:164e
23:53:17.192: Driver Version: 31.0.24002.92
23:53:17.192: output 0:
23:53:17.192: name=XG259QN
23:53:17.192: pos={1920, 0}
23:53:17.192: size={1920, 1080}
23:53:17.192: attached=true
23:53:17.192: refresh=240
23:53:17.192: space=RGB_FULL_G22_NONE_P709
23:53:17.192: sdr_white_nits=80
23:53:17.192: nit_range=[min=0.099800, max=426.000000, max_full_frame=351.000000]
23:53:17.193: Loading up D3D11 on adapter NVIDIA GeForce RTX 5070 Ti (0)
23:53:17.319: D3D11 loaded successfully, feature level used: b000
23:53:17.319: DXGI increase maximum frame latency success
23:53:17.325: D3D11 GPU priority setup success
 
Set OBS back to 60FPS until you get things stutter free. After you fix your configuration issue, if things are stabilized go back to 120FPS.

23:53:17.614: video settings reset:
23:53:17.614: base resolution: 1920x1080
23:53:17.614: output resolution: 1920x1080
23:53:17.614: downscale filter: Bicubic
23:53:17.614: fps: 120/1
23:53:17.614: format: NV12
23:53:17.614: YUV mode: 709/Partial
23:53:17.614: NV12 texture support enabled
23:53:17.615: Audio monitoring device:
23:53:17.615: name: Default
23:53:17.615: id: default
 
This is the current log. I pretty much stripped everything down and updated to the newest OBS.
I can't tell if my eyes are lying to me still but my 60FPS recording still looks a little choppy.

For context, before I did a full upgrade. I recorded 60FPS at 144hz and it looked pretty good to me.
Ever since upgrading, it just doesn't look right. I can't tell if that's because my eyes are so used to 240hz+ refresh rates that a 60FPS recording looks off to me but I swear it's not. I swear the recordings I see of other people recording in 60FPS looks better than mine.
 

Attachments

There had to be significant improvement now that your rig is not mis-configured?

I would relax that refresh rate & see if there's anymore improvement. Rig or the source you're using are suspect.

I would also work on your audio. It's messy, plugins failing & you're using device timing for both Discord & Spotify. I highly doubt both are arriving to OBS at precisely the exact same time or in sync with the video.

21:52:21.540: [win-wasapi: 'Mic/Aux'] update settings:
21:52:21.540: device id: {0.0.1.00000000}.{6c5924cf-1f8f-4b16-85c0-84bdbb3e8b41}
21:52:21.540: use device timing: 0
21:52:21.541: User selected new VST plugin: 'C:/Program Files/VSTPlugins/ReaPlugs/reagate-standalone.dll'
21:52:21.541: Failed trying to load VST from 'C:/Program Files/VSTPlugins/ReaPlugs/reagate-standalone.dll', error 126
21:52:21.541:
21:52:21.541: VST Plug-in: Can't load effect!
21:52:21.541: User selected new VST plugin: 'C:/Program Files/VSTPlugins/ReaPlugs/reaeq-standalone.dll'
21:52:21.541: Failed trying to load VST from 'C:/Program Files/VSTPlugins/ReaPlugs/reaeq-standalone.dll', error 126
21:52:21.541:
21:52:21.541: VST Plug-in: Can't load effect!
21:52:21.542: User selected new VST plugin: 'C:/Program Files/VSTPlugins/ReaPlugs/reaxcomp-standalone.dll'
21:52:21.542: Failed trying to load VST from 'C:/Program Files/VSTPlugins/ReaPlugs/reaxcomp-standalone.dll', error 126
21:52:21.542:
21:52:21.542: VST Plug-in: Can't load effect!
21:52:21.542: [Loaded global audio device]: 'Mic/Aux'
21:52:21.542: - filter: 'Noise Suppression' (noise_suppress_filter_v2)
21:52:21.542: - filter: 'Noise Gate' (vst_filter)
21:52:21.542: - filter: 'EQ' (vst_filter)
21:52:21.542: - filter: 'Compressor' (vst_filter)
21:52:21.593: WASAPI: Device 'Mic In (Elgato Wave:XLR)' [48000 Hz] initialized (source: Mic/Aux)
21:52:21.643: adding 42 milliseconds of audio buffering, total audio buffering is now 42 milliseconds (source: Mic/Aux)
21:52:21.643:
21:52:22.201: [win-wasapi: 'Spotify Audio'] update settings:
21:52:22.201: device id: {0.0.0.00000000}.{c4d08703-65ac-4fe8-a8f0-8f2c189cb642}
21:52:22.201: use device timing: 1
21:52:22.204: [win-wasapi: 'Discord'] update settings:
21:52:22.204: device id: {0.0.0.00000000}.{54c17d0c-66a7-4445-91f9-c3bd215bd667}
21:52:22.204: use device timing: 1
21:52:22.204: [WASAPISource::TryInitialize]:[{0.0.0.00000000}.{54c17d0c-66a7-4445-91f9-c3bd215bd667}] Failed to enumerate device: 80070490
21:52:22.204: WASAPI: Device '{0.0.0.00000000}.{54c17d0c-66a7-4445-91f9-c3bd215bd667}' failed to start (source: Discord)
21:52:22.208: Device for 'Audio Output Capture' source Desktop Audio is also used for audio monitoring.
21:52:22.208: Deduplication logic is being applied to all monitored sources.
21:52:22.208: [win-wasapi: 'Desktop Audio'] update settings:
21:52:22.208: device id: {0.0.0.00000000}.{7084f625-8ecf-437c-9a1d-94b3128fecbf}
21:52:22.208: use device timing: 0
 
Clean-up needed on aisle 5..
21:52:21.498: Encoder ID 'jim_nvenc' is deprecated and may be removed in a future version.
21:52:21.498: Encoder ID 'jim_nvenc' is deprecated and may be removed in a future version.
 
rockbottom said:
There had to be significant improvement now that your rig is not mis-configured?

I would relax that refresh rate & see if there's anymore improvement. Rig or the source you're using are suspect.

I would also work on your audio. It's messy, plugins failing & you're using device timing for both Discord & Spotify. I highly doubt both are arriving to OBS at precisely the exact same time or in sync with the video.

21:52:21.540: [win-wasapi: 'Mic/Aux'] update settings:
21:52:21.540: device id: {0.0.1.00000000}.{6c5924cf-1f8f-4b16-85c0-84bdbb3e8b41}
21:52:21.540: use device timing: 0
21:52:21.541: User selected new VST plugin: 'C:/Program Files/VSTPlugins/ReaPlugs/reagate-standalone.dll'
21:52:21.541: Failed trying to load VST from 'C:/Program Files/VSTPlugins/ReaPlugs/reagate-standalone.dll', error 126
21:52:21.541:
21:52:21.541: VST Plug-in: Can't load effect!
21:52:21.541: User selected new VST plugin: 'C:/Program Files/VSTPlugins/ReaPlugs/reaeq-standalone.dll'
21:52:21.541: Failed trying to load VST from 'C:/Program Files/VSTPlugins/ReaPlugs/reaeq-standalone.dll', error 126
21:52:21.541:
21:52:21.541: VST Plug-in: Can't load effect!
21:52:21.542: User selected new VST plugin: 'C:/Program Files/VSTPlugins/ReaPlugs/reaxcomp-standalone.dll'
21:52:21.542: Failed trying to load VST from 'C:/Program Files/VSTPlugins/ReaPlugs/reaxcomp-standalone.dll', error 126
21:52:21.542:
21:52:21.542: VST Plug-in: Can't load effect!
21:52:21.542: [Loaded global audio device]: 'Mic/Aux'
21:52:21.542: - filter: 'Noise Suppression' (noise_suppress_filter_v2)
21:52:21.542: - filter: 'Noise Gate' (vst_filter)
21:52:21.542: - filter: 'EQ' (vst_filter)
21:52:21.542: - filter: 'Compressor' (vst_filter)
21:52:21.593: WASAPI: Device 'Mic In (Elgato Wave:XLR)' [48000 Hz] initialized (source: Mic/Aux)
21:52:21.643: adding 42 milliseconds of audio buffering, total audio buffering is now 42 milliseconds (source: Mic/Aux)
21:52:21.643:
21:52:22.201: [win-wasapi: 'Spotify Audio'] update settings:
21:52:22.201: device id: {0.0.0.00000000}.{c4d08703-65ac-4fe8-a8f0-8f2c189cb642}
21:52:22.201: use device timing: 1
21:52:22.204: [win-wasapi: 'Discord'] update settings:
21:52:22.204: device id: {0.0.0.00000000}.{54c17d0c-66a7-4445-91f9-c3bd215bd667}
21:52:22.204: use device timing: 1
21:52:22.204: [WASAPISource::TryInitialize]:[{0.0.0.00000000}.{54c17d0c-66a7-4445-91f9-c3bd215bd667}] Failed to enumerate device: 80070490
21:52:22.204: WASAPI: Device '{0.0.0.00000000}.{54c17d0c-66a7-4445-91f9-c3bd215bd667}' failed to start (source: Discord)
21:52:22.208: Device for 'Audio Output Capture' source Desktop Audio is also used for audio monitoring.
21:52:22.208: Deduplication logic is being applied to all monitored sources.
21:52:22.208: [win-wasapi: 'Desktop Audio'] update settings:
21:52:22.208: device id: {0.0.0.00000000}.{7084f625-8ecf-437c-9a1d-94b3128fecbf}
21:52:22.208: use device timing: 0
Click to expand...
60FPS Video still looks the exact same as before.
Actual performance in game still the same.

I had those filters set up for my mic.
I do not use any plugins.
I do upload a profile or scene collection that I had saved before but let me try it with a new scene collection and the fixes you mentioned.

I appreciate the patient help a lot!
 
The Hardware-accelerated GPU scheduling ("HAGS") feature in Windows is currently known to cause performance and capture issues with OBS, games and overlay tools. We recommend disabling it via these instructions. Be sure to restart after disabling it.

AFAIK OBS renders the source based on the canvas FPS, so you need to make sure that your game is running at a constant even multiple FPS of the canvas FPS. Converting from 240 FPS to 60 FPS is pretty easy; 213-237 FPS not so much.

Try eliminating any frame rate conversion by setting your monitor to 60 Hz, capping your game 60 FPS, capturing at 60 FPS and then watching on a 60 Hz monitor.
 
You must log in or register to reply here.
Back
Top