Playback Is Stuttering (Going Crazy)

[SouthernKid]

Hi everybody,

So, after a whole day of pulling my hair out i can't, for the death of me, figure out what i should be doing other than what i did 1y ago. I have all my settings the same. I have tweaked, on, off, this, that. Still, to no avail have i gotten closer.

Could any of you 'Wizards' kindly look at my Log or tell me what's going on?
I find it very hard to believe my 4080 is burned. My games run fine.
NO lag, NO stutter. It's this dam app that's causing me some problem.

So, when I was previewing, I would notice stutters though none that were in game. So, I decided to hide the preview as its not always 100% accurate, from what I have noticed (sometimes it would lag but in the playback it showed no signs of it) and read that it takes resources. Still, the same problems.
I have also noticed a fascinating pattern, earlier today, though now it doesn't show (which is very strange, somehow I got rid of that timer). After around 1min15sec, there would be this crazy lag but then it would subside randomly (Used ACMIrage) for test. In smaller indie games my recording are such as bad. Yet, I repeat, my gameplay is fine. Not 1 Stutter or problem.

My head hurts and my back even more from spending over 6h trying to figure this out before coming here.
I can't understand, my settings are the same, so what's causing all these terrible, glitchy recordings which are as if I'm running Cyberpunk off a windows 98 with 4mb ram (that was a joke)

My log https://obsproject.com/logs/BBlkl76P8j7OSREU
Specs - 4080 ROG, Rog Wifi Z motherboard. Corei913k

 

[Clapfish]

BUMP

Gonna jump in on this as I just made an account to complain about the same thing.

I have a 4070 Super with Ryzen 7 7700 and an Asus Rog Strix B650E-E with 32GB RAM - everything runs sweet and smooth... EXCEPT OBS output on both stream and video.

The only 'solution' (actually not a solution just a workaround with the constant threat of stutter) is to match the OBS Video FPS setting with my monitor set at 60hz to almost (*almost*) exactly what the refresh rate really is, which according to displayhz.com is around 59.9986xx hz. To achieve this I've set a fractional FPS value in OBS of 599986 / 10000.

As a result of this, my last couple of streams have been stutter free; however, I still notice a pattern in GPU utilisation (which is most pronounced at the standard '60' FPS setting in OBS) where it will gradually increase to around 75-80%, then fairly rapidly fall to around 30% only to gradually climb again. The stuttering, as far as I've noticed through lots of testing, occurs at the high point, with some potential for local stutter in the preview (when enabled) around the low point.

I got the idea for trying a fractional FPS setting from a YouTube video I found on the issue: https://www.youtube.com/watch?v=eubBwFxWwzc which I believe you guys should already be aware of as, if memory serves, I found this video on an obsproject forum post some time ago when I started investigating the issue more thoroughly.

The problem is that, despite having had a couple of smooth 3-4 hour streams recently since adding the fractional value (no other settings in OBS or elsewhere [nvidia / windows] seem to affect this issue), if I'm unlucky enough to stream at the dreaded 'high point' of GPU utilisation as detailed above, I worry I'll have something ridiculous like an hour of stuttering.

I believe something is going on with OBS in the background relating to vsync and/or monitor refresh rates causing this weird wave in GPU utilisation which coincide with a horrible stuttering output from OBS.

Can someone explain what is going on under the hood and if there is a permanent workaround or solution to this issue?

So far I've only been streaming Sekiro with vsync on @ 60fps (native game lock) and a monitor capable of 180hz but set to 60hz because Sekiro stutters locally (i.e. on my screen while playing) if the refresh doesn't match the game. I have tried other games with recording and on stream briefly and encountered similar, regular intervals of smooth output, stuttering output, repeat - like clockwork. The intervals only vary depending on the fractional/integer FPS setting in OBS and the game framerate, as far as I can tell.

For example, I have a lot of VODs now on YouTube (from Twitch) showing regular ~10min smooth followed by ~2.5min stutter while I had 60fps set, and now some longer smooth outputs after switching to the fractional value.

Apologies if this isn't well written but I will be happy to clarify anything if/when required.

Any investigation / assistance from OBS devs would be greatly appreciated here, it's been weeks now of investigation on my end with only this temporary workaround (again, with the looming threat of streaming during a long stutter interval looming) found so far.

Cheers!

 

[rockbottom]

HAGS should be disabled.
22:35:00.011: HAGS Status: Enabled (Default: No, Driver status: Supported)

Try another capture method. Your audio buffered too but see how things go with HAGS disabled.
22:35:36.388: [game-capture: 'Game Capture'] attempting to hook fullscreen process: explorer.exe
22:35:36.388: [game-capture: 'Game Capture'] cannot capture explorer.exe due to being blacklisted

22:35:42.294: Max audio buffering reached!
22:35:42.294: adding 1044 milliseconds of audio buffering, total audio buffering is now 1044 milliseconds (source: Desktop Audio)
22:35:42.294:
22:35:42.317: Source Desktop Audio audio is lagging (over by 2144.35 ms) at max audio buffering. Restarting source audio.

 

[Clapfish]

Mm perhaps not related to my issue then... I will collect some info / logs and make a new post in due course for my particular issue, probably shouldn't have jumped in here :)

Edit: I definitely tried disabling HAGS for my issue as recommended in the YouTube vid I linked but that had no effect, for me at least.

I'll be monitoring to see how the OP gets on with this, and similarly I'd be interested to hear if he has similar results with the fractional FPS tinkering like I have.

 

[rockbottom]

^^

Correct, I didn't even bother to look at your post as there was no log.