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

[Chris Spiegl]

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

[Post31037633t2uy]

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

[mayjain]

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

[urban.space.man]

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.

[nyanthecreator]

Same Problem..

[tananoff]

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)

[Tristan25439104zbgw]

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.

[jakepercey]

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

[Chris Spiegl]

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?

[Tamal]

Is that mean there is still no solution year later?
btw we talking about most usefull (hardware accelerated!) export codec.

cmon guys, im really bewildered...

[Kevin-Monahan]

The status of this bug report has been updated.

[Kevin-Monahan]

Hey @Chris Spiegl,

Hope you are well. This bug has been marked as fixed internally a version or two ago. Is it fixed for you now, as well in 24.5? Let me know so I can take action on this bug report. I am trying to close it out if it is working now.

Thanks,

Kevin

[Chris Spiegl]

Thank you, @Kevin-Monahan for the check-in.

I tend to use Beta for most of my videos, so I already used the fixed version for a while.

Now, I tested version 24.5 (official release from 29 days ago) and I exported two files (once through Premire Pro itself, once through Media Encoder).

I am able to seek through both of the files (PP & ME export).

So it seems this is fixed in stable & beta now.

I am thankful that this is finally done.

But, please, let me iterate:

I still hold my point: taking a full year to fix such a basic issue (exporting a world standard video format) is ridiculous and should NEVER happen. This 100% cannot be in the interest of Adobe, and there really needs to be some work done on internal processes if this is how problems are treated and fixed.