I did. The monitor which gave me the best results is a native 1080p 60 Hz. The other one is a 1440p 144 Hz with G-Sync.
Yes, I think it's unrelated. But this microstutter happened every 30 to 60 seconds in my 1440p monitor operating at "60" Hz because it was actually updating the screen at 59.95 Hz instead of true 60 Hz like the 1080p monitor.
May I ask how many monitors in total you tested with? I am guessing not too many, but the more you tested with, the more "ammo" it gives us.
I only own those two monitors. Using CRU to fix the refresh rate to 60 Hz did help me eliminate the microstuttering I had every 30 to 60 seconds.
Ah well then somebody needs to grab 2 other monitors to test with. There is a remote chance that our monitors are sometimes not reporting the correct refresh rate to Windows which in turn messes up OBS. Yes, I know the odds are astronomically low, but that is why this thread will be staying up for a long time. We are trying to find crazy obscure solutions at this point.
I don't want to sound stupid, but could you condense your 2 paragraphs into concise points on 1. What you think is going wrong and 2. How to fix it?
But what if my monitors were bought before variable refresh rate monitors were in existence?
Only these apply to me because I had 0 issues before 2018.
Which is exactly why it shouldn't be the end-user who works on this. OBS developers need to go after this bug using all tools at their disposal. That includes talking to a DirectX expert at Microsoft about this, and working together to solve this.
It's the EDID of that monitor that has been the problem even if it was purchased before VRR's hit the market. Like you said....users shouldn't have to make corrections on this level.
It's open source. If anyone has the coding experience to compile it into the Universal Windows Platform to see how it responds over the Desktop Composition, then they can just have at it. Some apps, including this one, are still using DirectShow, which was replaced by Media Foundation. The question is does the same stuttering happen in the Streamlabs version? That's why I said there are so many variables here....but this is an awesome discussion that has to happen going forward. The May 2019 update will change things even further with Windows 10 and UWP.
But as I said, I had 0 problems before 2018. So while some people can blame the monitor, I can only blame OBS and/or Windows. It truly is fascinating that after so many posts on this thread, there is not 1 developer willing to speak. I understand that this is open source, and it is all volunteer operated. But you would think there would be at least 1 person brave enough to tackle a real challenge instead of the usual posts that come through here with people trying to stream higher resolutions/fps on a low-end computer.
I will be shocked if this actually fixes anything though. Windows has had issues forever now related to refresh rates and/or dual monitor setups. Heck, what about the bug where if you only have 1 application open and it is fullscreen, you can't alt tab out to your desktop. You must have at least 1 other item open on your primary monitor if you want to see your taskbar on the primary monitor. This is apparently considered a "feature", so good luck ever having it fixed. I wouldn't doubt if this preview stutter is a symptom of some other "feature" that Microsoft will never fix.
But did you try on an actual 60hz panel? For complete testing we can't just lower the refresh rate on a monitor, we need to see what happens on a bare-bones monitor.
