koala
Active Member
Count me in the people that have been just living with it. I'm satisfied when I look into my logs and I see no lost and lagged frames being reported. I also don't "see" any when I look at my own videos. If there is stutter or lost frames even then, it's good enough for me and I guess it's beyond my control. I admit that's probably what you mean with "willing to deal with it" - I'm not curious enough to do any deeper investigation into this. It's very time consuming to debug, and in the end I will probably find out I can do nothing about it. This is not worth it.
As far as I remember, someone on the forum found out such stutter can result from a small clock difference between OBS (better: the fixed 60 fps scheme of the video) and the screen refresh rate, because often the screen refresh rate isn't exactly 60 Hz but actually slightly less. This also applies to me. I have a 120 Hz monitor, I configured 120 Hz in Windows settings, but Windows says afterwards refresh rate is 119.97 Hz. If I tell OBS to capture with 60 fps, it's supposed to drop every other frame to get to 60 from 120. The game I'm capturing is vsync'd to 119.97 Hz, so there are just 119.97 / 2 = 59.985 frames being generated, so every 1/(60-59.985) = 66.66 seconds there is one duplicated frame if OBS is really capturing exactly 60 fps and the game is really rendering just 59.985 frames.
I said the game actually renders with 119.97 Hz, so this frame isn't actually being duplicated but pulled from a frame that's expected to be dropped if the refresh rate was really exactly 120 Hz. But this frame is out of sync, because it is generated for a presentation time 16.6 ms / 2 = 8.3 ms too early and the next frame is for 8.3 ms later but actually shown 16.6 ms later, which can be visible as stutter. But that's just for 1 frame.
This is "good enough" for me, and if there is really that 1 duplicated or out of time frame every minute (I'm unable to perceive this), I can live with it.
As far as I remember, someone on the forum found out such stutter can result from a small clock difference between OBS (better: the fixed 60 fps scheme of the video) and the screen refresh rate, because often the screen refresh rate isn't exactly 60 Hz but actually slightly less. This also applies to me. I have a 120 Hz monitor, I configured 120 Hz in Windows settings, but Windows says afterwards refresh rate is 119.97 Hz. If I tell OBS to capture with 60 fps, it's supposed to drop every other frame to get to 60 from 120. The game I'm capturing is vsync'd to 119.97 Hz, so there are just 119.97 / 2 = 59.985 frames being generated, so every 1/(60-59.985) = 66.66 seconds there is one duplicated frame if OBS is really capturing exactly 60 fps and the game is really rendering just 59.985 frames.
I said the game actually renders with 119.97 Hz, so this frame isn't actually being duplicated but pulled from a frame that's expected to be dropped if the refresh rate was really exactly 120 Hz. But this frame is out of sync, because it is generated for a presentation time 16.6 ms / 2 = 8.3 ms too early and the next frame is for 8.3 ms later but actually shown 16.6 ms later, which can be visible as stutter. But that's just for 1 frame.
This is "good enough" for me, and if there is really that 1 duplicated or out of time frame every minute (I'm unable to perceive this), I can live with it.
