Known Participant

Answered

No Hardware Encoding on M1 Pro

Forum|Forum|4 years ago
October 30, 2021
3 replies
17159 views

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!

This topic has been closed for replies.

Correct answer geekinit

"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

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

Thanks,

Eric

J

JonasJaekenMedia

Participant

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

Legend

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

Everyone's mileage always varies ...

J

JonasJaekenMedia

Participant

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

P

phatcorns

Known Participant

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.

NameTheJamesAuthor

Known Participant

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.

S

Steven J McConnell

Participant

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

NameTheJamesAuthor

Known Participant

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.

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