Recorded videos sometimes start stuttering after a minute or so then get worse with time

koala

Active Member
There can be a difference between the Windows desktop resolution and the game you play in fullscreen resolution. According to your OBS log, Windows definitely reports a desktop resolution of 2560x1440 according to two different entries in your OBS log:


Code:
15:36:41.072:       output 0:
15:36:41.072:         name=Acer XB273K S
15:36:41.072:         pos={0, 0}
15:36:41.072:         size={2560, 1440}
15:36:41.072:         attached=true
15:36:41.072:         refresh=144
15:36:41.072:         bits_per_color=8
15:36:41.072:         space=RGB_FULL_G22_NONE_P709
15:36:41.072:         sdr_white_nits=80
15:36:41.072:         nit_range=[min=0.098800, max=445.760986, max_full_frame=351.276398]
15:36:41.072:         dpi=96 (100%)

and

15:36:44.137: [duplicator-monitor-capture: 'Display Capture'] update settings:
15:36:44.137:     display: Acer XB273K S (2560x1440)

You can check and fix this if you call Windows settings→System→Display and check the resolution, for example according to the demo here: https://www.cnet.com/tech/computing/6-display-settings-you-should-be-using-in-windows-10/ In that picture, instead of 1366x778 it must show 3840x2160 on your system. It currently will show 2560x1440 on your system, according to OBS. Set this setting to 3840x2160, and if text appears too small with this, use a scaling of 125% or 150% instead of 100%.

However, in every game you can also set a resolution, and here you set 3840x2160 for your game according to this, so you actually play and capture your game in 4k:
Code:
15:37:01.363: [game-capture: 'Game Capture'] vk_shtex_init_d3d11_tex: OBS requesting VK_FORMAT_B8G8R8A8_UNORM texture format. capture dimensions: 3840x2160

Your performance issues might come from the two different capture sources you use: one display capture source and one game capture source, both capturing the same thing as soon as you're playing the game. The display capture source doesn't stop working if the game switches to its fullscreen mode. To remedy this, delete the display capture source. Disabling is not enough, you have to delete it. Your OBS preview will go empty, so to have something on the preview, add a window capture source of something you use for calibrating, but not a display capture - this might stomp on the game capture.

Another thing: There is encoder overload. Try a lower preset in settings→Output→Recording. Instead of P5, try P4 to P1 and see what happens. Also try different Tuning values, and try single pass mode. Dont be confused with these settings being descibed as lower quality - since you're using a quality based rate control (CQP), this is actually meaning "bigger filesize". You will not actually perceive a lower quality, only slightly larger file size. That's quality for steaming, so the description, but not for recording as in your case, where it will mean larger filesize.
 
Hi,
Yes again im aware of resolutions and my windows desktop is in full native 4K, aswell as the games im playing. Im not using 1440p anywhere on my setup, so no idea where thats coming from, its only obs logs and display capture that mention it.
Ok what your saying about the capture sources is interesting - so if im capturing gameplay footage, either using the full screen or specific window capture modes - i should actually delete the display capture one? And only re-enable this if im capturing windows desktop footage for example?
Right yeah I see what you mean regarding the settings aswell, thats interesting thanks for that, ill play with those settings and do some more testing, its just the way it is at the moment I can get perfect videos even with the settings i was using, it only happens sometimes - so i can think its gone away, do a 30 minute video then find out its gone choppy after a few minutes.

But again - as far as the 1440p resolution reporting ive no idea where its getting that from, everything on the system is setup for 4K, its only obs that mentions it and ive no idea why - its all confirmed 100% everything is running in full native 4K.

Thanks for your suggestions.
 

koala

Active Member
But again - as far as the 1440p resolution reporting ive no idea where its getting that from, everything on the system is setup for 4K, its only obs that mentions it and ive no idea why - its all confirmed 100% everything is running in full native 4K.
Could you please post a screenshot of your Windows setting Settings → System → Display? Where the Windows desktop resolution and scaling is visible? I'd like to understand where the difference between Windows and OBS reporting might come from.
 
I was just posting the screenshot but it was saying too large, although I think I see what is happening, the resolution is 3840x2160 but in windows display settings the scaling is set to 150% ( recommended ) and I just tried that on 100% and it does indeed show as 3840x2160 in display selection now aswell, so im assuming its the same in the logs - although this wasnt what was causing the original problem its still good to know where the reporting came from, obviously games etc were still using full 4k but this is obviously what was causing obs to see the display as 1440p.
I have just done another recording which was also fine, after I followed your advice of temporarily deleting the display capture source.
 

koala

Active Member
3840x2160 with 150% scaling makes sense: 3840 / 1.5 = 2560. However, it's reported by your log your scaling is 100% not 150%. It seems, there is a difference between Windows 10 and 11. Under Windows 10 it seems the "scaled" (virtually smaller) resolution is reported by the system calls and scaling always 100%, while under Windows 11 (which is what I use) always the configured native resolution is shown and the real scaling value (150%), and because of this I'm unable to see on my system what you see on your system.
 
Ok yeah that's very interesting. So it is how OBS is seeing the scaling on windows 10.
Again this wasn't what was causing the original problem anyway but its good we have got to the bottom of what was causing it to report that as its always bothered me.
As for the stutters sometimes, i've not had any now for a few short videos, and ill also keep the display source deleted while capturing gameplay video.
Is there any way to make OBS actually let me know during a recording, if it starts experiencing encoder lag? Then at least if it starts happening I can pause and look into it?
Thanks again.
 

rockbottom

Active Member
Changing the scaling in W10 does not change the monitor resolution. Guess again....

11:28:30.404: name=ROG PG259QN
11:28:30.404: pos={0, 0}
11:28:30.404: size={1920, 1080}
11:28:30.404: attached=true
11:28:30.404: refresh=60
11:28:30.404: bits_per_color=8
11:28:30.404: space=RGB_FULL_G22_NONE_P709
11:28:30.404: sdr_white_nits=80
11:28:30.404: nit_range=[min=0.098400, max=400.000000, max_full_frame=351.276398]
11:28:30.404: dpi=96 (100%)
11:28:30.404: id=\\?\DISPLAY#AUS25B5#5&32d63be9&2&UID4353#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
11:28:30.404: alt_id=\\.\DISPLAY1
11:28:30.406: output 1:
11:28:30.406: name=AVM 50v
11:28:30.406: pos={1920, 0}
11:28:30.406: size={1920, 1080}
11:28:30.406: attached=true
11:28:30.406: refresh=30
11:28:30.406: bits_per_color=8
11:28:30.406: space=RGB_FULL_G22_NONE_P709
11:28:30.406: sdr_white_nits=80
11:28:30.406: nit_range=[min=0.500000, max=270.000000, max_full_frame=270.000000]
11:28:30.406: dpi=168 (175%)
11:28:30.406: id=\\?\DISPLAY#PGM0002#5&32d63be9&2&UID4352#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
11:28:30.406: alt_id=\\.\DISPLAY2
11:28:30.407: output 2:
11:28:30.407: name=ASUS VG236
11:28:30.407: pos={-1920, 0}
11:28:30.407: size={1920, 1080}
11:28:30.407: attached=true
11:28:30.407: refresh=60
11:28:30.407: bits_per_color=8
11:28:30.407: space=RGB_FULL_G22_NONE_P709
11:28:30.407: sdr_white_nits=80
11:28:30.407: nit_range=[min=0.500000, max=270.000000, max_full_frame=270.000000]
11:28:30.407: dpi=144 (150%)
11:28:30.407: id=\\?\DISPLAY#ACI23F7#5&32d63be9&2&UID4356#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
11:28:30.407: alt_id=\\.\DISPLAY3
11:28:30.409: output 3:
11:28:30.409: name=fitHeadlessGS
11:28:30.409: pos={-5760, -505}
11:28:30.409: size={3840, 2160}
11:28:30.409: attached=true
11:28:30.409: refresh=30
11:28:30.409: bits_per_color=8
11:28:30.409: space=RGB_FULL_G22_NONE_P709
11:28:30.409: sdr_white_nits=80
11:28:30.409: nit_range=[min=0.500000, max=270.000000, max_full_frame=270.000000]
11:28:30.409: dpi=288 (300%)
11:28:30.409: id=\\?\DISPLAY#CLB1234#5&32d63be9&2&UID4357#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}
11:28:30.409: alt_id=\\.\DISPLAY4
 
It doesn't change the resolution at all, it changes the scaling of text, icons etc, the resolution is still 4K as are all the games you run on it, this is to do with how windows, by the sounds of it specifically windows 10, reports the scaling and how OBS interprets this.
 

rockbottom

Active Member
That's a pile of smokin' BS, just look at my post above. All monitors are working properly. (3) are scaled at different rates no less & resolution does not change. Keep believing that it's the OS or something else, I'm betting you haven't even tried going to Acer's support page, replacing the cable or done any troubleshooting at all.
 
I haven't got a fricking clue what your talking about - the resolution on the desktop, and in games is ALL native 4K - the windows resolution scaling does NOT change the resolution - it SCALES text and icons on the 4K resolution to make them easier to see, or else your text and icons appear tiny. Your still running in 4K resolution and playing games in 4K resolution if that's what your set in - as koala said above this is how windows 10 reports the scaling and how OBS interprets it. OBS sees it as 1440 due to the way windows 10 reports the scaling, again as koala said windows 11 doesn't do this.

Changing the SCALING in windows resolution doesn't change the resolution, if what your saying would be true then anyone running a 4K monitor with windows desktop scaling in use would ALL be running in lower resolutions - all your games would see a 1440 monitor, which they don't.
And a faulty cable or whatever else you want to blame it on would NOT only affect one single program when a myriad of others work perfectly.
If you continue to argue about this I will assume your trolling and therefore will not respond further.
 
If you have read the other posts - the reason that OBS recognizes this as 1440 when set at 4K native is due to using 150% resolution scaling on the windows display settings, which doesn't actually change your resolution - as your post above also proves. I'm assuming your on Windows 11, as koala above said this reports the resolution scaling to the system differently to windows 10 therefore OBS will detect and log the full native resolution aswell as report the correct amount of scaling in use. Windows 10 on the other hand reports this in a different way which means OBS picks up the scaled resolution instead of the native resolution, and also reports the scaling as 100%, regardless of what its set to.
Your post above even states the resolution doesn't change when using different scaling - which is exactly what i'm saying - it doesn't. It is an interaction between Windows 10 and OBS where OBS is picking up the scaled resolution from windows rather than the native resolution, but I have still been running in 4K the entire time.
 

rockbottom

Active Member
I ask because Nvidia limits 4k outputs on HDMI to 30FPS. Only Display Port will expose 60FPS+. The cable still could be damaged or not up to Spec, changing it out with a new cable might be all you need to do.
 
Yeah Display Port, Ye but if that was the case I wouldn't be able to run games in 4k @ 144hz, if the cable was out of spec etc. Yeah 3090 here aswell with only the one monitor connected.
 

rockbottom

Active Member
DP 2.0 was released after your monitor was produced, perhaps the cable that was supplied is an older spec. The cable should have the Spec on it. If it's not 2.0, you should replace it.


On 26 June 2019, VESA formally released the DisplayPort 2.0 standard. VESA stated that version 2.0 is the first major update to the DisplayPort standard since March 2016, and provides up to a ≈3× improvement in data rate (from 25.92 to 77.37 Gbit/s) compared to the previous version of DisplayPort (1.4a)
 
Last edited:
Top