Premiere Pro 22.0 - Preview window tearing (V-sync). Need to be fixed.
Hi!
I've heard I am not the only one to have this issue. Preview window in Premiere Pro 22.0 is terribly tearing. Like some kind of V-sync bug. It's not there on ver. 15.1.0. Though it's still has bugs.
I have read everything. I turned on/off/what ever else V-sync in my Nvidia control panel for Premiere. Turned on/off GPU for previews in proj settings. Forced the system to use different video adapters for Premiere. Nothing. Tearing. Even on pre-rendered clips. Even without any effects applied. On Full resolution, "High quality" preview settings. No matter if it's Low-res HD footage or heavy 4K vids.
If I open the same preview file from Adobe previews folder it runs OK. Exported video is OK. But it terrible to work. I can't say, if footage is OK, until I export it. And I normally add some glitches to my video transitions. How do I know, is it my glitch or a bug?
Definitely needs to be fixed. Check out attached file for an example please.
BR, Anton.
Gigabyte Aero 2021, 11th gen i7, 64 Gb RAM, RTX 3060. Latest drivers. Nvidia Studio driver.

-
Anton Chernyshov commented
Guys, if you see it and it's important, please, VOTE for it!!!!
-
Anton Chernyshov commented
Any news on fixing tearing? WIth new 22.3.1. version of Premiere nothing changed. It is still terribly tearing. Noone is paying attention to it. I've heard that even MacBooks M1 have the same issue.
-
Anton Chernyshov commented
Unfortunately, turning V-sync in NVidia control panel doesn't work for me. Playback tearing is still there.
-
Grant Van Zutphen commented
I've had this problem too however turning on V-sync in my Nvidia control panel for Premiere solves it each time. FWIW, this setting defaults back to Off each time you update your GPU driver after doing a clean install. I'm always having to go in and manually reset it from Off to On.
-
Anton Chernyshov commented
Hi, David!
Thanks for your answer so much, really appreciate that! Sure, I will spend all the time neccesary to answer any quastions and to fix this bug for me and other guys out there.
I can provide you with full specs of my machine. I have just switched to it from older laptop and was so disappointed that I didn't get better quality workflow.- How many monitors are you running in your configuration?
Only one. My original built-in monitor, it's OLED 60 Mhz Samsung panel SDC4143 of my Gigabyte Aero 15 OLED book. Check out attachment for full specs.
- Do you use Transmit?
Since I don't use any external video output device, no.
- What are the native resolution(s) and scale(s) and refresh rate(s) of your monitors?
Original resolution is 3860 X 2160. Win 10 scales it to 250% which is a recommended option. Refresh rate is fixed to 60 Mhz.
- What color bit depth(s)?
It's 10 bit depth.
- What's a typical footage frame rate in your workflows?
Normally I work with 60 fps footage from Sony A73. Also HD and 4K 60 fps footage from DJI Mavic Pro and Air 2S. My final sequence is usually 30 fps for youtube (sport tutorials).
I see tearing in both 60 fps and 30 fps sequence previews, though 60 fps look much smoother, but still have the same tearing. 30 fps previews are really unsmooth for some reason, by the way. And tearing is there on both pre-rendered and unrendered previews. It's definitely something related with the way video is sent to the display rather than performance issue. And you are right, it shows up usually when obects are moving fast horizontally. Like in my first message here (see 1st message attachment) the blue kite it flying rapidly.
Let me know if you need more details. I believe that my this Gigabyte Aero is often used by creators as a tool, so I think it will be useful for many of us.I am attaching my display specs, as well as built-in adapter and my Nvidia specs.
Cheers, Anton.
-
David Simonton commented
Hi, Anton; you are not alone, and it's also true that the character and frequency of the "tearing" bugs would have changed with version 15.2 forward.
In 15.2 we changed the default display technology on Windows from OpenGL to DirectX, though if you search the web for "Premiere Pro tearing" you'll see that people also experienced tearing issues with OpenGL.
With DirectX, we can run display rates higher than a monitor's refresh rate, which can cause these tearing issues on footage (most commonly) with rapid horizontal motion. But we've also observed that some environments run into tearing issues more pronounced than on other environments. On my primary test system, I can see it on some footage if I'm running a Transmit monitor, or if I have my PGM or SRC panels maximized to fill the full screen, but I don't notice the tearing when my PGM and SRC monitors are at their standard workspace size. Other testers at Adobe can see the tearing even at default scaling in both Pgm and Src panels.
And I have seen that force enabling v-sync on my primary test system will cause tearing issues to return to the way they behave prior to 15.2, though I think this hasn't proven universally true.
I am using a High DPI, 4k monitor, and I've noticed that the bit depth (8-bit vs. 10-bit) can sometimes affect tearing. It can also potentially be affected by footage/sequence frame rates, driver version, the specific adapter/GPU, the monitor, the refresh rate, supported resolution(s), monitor scaling, and maybe settings in the NVidia/AMD control panel (like forcing vsync).
It is a display-only issue, and you wouldn't see these tearing artifacts in rendered media, which I know is small comfort. We might be able to fix the display issue or reduce its occurrence by forcing v-sync, but this would also impact performance, and the impact & consequences aren't well understood, because of the possible combinations across all user configurations.
Let me ask you a few follow-up questions if you get some time to answer them:
- How many monitors are you running in your configuration?
- Do you use Transmit?
- What are the native resolution(s) and scale(s) and refresh rate(s) of your monitors?
- What color bit depth(s)?
- What's a typical footage frame rate in your workflows?That information, along with the knowledge of your RTX3060, would probably let me reconstruct your setup, and maybe offer a mitigation strategy for now.