Inspiring

Question

H.264/H.265 Formats that use hardware decoding in Premiere -

Forum|Forum|4 years ago
August 26, 2021
6 replies
7009 views

I found this on Puget systems site. Full credit to them. This explains alot of why my drone footage plays well, while my Canon R6 plays poorly.

Hardware or GPU

This topic has been closed for replies.

R Neil Haugen

Legend

Adobe's engineers have just added some more to the HEVC support equation if you have the right Intel CPU. Details of the public beta HEVC additions in the following link to their public beta forum.

Neil

Discuss: Hardware Acceleration for HEVC on selected Intel CPUs

Everyone's mileage always varies ...

A

Andy 1968

Inspiring

Neil,

Thanks for posting the link. I have nothing aginst AMD but when it comes to Premiere Pro I have to recommend Intel CPUs with an IGPU because of the Quick Snyc features. I don't doubt Abode has an M1X chip and Alder Lake CPU for testing purposes. I think we should see some benchmarks soon. I think Window 11 hits the stores next month.

A

Andy 1968

Inspiring

That chart should be a sticky that we can link to if people are having problems editing video from a drone or DSLR camera. Not all H.264/265 is edited the same. Having said that I would like to think Premiere Pro will take full advantage of the 10nm Adler Lake CPUs. Some leaked benchmarks suggest it will be a huge improvement over the old and wornout 14nm chips.

A

Andy 1968

Inspiring

I am sure most people are hip to the benefits of Nvenc and Quick Sync but if not the video below might be helpful. I think they both work great but I admit I would like to see more H.264/265 variations supported ASAP.

https://www.youtube.com/watch?v=1L-erwmRxAU

A

Andy 1968

Inspiring

That chart should be handy to have. I always post that Nvenc and Quick Sync cannot play all the odd variations of H.264/265. I don't doubt in another 2-3 years they will support even more variations of H.264/265.

A

Andy UrtuAuthor

Inspiring

Go over to Puget systems and look at the codecs supported by Resolve. With Gen 11 Intel CPUs, quick sync suports ALL of the various codecs.

I sure hope Adobe gets moving on this.

Warren Heaton

Community Expert

Niel,

No one is suggesting Nvenc and Quick Sync are bug free but the whole purpose of Nvenc and Quick Snyc is to edit native H.264/265. Talking about transcoding to Pro Res or Cineform on a thread about Nvenc and Quick Sync is counter productive to the purpose of this thread. If someone's system is malfuntion I agree transcoding would be wise but this thread is about the benefits of supporting Nvenc and Quick Sync as opposed to helping trouble shoot a person's editing system. That being said I understand Warren loves to transcode to Pro Res. I also understand Warren does not think H.264 should be used for editing. Starting a new thread about the benefits of transcoding to Pro Res and smart rendering for those without Quick Sync or Nvenc hardware would be great but this thread is about editing and rendering H.264/265.

There is every reason to point out that H264/H265 is not an editing CODEC in a conversation about using it to edit. It's akin to discussing the difference between water-based paint and oil-based paint. Sure, one can skip that conversation, but shouldn't act surprised when things do not go as expected.

In the bigger picture, we have CODECs for acquisition, editing, and delivery. H264/H265 falls under acquisition and delivery and any hardware options that make that faster better serve that purpose. Mentoring with a lead editor or any professional training should cover the uses for H264/H265 as well as hanging out with professionals in a community forum.

Regardless of which consumer/prosumer/professional video editing software that a user chooses, there is no optimized option that uses H264 nor H265. Furthermore, when using H264 for proxy files there is no Timeline option that uses H264 or H265 for rendering. This is true for Premiere Pro, Final Cut Pro, Media Composer, and Resolve. (It may be worth noting that for Media Composer that having native H264/H265 in the Timeline is a non-starter while Premiere Pro, Final Cut Pro, and Resolve require an editing CODEC to be used for rendering.) Specific to Premiere Pro users, they may notice the yellow line that appears above H264/H265 clips in the Timeline.

The Premiere Pro user guide discusses CODECs that are good for editing here:
https://helpx.adobe.com/premiere-pro/using/smart-rendering.html

And Kevin Monahan has written a great resource on how to do it here:

https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-guided-workflow-smart-rendering/td-p/10968785

I'd like to remind participants in the Adobe threads that a little courtesy goes a long way in the user forums - especially during points of disagreement. I am sure that some participants didn't mean to disparage each and every last professional editor in the industry in a prior post in this thread, but it sure reads as such.

M

mayjain7130546

Participating Frequently

Hi @Andy Urtu,

We have enabled Hardware Acceleration decode of HEVC/H264 4:2:2 10 bit on Mac ARM systems in the latest Premiere Pro Beta builds. We will also look into other platforms.

Please 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

You can have a look at the announcement here:
https://community.adobe.com/t5/premiere-pro-beta/discuss-hardware-acceleration-decode-for-4-2-2-10-b...

Please let us know how it goes for you.

Thanks,
Mayjain