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)
I am having tihs exact same problem and its driving me nuts. Adobe neet to sort this problem out ASAP> There is a workaround I believe and thtas to export it VBR 2 pass. Seems to work okay for me. Not ideal as its adds time but come on Adobe!
Same here! Creates really jerky curropt video.
Apple M1 Max
It completely cancels out me using Premeire M chip version!
Same problem for me with the lasted Macbookpro M1 max.
I'm experiencing glitches on my exports on almost each clip I used optical flow.
A real bumer 😞
Don't have an M1 but have had issues with Optical flow before.
A work around for me was to nest the clip(s) I was using Optical flow on. Using Optical flow inside of the nest not on the nest.
A shot in the dark, but doesn't hurt to try?
No I am a professional editor and understand the limitations of Optical Flow and its implementation, and how to get it to work properly. This is a rendering error with M1 Macs and Premiere.
rlr and community,
Sorry about this issue. We need to get the product team's attention to this issue. Therefore, to increase my ability to advocate for a fix on your behalf, could you help me out by upvoting this bug? https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/44485809-bug-optical-flow-a...
My colleague Summet has already filed on this issue internally.
Thank you for calling attention to this bug, speed effects are a core tool in an editors arsenal.
This bug also appears when I batch render to Media Encoder, even if I'm running in Rosetta, meaning I cannot batch export. Another frustrating problem, as I often have numerous delivarables, cutdowns and spec requirements for distribution channels, slowing down my workflow quite a bit and impacting my ability to hit deadlines in a timely manner.
Is there an update on this bug affecting core functionality in the software?
Same issue here on a Mac Mini M1. I have to send projects to my iMac Pro for a final export.
Has everyone tried switching from Hardware to Software encoding? Not saying this as a permanent fix, just to see if either mode provides a different experience or if they result in the same corruption.
I have experince doing software encoding only or 2nd pass encoding ; it doesn't work. It turns out all my atempts exporting with media encoder didn't work.
The only real solution for me was to boot Premier using Rosetta, but it turns out that even using rosetta I had other weird gltich (some of my 4k footages (R5 422 CLOG) used to pixelate SO THEN I descided to do a clean instal of my mac OS and réinstal Abobe cloud software without using my Timemachine back up from my previews i9 macbook pro 2020 = seems to fix all my issue with Optical Flow in rosetta mode so far ! and mith NeatVideo denoiser pluging as well.
It turns out that using my timemachine of an intel Mac on a sillicon Mac isn't a good way to start using a Mac M1
I'm one of Premiere Pro's product managers and this issue definitely has our attention. It's a bug we can reproduce and it is one we have logged. I do not yet have an ETA for when it will be fixed but when I do, I will share it with you.
My apologies that this issue has gone unaddressed for so long.
Was this fixed? I'm getting weird artifacts in my exports as well.
Not yet! Mine is still doing it. You have to use Intel Prmeire and export directly from Premeire. If I use Media Encoder to queue it will still have curropt video. Despite using Intel Premiere 😞
I guess for the OP the solution might have been fixed with Beta, but the issue I'm having with interlaced exports is still happening in the Beta. The only fix was using an Intel based mac.
We are aware of the interlaced export issue too. It's being worked on but is not yet in the beta.
Are you exporting to a local hard drive or to a network attached storage device?
This issue should be fixed in the latest beta of Premiere Pro and will be included in the next release version of Premiere Pro. Information about how to use Creative Cloud beta applications is here: https://helpx.adobe.com/x-productkb/global/creative-cloud-beta.html. The summary of that article is that:
1. Beta apps are available from the "Beta Apps" section of the Creative Cloud Desktop app.
2. Beta apps are designed to be installed alongside release apps - it's completely safe to have both installed. However...
3. Beta apps are unfinished and should not be relied upon for critical work.
where can I download the beta version and test?
I just used Beta. You're right! This issue is now gone in Beta! Thank you so much! Looking forward to the pPro release.
Was this resolved in the 22.3 update? I don't see it in the release notes for known issue or fixed issue.
Yes, it is. I'm also interpreting your comment as "Hey, Adobe, you should do a better job listing that bugs are fixed" 🙂
If so, I agree and it's something I'm looking into.
Amazing and thanks. Looking forward to testing it!