Skip to main content
Chris Spiegl
Community Expert
Community Expert
April 12, 2023

MacBook M1 Max Exported H265 File (AME/PP) can not playback / seek

  • April 12, 2023
  • 43 replies
  • 4711 views

I have been using the M1 Max + Premiere Pro for years at this point but with the recent release I got problems for about a month or two now which I never had before.

 

When I export a file with H.265 at 4k or 1080p, the file ends up not being playable in preview, QuickTime, VLC, or Premiere Pro for that matter (importing it again into a new sequence).

 

The exported file is NOT playable when exporting h.265 longer than 10 minutes with:

- Premiere Pro 2023.2

- Media Encoder 2023.2.1

- Premiere Pro 2023.2 on M1 with Intel Version (Rosetta)

- Premiere Pro Beta 2023.4

 

This problem is happening no matter if I export with Premiere Pro or with Media Encoder.

 

Export works normally when:

- exporting to h.264

- exporting with an Intel MacBook to h.265

- exporting to h.265 with DaVinci Resolve

 

I've not had this issue in December but it's been annoying recently that I can't use H.265 any more for the exports.

 

I hope this can be fixed / figured out soon.

 

Technical Details:

- MacBook Pro M1 Max

- Premiere Pro 23.2

43 replies

Chris Spiegl
Community Expert
Community Expert
November 28, 2023

I have been working with the Beta for months at this point. Those do work and continue to work.

But I would really prefer not to have a to use a Beta as my daily driver just so that export to HEVC works.

 

I just ran an export with HEVC in PP 24.0.3 and it appears to still not work for Seeking.

I feel this is slowly but surely becoming ridiculous. A world standard in video codecs / packaging and one of the leading editing programs can't export to it in the regular version?!

 

This bug has been known (and fixed in the beta) for over 6 months at this point!

 

It can't be that hard to release an upate that actually fixes something, can it?

Participant
November 18, 2023

Yep, I have the same issue! Can't scrub through long videos on my Mac M1 machine. 

Participant
November 17, 2023

Still have the same issue with Apple M1 Max and Premiere V24.0.

 

Edits H.265 footage from Canon cameras perfectly.

 

Footage exported from Premiere and readded to another project requires rendering before use.

Participant
November 16, 2023

Hello! still have same problem with Mac Mini M2 Pro 16/512 (10CPU/16GPU) with last Pr(24.0.0 b58) and Me(24.0.2 b2)

nyanthecreator
Participant
October 15, 2023

Same Problem..

Inspiring
October 3, 2023

Still cannot get H265 videos to work in Premiere 24 on an M1 Mac.  Program monitor and its play button freeze, although the entire app doesn't freeze.

Participating Frequently
August 28, 2023

Hi @Post31037633t2uy @Chris Spiegl ,


Sorry for this problem. This has not yet been fixed in normal builds, but is fixed in the latest beta 24.0.0 builds. 
Please check out the latest beta build version from the creative cloud and let us know how it goes there.

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


This is also on track to be fixed in normal builds. I am tracking it and will update here in future. 

Thanks,

Mayjain

Participant
August 25, 2023

Hi,

 

we have the same issue with 23.6 (Build 62) on an M1 Ultra. H264 works without any issues, but with H265 we encounter the previously described and supposedly fixed problem...

 

Kind regards,

Hendrik

Chris Spiegl
Community Expert
Community Expert
August 24, 2023

Dear Adobe & all, @mayjain7130546 @Kevin-Monahan 
I have recently tried switching back to the regular version with the August release 23.6 which states that HEVC is now supported again. However, the export with the 23.6 release does show I B and P frames, but the scrubbing does not work on my M1Max machine (this is tested with AME exports mainly).

The 24 beta release continues to work without the "not able to scrub" situation.

I hope this feedback continues to help resolve this issue and make it available as soon as possible to the regular version again.

Cheers, Chris

Participating Frequently
June 20, 2023

Thanks, @Chris Spiegl for the update. Glad the fix worked in beta builds. This will also be released to the standard versions in near future. 
Customers' feedback is very important for us and we would not like our customers to wait long for bug fixes whenever possible. I apologize for the unexpected delay in this case. Rest assured we keep monitoring the user issues and try to prioritze as much as possible. 
Thanks again for raising this issue.


Glad to help,
Mayjain