TexelGuy
New Member
The original poster of this thread @wiliextreme tested this on Linux as well and saw the same behavior, so I don't think Windows is to blame here.
Interval stutter / jitter / duplicated frames bug - workarounds
- Thread starter wiliextreme
- Start date
ciinTri
Member
I think he was implying that he tested it on a "Bootable USB Drive", so someone experiencing these stutters need to confirm this with actually installing Linux.
TexelGuy
New Member
There's no difference between an Ubuntu partition on a USB drive vs on an internal drive. It's still Linux. You can't boot into Linux without installing it somewhere, and a USB drive can be used to do that as well.
TexelGuy
New Member
Unless you're talking about the "live" Ubuntu that you can access before installing it, but I think it should be very obvious that you shouldn't use that to test OBS, because it will be lacking GPU drivers. I doubt that's what he was talking about.
TexelGuy
New Member
Fair point, I assumed it was an installed copy on a USB drive because it seemed obvious you're not supposed to use the live session version for this kind of thing.
Unfortunately, wiliextreme seems to be inactive, we might not be able to get a reply from him. You're right that we need other people to test it on Linux. OBS is on macOS as well, so maybe someone who has a Mac can test it.
wiliextreme
New Member
@TexelGuy @ciinTri
To clarify, when testing on Linux, I only booted live Ubuntu from pendrive. I didn't bother with full HDD install because I only wanted to quickly check if it is windows-only bug or not. The stutter at regular intervals was still present so I assumed it is a bug inside OBS or some library used by it. I suspect Linux installed on HDD would give the same result, but didn't try it by myself.
To clarify, when testing on Linux, I only booted live Ubuntu from pendrive. I didn't bother with full HDD install because I only wanted to quickly check if it is windows-only bug or not. The stutter at regular intervals was still present so I assumed it is a bug inside OBS or some library used by it. I suspect Linux installed on HDD would give the same result, but didn't try it by myself.
Hey guys, i've been reading this post past few days and i have encountered an issue with my streaming + gaming PC with "frame pacing" at least thats what i think it is.
Long story short i have Elgato 4k Pro capture card and i use OBS on my gaming PC to fullscreen project to capture card, when im not using OBS my game works really smooth, precise. As soon as i open OBS and cast a screen to capture card the game still has high fps, low frame times but its not as smooth as before, it feels "heavy" if you know what i mean.
Anyone else had similar issues in the past?
Long story short i have Elgato 4k Pro capture card and i use OBS on my gaming PC to fullscreen project to capture card, when im not using OBS my game works really smooth, precise. As soon as i open OBS and cast a screen to capture card the game still has high fps, low frame times but its not as smooth as before, it feels "heavy" if you know what i mean.
Anyone else had similar issues in the past?
PaiSand
Active Member
Windows. Check on the display settings.
aftrshck
New Member
This doesn't give you exact numbers, usually something like 119.96424 or 59.99432 etc.
I heard people are using some custom software in order to get exactly 120.000/60.000 or at least get really close it.
wiliextreme
New Member
@TexelGuy @ciinTri
Just realized I might have been wrong about Linux having this issue. I don't remember if I actually recorded any actual video while on Linux or maybe I just noticed interval stutter on OBS preview and assumed it would be also on recordings (which may not be true as proven by Elgato Camlink which stuttered only on preview).
So this bug may or may be not present on Linux, not sure, don't have time right now to check it again but wanted to clarify that if someone else would like to test it.
Just realized I might have been wrong about Linux having this issue. I don't remember if I actually recorded any actual video while on Linux or maybe I just noticed interval stutter on OBS preview and assumed it would be also on recordings (which may not be true as proven by Elgato Camlink which stuttered only on preview).
So this bug may or may be not present on Linux, not sure, don't have time right now to check it again but wanted to clarify that if someone else would like to test it.
aftrshck
New Member
I did some testing on CachyOS (Arch Linux with both Wayland / X11 display protocols) and results i got weren't really good in my case (i7 8700 and RTX 2060 Super).
While i didn't notice any interval stutter at all (i even forced FPS/display refresh rate mismatch in OBS to get it), the recordings were really choppy (frame drops/encoding lag?) and overall game/OBS performance is just horrendous compared to Windows.
Linux uses completely different techniques for display/window capture + doesn't have game capture at all since you are running things through Proton. It looked to me like they are not very optimized for OBS or Nvidia/Intel hardware (had constant 75-80% GPU/CPU load while windows barely reached 45-50%).
Could be running flawless on AMD but i can't test that sadly.
While i didn't notice any interval stutter at all (i even forced FPS/display refresh rate mismatch in OBS to get it), the recordings were really choppy (frame drops/encoding lag?) and overall game/OBS performance is just horrendous compared to Windows.
Linux uses completely different techniques for display/window capture + doesn't have game capture at all since you are running things through Proton. It looked to me like they are not very optimized for OBS or Nvidia/Intel hardware (had constant 75-80% GPU/CPU load while windows barely reached 45-50%).
Could be running flawless on AMD but i can't test that sadly.
aftrshck
New Member
If you are feeling like recording on Linux, i highly suggest this software: https://flathub.org/apps/com.dec05eba.gpu_screen_recorder
Way better performance than anything i've seen on Windows including OBS.
Way better performance than anything i've seen on Windows including OBS.
RTSS should work just fine, but it won't solve the issue. i've tried.
aftrshck
New Member
Oh yea, i tried both RTSS and CRU now. Didn't help much :(
Also, found this amazing software recently while searching for OBS alternatives:
GitHub - kebby/Capturinha: A tool for real time screen and audio capture on Windows, using NVIDIA's NVENC and with an emphasis on performance, correctness (eg. frame rate stability) and configurability. Mostly made for demoscene productions but you c
A tool for real time screen and audio capture on Windows, using NVIDIA's NVENC and with an emphasis on performance, correctness (eg. frame rate stability) and configurability. Mostly made for d...
github.com
It doesn't have much options and just records your current screen size/refresh rate, but quality and performance is amazing + it doesn't have any stutter no matter how long you record with it.
Shvok
New Member
Sorry for the bump.
I believe I have found a solution, at least with the use of a capture card. I experienced this issue a while back and even made a post on it, then figured out that enabling 'Buffering' on the capture card fixed it.
I am currently using an AverMedia GC553G2 (HDMI 2.1), and running a monitor in native 1440p 240Hz using loop-through (no cloning because I don't like latency). I was recently messing around with CS2, and during my tuning, I disabled fullscreen optimizations on the game exe. As I was playing a DM, it hit me, what if the emulation that Windows does by default with FSO is the reason that the "Buffering" option in OBS has to be enable? So I went in to the capture card settings in OBS and changed buffering from 'Enabled' to 'Disabled'.
I set OBS recordings to "use stream encoder" so I can record exactly what my stream would see. I then did some recordings and testing with, CS2, QuakeLive, Quake Champions, DOOM Eternal, and Cyberpunk 2077 - All with the "Disable Fullscreen Optimizations" box checked on the respective exe's. After hours of testing the issue was gone! I have been recording and testing ever since and the 60FPS frame pacing issue seems to be fixed.
I'm on Windows 11 Pro 24H2 build 26100.6584 with Windows Feature Experience Pack 1000.26100.234.0
My capture card configuration in OBS is as follows:
- Resolution: 2560x1440
- FPS: 60 (because I am streaming at 60FPS)
- Video Format: Any
- Color Space: Default
-Color Range: Default
Buffering: Disabled
To disabled Fullscreen Optimizations you will need to do it on each of the games exe's: https://imgur.com/a/XPNRVyX - So with the box "checked" it will be disabled. By default it is enabled (the box is unchecked).
Without getting too into it. What FSO in W10/11 does is runs the game in fullscreen-window, but "emulates" Fullscreen Exclusive. This also changes the flip-model that is used. Disabling Fullscreen Optimization (the box is checked) makes the game run in Fullscreen Exclusive mode. Where the GPU is communicating directly with the game render, and not going through a WDM emulation layer. This also changes the flip-model back to the "legacy" FSE model. If this does indeed fix it consistently for others, suspect that it is that 'emulation' layer that Windows is doing is the reason for the frame pacing inconsistency. With FSO, Windows is attempting to lower latency. Instead it seems to be causing frame pacing issues.
I'm really curious to have others with this issue, specifically with a capture card, to test this as well! So far it's been clean for me. If that changes I will report back.
I believe I have found a solution, at least with the use of a capture card. I experienced this issue a while back and even made a post on it, then figured out that enabling 'Buffering' on the capture card fixed it.
I am currently using an AverMedia GC553G2 (HDMI 2.1), and running a monitor in native 1440p 240Hz using loop-through (no cloning because I don't like latency). I was recently messing around with CS2, and during my tuning, I disabled fullscreen optimizations on the game exe. As I was playing a DM, it hit me, what if the emulation that Windows does by default with FSO is the reason that the "Buffering" option in OBS has to be enable? So I went in to the capture card settings in OBS and changed buffering from 'Enabled' to 'Disabled'.
I set OBS recordings to "use stream encoder" so I can record exactly what my stream would see. I then did some recordings and testing with, CS2, QuakeLive, Quake Champions, DOOM Eternal, and Cyberpunk 2077 - All with the "Disable Fullscreen Optimizations" box checked on the respective exe's. After hours of testing the issue was gone! I have been recording and testing ever since and the 60FPS frame pacing issue seems to be fixed.
I'm on Windows 11 Pro 24H2 build 26100.6584 with Windows Feature Experience Pack 1000.26100.234.0
My capture card configuration in OBS is as follows:
- Resolution: 2560x1440
- FPS: 60 (because I am streaming at 60FPS)
- Video Format: Any
- Color Space: Default
-Color Range: Default
Buffering: Disabled
To disabled Fullscreen Optimizations you will need to do it on each of the games exe's: https://imgur.com/a/XPNRVyX - So with the box "checked" it will be disabled. By default it is enabled (the box is unchecked).
Without getting too into it. What FSO in W10/11 does is runs the game in fullscreen-window, but "emulates" Fullscreen Exclusive. This also changes the flip-model that is used. Disabling Fullscreen Optimization (the box is checked) makes the game run in Fullscreen Exclusive mode. Where the GPU is communicating directly with the game render, and not going through a WDM emulation layer. This also changes the flip-model back to the "legacy" FSE model. If this does indeed fix it consistently for others, suspect that it is that 'emulation' layer that Windows is doing is the reason for the frame pacing inconsistency. With FSO, Windows is attempting to lower latency. Instead it seems to be causing frame pacing issues.
I'm really curious to have others with this issue, specifically with a capture card, to test this as well! So far it's been clean for me. If that changes I will report back.