M1 Max Export Problems

[dj_darren]

Hi.

Sounds like a lot of people are having similar problems to me when trying to export a sequence as h264. I'm using Premiere 15.4.1 (2021) on a brand-new Macbook Pro 16" M1 Max. 32GB RAM 1TB SSD.

When viewing the export it's full of glitches and repeated frames (for example someone walking a step, jumping back then taking the same step again), which appear throughout but seem to be worse in any clips with a speed change.

The project is still in progress, so it's a combination of raw footage shot on Canon C300, some ProRes clips and h264 preview clips from a stock website (which will be replaced with ProRes).

Everything looks fine when rendered in the sequence but even checking "Use Previews" in the export dialog box doesn't help. Exporting as ProRes then converting in Media Encoder solves the issue, but this isn't exactly an efficient workflow.

I've tried both hardware and software encoding for the export. Software appears a bit better, but it still has a few glitches.

Can't upgrade to Premiere 2022 because this is the only M1 machine in the office and it will eventually be opened on an Intel machine (which can't be upgraded) so I'm very afraid if this probelm gets fixed it will only be fixed in the latest version and I'll be left with a very expensive brick.

[defaultsmbhe6i4b8uq]

The only way I'm able to get a clean export is to run 2022 in Rosetta.

[mayjain]

Hi @defaultsmbhe6i4b8uq  @euand60297766 , 

Sorry for the issue. Can you please try the latest beta build once? 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.

Thanks,
Mayjain

[mayjain]

Hi everyone, 

Please try the latest beta build once. We have done some export quality 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.

Thanks,
Mayjain

[paulrezult]

Just to add a slightly different solution to this, although not ideal....

I have just upgraded to an Apple Studio (M1 Max) from my trusty old iMac and I'm experiencing glitches when I export to MXF files for TV Broadcast. I have never had this problem before so it's clear it's related to the M1 Chip.

But one thing to note is when I de-interlace my timeline before exporting in Media Encoder, all the gliches are gone.

It's not an idea situation to de-interlace because it's for braodcast but I hope this information helps and I hope this gets sorted soon because it's an extrememly embarrasing situation for me and my client.

Thanks

Paul

[max2428555970ut]

For now I have my old 2019 pro and new 2021 M1 pro. Same project export goes twice faster on intel. Tried several tricks and only option for now is to run even beta in intel mode. Then timing is equal. Could it be caused by fact that project was created on intel machine?

[paulrezult]

I'm running PP 22.3.1 via Rosetta which runs about half speed on export.

Anything running natively via M1 Max is still full of glitches on export.

I think it's nearly a year now since Premiere ran on M1 chips so really not impressed at still having to do workarounds especially for broadcast material.

I believe that a project created on an Intel machine shouldn't make any difference.

[christopherb50820406]

This issue has not been resolved for me with the latest version - Running Premiere in Rosetta hasn't helped either. see attached. 

 

[christopherb50820406]

This issue has not been resolved, opening in Rosetta does not fix the problem for me. see attached.