Participating Frequently

Question

Premiere Pro Export Glitched Frames on M1

Forum|Forum|4 years ago
August 12, 2021
25 replies
31844 views

Hello,

We just recently got 2 new m1 macbooks for video eiting and are having a problem where frames have glitches in them while ecporting. Have tried both harware and software encoding while exporting from both premiere directly as well as media encoder. Have also tried different formats for exporting, H.264, Quicktime, etc, and the problem seems to occur no matter what settings we choose. Initially I thought this was a computer specific problem however it is happening to both of our brand new M1 Macbooks.

It's usually a 1 frame long glitch that scales/repositions a small portion of the video

It occurs at different points in each export

Any ideas to fix?

I've attached samples, AME glitch happens at 0:21; PPHW at 0:06, 0:15 and 0:22; and PPSW happens at 0:10

ame_hardware_high.zip

pp_hardware.zip

pp_software.zip

This topic has been closed for replies.

A

Alex Kartynnik

Participant

End of 2023 and now I also strat getting this issue...

A

Anonymous

Did anyone find a solution to this? I just purchased a new M1 Max Macbook and suddenly Premiere Pro isn't exporting properly, using the same sequences/settings as my previous Mac.

I'm this close to sending the computer back...

guillaumec44441302

Known Participant

I have been dealing with this issue for about a year now on 2 different M1 machines and that is the only fix, run premiere in Rosetta. I have posted this issue in many of these discussion forms. I cannot believe after all this time and the money I spend on this software the issue has not been fixed properly. What is going on Adobe? I cannot use GFX, Alpha Graphics, or Frame holds at all in the M1 native version. It gets embarrassing having your clients point out mistakes that cannot be seen while editing. Mistakes not caused by you but the software you trust and pay good money for to make a living.

D

dbjt

Participant

Let's hope the Beta version gets an official release soon. I can't use it for work unfortunately until they have an offical release. But @guillaumec44441302 if you can, you should really download the most recent Beta and give that a shot.

Kevin-Monahan

Community Manager

Hi, dbjt,

Has the 22.4 Beta hit your Creative Cloud application yet? When you do, give that a try. Bug fixes are afoot. I hope the new version provides relief once it hits everyone's Creative Cloud app. A bit weird that the Rosetta version seems to work around some of these bugs. Sorry about that. I'll do some testing with the new version and my MacBook Pro M1. I'll let the community know how it goes.

In the meantime, keep in mind that the M1 MacBook Pro has roughly the same GPU power as an NVIDIA 1650 Super, which has around 4 GB VRAM (I read). If you have a lot of GPU-intensive processes, like scaling 4K to HD, Lumetri, GPU accelerated effects, mogrts, essential graphics text, graphics, etc., you need to keep those processes in mind. If you push it too much (like running two or three monitors on top of all these GPU processes), I think it's why you see these issues.

Say, have you tried smart rendering? That could offload many of those processes and make your workflow smoother. Different, and may take a bit more time and way more drive space (temporarily), but smoother—just a thought.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

J

JohnjAyala

Participating Frequently

I’m posting my summary after a long call with Adobe technical support about the issue of distorted frames when rendering and exporting using an M1 based Mac with Premiere Pro 22.2. We ran several tests and narrowed it down to .mov files that contained alpha channels that were brought into Premiere Pro. These files caused flash frames (Green glitches and traces of recomposed media) when rendered and/or exported. The solution (that’s not really a solution) is to open the “Intel Based version” of 22.2 that you can access through the Adobe app portal (see attached photo). This will open Premiere and then you can open your non-Intel based project through the Premiere interface. I tried doing a render with the “Intel based version” with the renderer set to Mercury Playback Engine GPU Acceleration (Metal) and I didn’t have any flash frames, it was much faster than the Software Only option and the speed is pretty close to the 22.2 M1 version of Premiere (see below for more info).

What I emphasized to Adobe is that even though this is a valid work around- it’s not a solution. Why do we have to use the Intel version when working on an M1, when these computers don't have Intel chips? All of us who purchased a new M1 computer did so to boost the performance in our editing systems. Not being able to utilize the new technology is a problem that needs to be fixed.

Other information:

-This was done on a MacBook Pro (16-inch, 2021), with an Apple M1 Max chip, 64GB of memory, running Monterey 12.1

Based on this thread and a couple of others, the problem seems to affect all M1 based macs who are using Premiere Pro 15.4 - 22.2.

-I also heard people claim that frame holds were causing these flash frames as well. While I can’t say that this is definitely not the case, we did run several tests using and stacking clips with frame holds (without alpha channels) and were not able to produce the glitching.

-Even more: I ran a test, exporting a 20min HD ProRes HQ comparing the two versions of Premiere 22.2 (Non intel vs. Intel Based version) with the renderer set on both to Mercury Playback Engine GPU Acceleration (Metal). The Non-Intel version (the one that utilizes the M1 chip and has glitches) clocked in 25 seconds faster (4:02 Vs. 4:27). Not exactly a game changer, but it would still be nice to take advantage of the speed.

M

mayjain7130546

Community Manager

Hi @JohnjAyala ,

Very sorry for this problem. Can you please try the latest beta once ? We have done some export improvements in the latest beta builds. You can download the latest Premiere Pro Beta build from Creative Cloud --> Beta apps --> Premiere Pro (Beta)

https://helpx.adobe.com/x-productkb/global/creative-cloud-public-beta.html

Please try and let us know how it goes in the beta build. If you still see this issue in beta builds, please share your original footage/Project file & export settings. We will check it at our end and take quick action.

Thanks,
Mayjain

M

mayjain7130546

Community Manager

Hi everyone,

Very sorry for this problem. We have done some export improvements in the latest beta builds. We expect exports to come out without glitches now. You can download the latest Premiere Pro Beta build from Creative Cloud --> Beta apps --> Premiere Pro (Beta)

https://helpx.adobe.com/x-productkb/global/creative-cloud-public-beta.html

Please try and let us know how it goes in the beta build. If you still see this issue in beta builds, please share your original footage/Project file & export settings. We will check it at our end and take quick action.

Thanks,
Mayjain

T

TKane31

Participating Frequently

Hey PP users,

Recently got my brand new 16 inch maxed out M1 laptop running Monterey12.1 and started moving jobs over to it. I had a bunch of longer format videos go out with audio glitches and sync issues running PP 2022. Most of the time, but not all of the time, there were some audio plug-ins appplied. Clients were pissed and I took a lot of heat. These videos range from 10 minutes to 45 minutes so don't have the time to QC every frame and being I've been doing this work for almost 2 years I've never had to until now. Not sure if it's an M1 issue or a PP 2022 issue but I'm back to working in PP 15.4.2 on my old cheese grater as I can't trust PP 2022 with the M1. When I have some down time I'm going to see if 15.4.1 behaves the same way on the M1. My guess is it won't.

Adobe feel free to weigh in anytime now. Just dropped several K on a new system and I'd love to be able to use it! Thx!

R

richyratton

Known Participant

Another bunch of glitches on an M1 Mac Mini running Monterey 12.2 and 12.2.1. Didn't have it before but do now. Seems to happen for me when GFX with alpha channels are in the timeline, happens in CC21 and CC22. Nightmare. Then again, can't think of a Prem release that wasn't buggy.

Can confirm that if I open the project using the Intel version of Prem the issue goes away.

WHAT ARE YOUR PROGRAMMERS DOING ADOBE????

Sander Vreeburg

Participant

Nice to see that everybody tries to fix this.

It would even be better if Adobe would comment on this issue.

This is not a minor issue. This is Adobe letting professionals deliver crappy productions to their clients.

Please Adobe, comment on this and fix this problem. Fast.

T

Thomas Whitmire

Participant

I believe I have found the source of the problem, at least on my project. It is some combiination of mixed FPS timelines, including frame holds. In my case, some elements are 30FPS and others are 29.97.

I believe the timeline gets corrupted and those intersection points where the framerates need to be resolved generate glitches.

My solution is to cycle the timeline settings' framerate. In other words, switch from 30 to 29.97 and back to 30. This will cause a re-mapping of the appropriate frame blending. I then exported, and it worked correctly.

I'm still not 100% sure this will provide a fix. This glitch may be more random, and my exports are just working this morning. Could others' try this solution and report? Thanks and good luck!

T

Thomas Whitmire

Participant

So, this didn't fully fix it, but I'm in the hunt. Here are my variables:

1. Re-save the project file to a totally different drive

2. Export as ProRes 4:4:4

3. Save the output to a totally different drive (same target as #1)

4. Cycle the FPS for the Timeline

5. Delete media cache files

6. Rename Project file

7. Restart Premiere

8. Software encoding via Media Encoder

Results:

#1 #2 #3: clear glitching

#5 only: glitches, at a different location

1 2 3 4 5 6 7: glitches at same location as previous

1 2 3 4 5 6 7 8: this worked.

8 only: this worked

9 Intel-boot only: this worked.

So, it's looks like a fundamental software glitch with AP, M1, and the GPU. I think my general diagnosis from previous comment may be accurate but I could never find a solution.

T

Thomas Whitmire

Participant

To be clear:

1. Try Software Only

2. Boot from Intel (from Adobe launcher)

3. Remove Hold Frames (lol)

If anyone wants to keep experimenting with sequences with mixed FPS assets, let me know what you find.

jforozcop@gmail.com

Participant

I had the same Issue and I fixed it opening Premiere Pro using Rosetta. This solver the issue for me!

Sander Vreeburg

Participant

Does anyone know if the latest release V22.2 fixes this issue?

J

JohnjAyala

Participating Frequently

They are not. I just got my new M1 laptop and installed V22.2. I didn't know anything about these glitches until I tried to export (on a tight deadline-this almost gave me a heart attack) and then found this thread. I went back to my old system, which luckily, I did not sell yet. This is crucial-amazing this isn't fixed yet.

tomsteiner.rcm

Participant

Brand new MacBook Pro 16 inch M1Max 64 GB (latest Monterey and Premiere)

Exported a project in h264 and got 15-20 glitches in a 3 minute video. Opening the intel version fixed the problem.

But boy. I am angry. What is going on here.

Deleted all frame holds. Did not make any difference.

Example (see ghosted cornerbug top middle):

eaglewhisper

Participating Frequently

I'm having the same exact problems on the same setup. MacBook Pro MacOS Monterey M1 Max chip.

It seems to help if you make a new sequence and then copy/paste your old timeline into the new sequence (still it's a crapshoot) or opening PP with the Intel version.

Even weirder, when I bring the glitched exports back into Premiere, it shows no glitches in the source monitor - but does show the glitches in Quicktime and Resolve.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded