Bug: Optical Flow and M1 Max
Hi,
I am having a consistent bug in which optical flow on clips renders improperly on my M1 Max Macbook Pro. This occurs on both .mp4 and ProRes clips during timeline renders and exports. This bug appears to have been around for some time. Unless fixed, I cannot use my M1 machine on commercial projects.
M1 Max, 64GB memory
Version 22.0.0 (Build 169)
Thanks!


This issue has been fixed in the latest version (v22.3) of Premiere Pro.
-
Felipe Beuren commented
Finally! here is working fine
-
Chris Davies commented
So far, once updating, the glitch issue seems to be gone. Can anyone else confirm if there is no more glitching for them?
-
Dennis Giancarlo Santa Cruz Villegas commented
Any update Fergus? We are all still waiting :/
-
Andrew Hakim commented
Yes, please let us know asap. My colleagues and I deal with glitching issues constantly.
-
Rob Claisse commented
Any update Fergus?
Over a month ago you did say "I'll provide an update no later than this time next week."
Premiere is kind of useless for those of us that use optical flow on most projects. -
Luis Azcona commented
VBR 2 PASS seems to solve this for me - but it is added time and strain on laptop. Just throwing that in there in case it's helpful for the tech team. anxiously waiting for updates too.
-
Luis Azcona commented
just bought my m1 macbook pro. This issue just hit me too. waiting.
-
Bismarck Rojas commented
Still waiting....
-
Robert Röglin commented
Hello any news about the update, I am waiting anxiously for it. I urgently need to export a project.
-
Steven Probets commented
Thanks for the response Fergus! It really is appreciated to know people are listening. I found it still appears if I use Rosetta Premiere but export the sequence to Media Encoder for encoding. That was a couple of months ago though. Not sure as of now, as I won't touch the M1 version until this is fixed. I always use Optical Flow but would love to use the power of my £4000 MacBook Pro :(
-
Chris Davies commented
So is this issue ever going to be fixed? Extremely frustrating.
-
Randy Rubin commented
How is this not listed as a known bug in the 22.2 release?
-
Steven Probets commented
It's absolutely infuriating and basically renders using Premiere with M1 capabilities useless and unusable.
-
Gilly commented
I'm still seeing this bug. Plays fine in the timeline but glitches are present on exports to mp4 and ProRes with or without 'render with previews' selected.
Mac M1 Max.
-
Randy Rubin commented
Intel mode is still buggy and cuts performance significantly, causing lag and crashes. Not a solution in a commercial environment.
-
Evan Schallack commented
I THOUGHT I WAS CRAZY OH MY GOD IVE BEEN DEALING WITH THIS ALL MONTH!
-
Bart Beckers commented
I have exactly the same configuration and exactly the same problem. It's a pity that it doesn't work, because it just worked fine two weeks ago....
-
Blake Alley commented
Same issue here but it seems to work correctly with the Intel version of Premiere. The bitrate on H.265 also only exports at 60% the target bitrate but that's a whole different bug. I can't remember if Apple Silicon-based Premiere introduces glitches on other types of interpolation but I feel like I remember it doing it on time remapping or some other effect.
-
Robert Röglin commented
Hi, I have the same problem.
When rendering videos with optical flow it adds a kind of glicht that makes the videos unusable. Unfortunately I am currently working on a project where it is very useful, so I have to remove the optical flow or just use Davinci Resolve to make the videos with optical flow and reimport in Premiere.I've also had a similar problem with alpha channel files, and with graphics exported from After Effects for use with the Essential Graphics panel.
When using the intel version, it's a little better but I've had it not recognize After Effects compositions in Premiere.
I hope this can be solved soon, because otherwise the software is unusable for this kind of projects. And at this point exporting an XLM for use in other software and readjusting everything would be an incredible waste of time.
-
Antoine Autokroma.com (Independent Developer of AfterCodecs, BRAW Studio, PlumePack, Influx) commented
Ok thanks for testing ! It was a way to troubleshoot the issue, if it works in Rosetta Intel mode then the Adobe developers can better know where the issue is from