No Hardware Encoding on M1 Pro

[NameTheJames]

Hello all, I am putting my new 14" Macbook Pro (base configuration 8-core M1 Pro) through its paces and noticed that I only have access to Software Encoding in Premiere and Media Encoder when using H.264 (Match source, high bitrate -- and I did try changing it to CBR rather than VBR per some other forum suggestions; that made no difference)

1. Is this an issue with the Apple Silicon chips that is yet to be updated? The GPU is a major draw for this computer to me and I'd love to be able to use it to encode more quickly.

2. Are there other codecs I should try? I tend to use H.264 for maximum cross-compatibility and have not dabbled with ProRes or any of the other multitude of options.

I am getting the "Your system's hardware does not support hardware acceleration for the current settings" message.

Thank you!

[NameTheJames]

For anyone who comes across this later -- it seems this issue was in my Memory settings. "Optimize rendering for:" was set to Performance, rather than Memory -- once I set it to Memory, Hardware Encoding became available.

[Steven J McConnell]

Hmm, that's really odd. I'm experiencing the same issue, but the switch to "memory" didn't fix it.

[NameTheJames]

Yeah, you know, going further with this I’ve found more exceptions. I’m not
sure exactly what is the cause anymore, but hardware encoding is working
for me now on ordinary MP4s.

[Zack P]

As someone who came across this later, this weirdly worked (even though, as you say below, it doesn't seem to be the actual root issue). Thanks!

[R Neil Haugen]

"Hardware" versus "Software" encoding for H.264/265 or "HEVC" exports is limited by your CPU, not your GPU.

It is only about whether your CPU has the extra hardware bits specifically used for 'hardware' long-GOP encoding. It has nothing whatever to do with your GPU or GPU accelerated effects within Premiere.

And the controls for long-GOP "Hardware" versus "Software" encoding are found in the Preferences dialog, and also in the Export dialog if you have chosen a long-GOP preset for H.264/265 HEVC.

Neil

[geekinit · Accepted solution]

For me, it was hitting "Match Source"  which apparently enabled settings from my camera's source that my GPU could not support. 

Thanks,

Eric

[moz30416923]

For me, it was unchecking "Export Audio" that causes Hardware acceleration to grey out.

[moz30416923]

Having the same issue. But I don't see "Optimize rendering for" in Memory settings (ver 22.3.0). The only customizable adjustment is the amount of memory allocated for non-Adobe CS apps. Any ideas?

[phatcorns]

I have also found that CBR encoding does not work for Hardware Encoding for h.264 or h.265. It has to be VBR it seems.

[JonasJaekenMedia]

I'm still having this issue. I just got myself a new Macbook M1 Max and have the same problem.
I cannot render with Hardware Encoding if I choose CBR. It only works when I switch to VBR 1 PASS. Switching to H.264 or H.265 doesn't help either.

[R Neil Haugen]

I don't recall any app that has 2-pass hardware encoding. As the hardware bits that do long-GOP encoding don't have that capability. They can do it fast, but not always better.

The CPU can do the two-pass thing. First pass goes through the entire export to figure out what it will do for encoding in the second pass.

And out of curiosity, why do you need CBR?

Neil

[JonasJaekenMedia]

Hey Neil, thanks for your reply.

I myself have always been used to exporting in CBR because in my opinion it gave good results and I always found this to be said online as well.

I just don't really understand why an "M1 MAX" can't export CBR in Hardware Encoding and my 2019 Dell XPS can, obviously thanks to the nvidea graphics card I guess?

Furthermore, I certainly don't see any problem to export in VBR 1 pass (Hardware encoding). But unfortunately I don't see any option to use VBR 2 pass either. I can only select CBR or VBR 1 pass.

Cheers
Jonas

[R Neil Haugen]

CBR uses the same bitrate for every frame. But frames with lower levels of details and motion and such actually do not need the same bitrate for a good image as frames with a ton of fine detail. But using CBR, the computer has to create and then process as many bits for low-detail frames as for high-detail frames.

Using VBR means that when there's a use for high bitrate, you get it. When there isn't, you don't get it ... because you don't need it. And yes, this has been shown many, many times in 'live' testing and presentations.

@RjL190365 is probably the best one to respond on the fine details of encoding per CPU/GPU combination.

Neil

[JonasJaekenMedia]

Dear Neil,

Thank you so much for your information and help. But after having this new Macbook M1 Max for about a week I am experiencing more and more issues when working with Premiere Pro (2023) 23.0. Not only with slow renders but also when editing. Mostly Sony A7IV footage (XAVC S or S-I)

I've looked up so much on the internet about this, but can't find any solution as to why my new macbook runs premiere pro so slow. I'm starting to think there is something wrong with this model. 😞

I tried using Resolve and it runs pretty smoothly. But i'm so used to Premiere.


Cheers
Jonas

[R Neil Haugen]

Not a Mac expert ... maybe @Warren Heaton or @Kevin-Monahan  could help ...

Neil

[Kevin-Monahan]

Hey Jonas,

I have the same issue with hardware encoding and CBR. On macOS, it doesn't seem to be supported on Intel or Apple Silicon, while it is on my Lenovo PC laptop. Sorry about that.

I do not see a bug filed for CBR specifically, but you can make one here: https://adobe-video.uservoice.com/forums/911233-premiere-pro

Thanks,
Kevin

[Warren Heaton]

MacBook Pro (16-inch, 2021) Apple M1 Max

• H264 CBR is Software Encoding
• H264 VBR 1-Pass is Hardware Encoding
• H264 VBR 2-Pass is is Software Encoding
• H265 CBR is Software Encoding
• H265 VBR 1-Pass is Hardware Encoding

iMac Pro (2017) 3 GHz 10-Core Intel Xeon W

• H264 CBR is Software Encoding
• H264 VBR 1-Pass is Hardware Encoding
• H264 VBR 2-Pass is is Software Encoding
• H265 CBR is Software Encoding
• H265 VBR 1-Pass is Hardware Encoding

HP Omen 15-dh1xx Laptop Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz 2.59 GHz

• H264 CBR is Software Encoding
• H264 VBR 1-Pass is Software Encoding
• H264 VBR 2-Pass is is Software Encoding
• H265 CBR is Hardware Encoding
• H265 VBR 1-Pass is Hardware Encoding

DaVinci Resolve 18 makes it difficult to tell if "hardware acceleration" is being used for H264 and H265 exports as the Export Option simply reads "Use hardware acceleration if available".

For Premiere Pro or DaVinci Resolve, I would transcode Sony A7IV footage (XAVC S or S-I) to ProRes 422 HQ or ProRes 422 LT.  XAVC is a great CODEC for in camera acquisition of picture, but it's not a great CODEC for editing.  Sony makes Sony Catalyst Prepare available for transcoding to ProRes, but it's easier to do it via Premiere Pro's Ingest project settings.

Jonas, I highly recommend that you take one of your current Sequences that uses Sony A7IV camera original footage and make a duplicate Sequence with "_ProRes" added to the duplicate Sequence name.  Select all of the Clips, right-click and use Render and Replace transcode Individual Clips to ProRes 422 LT.  60 minutes of source footage should take about three minutes to transcode and require about 42GB of storage space.  When that is finished, change the duplicate Sequence settings to Custom QuickTime Apple ProRes 422 LT.  You'll be prompted to delete Render Files (click OK).  Close the Sequence Timeline and re-open it.  You'll notice that the Yellow Preview Render line appears much less frequently if at all.  Re-render if needed.  You'll notice that that is much, much faster being ProRes to ProRes. Export both the Sequence that uses Sony camera original footage and the duplicate that uses ProRes to the "Match sequence preview settings" Preset.  Take not of the export times.  Export both Sequences to MP4 and also take note of the export times.  Also keep in mind that ProRes can be uploaded to FrameIO, Vimeo and YouTube.  If you try Resolve, it defaults to ProRes HQ for the "Optimized" setting under macOS, but it can be set to ProRes LT or DNx.  Premiere Pro supports more choices for "Smart" editing, but you're on a computer with encoding engines for ProRes so use ProRes unless something about your workflow were to require DNx.  If you were to ever switch to Avid Media Composer, your Sony footage would be transcoded to DNx when ingested.

[Warren Heaton]

H265 VBR 2-Pass should be availble as of macOS 13 Ventura; however, I don't have info on whether it will be Software or Hardware.  Nevertheless, I'd wait on updatintg to macOS 13 Ventura until at least 13.4 to 13.6 rather than adopt it early.  macOS 11.6 to 12.6 seem pretty stable.

[JonasJaekenMedia]

Hey Warren,
I can't thank you enough! I've heard a lot about ProRes running very smootly on Apple Silicon chips.
I will definitly give this a go! Thanks for all the info.

Cheers
Jonas

[Nate5FAB]

Hi Neil

Really appreciate your time on this thread. Been testing Apple silicon this week and encountered the hardware acceleration limitations discussed here. 

Your point re VBR vs CBR is totally true, but to give more context to other users queries here; there are lots of use cases where editors need and use CBR regularly:

- CBR gives editors an option when MP4 is required but VBR doesn't cut it: Adobe's VBR encoding is awful at complex, contrasty detail (think grass, leaves, dappled light etc) especially if you're forced to edit from a clients highly compressed recordings like older DSLRs, OBS etc

- We often use CBR as a control when troubleshooting issues with Adobes VBR renders/settings

- Sometimes a client asks for CBR, so CBR you must deliver

- If the final's being uploaded to YouTube, in our experience CBR results in less artefacts once the lazy YT encoders have chewed it up into a VBR stream

- I have personally found CBR to deliver a more consistant render experience with predictable time frames and much much less fails, crashes and render artefacts than VBR.

I find many content clients have little knowledge of video files, codecs etc so generally if the delivery format requested is MP4 we deliver a chonky CBR file as their "MASTER" AND a lightweight VBR they can upload faster etc.

Apple silicon is a marvelous feat of efficiency, but I think many of the queries in this and related threads are from users who expect Apple sililcon to be a versatile professional tool. And/or those that expect Adobe to be able to leverage Apple hardware in the same way as PC hardware. Unfortunately the cost of compromises apple made for a "unified" system are starting to show.

While CBR might seem like a rare use case, If I was locked into Apple for my workflow (as many Adobe customers are), Adobe not leveraging hardware for CBR rendering would be a deal breaker on Adobe products.

[Warren Heaton]

@Nate5FAB 

I've found Apple Silicon to be fantastic for Premiere Pro, After Effects, Photoshop, Ilustrator and InDesign, even with Software Only CBR H264 encoding.

CBR H264 encoding also not available if running Intel Xeon processors.

As far as Adobe being able to enable it on Apple Silicon or Intel Xeon, isn't it tied to QuickSync?  So, Intel Core and some Intel Celeron, Intel Pentium, and Intel Atom with Intel HD Graphics support.

Edit:  I just double-checked.  I'm always confusing QuickSync with what NIVDIA provides.  CBR H264 requires NVIDIA hardware for quicker encoding - which, of course, we'll likely never have under Apple Silicon.

[Nate5FAB]

Thanks for the info Warren! I wasn't aware CBR was nvidia dependant. Seems strange doesn't it? I think of CBR as "manual" and VBR as "automatic" versions of the same process. Interesting that the less complex process requires the more specialist hardware.

I've now tested M1 Pro, M1 Max, M2 and M3 basic models for Premiere editing: Experienced playback lag and about 15% failure rate on renders on all of them. Basic 1080 60 projects with prores footage, using the same setup that runs fast and flawles on PC. That plus the long export time due to lack of hardware encoding rules Apple out for any sort of pro work based on my tests.

My last Mac was Intel based so maybe I'm missing a silicon trick?

Since you mentioned having a different experience with Apple Silicon, I wondered do you have any specific settings that grant you good perfromance, despite the lack of hardare encoding? And may I ask if you find your good results with a particular chip or setup? (since I could only get my hands on the ones listed above)

Thanks kindly!