Support AV1 Video Encoding and Decoding

But it is still ridiculous that what is easy to implement at the current monthly price since 2018 was apparently not possible... xd

How we various users look at things, and how the staff of an NLE looks at things, are going to vary. Considerably. We all see things that we think we and others could benefit from as rather important. Which is natural and normal.

For me, it's some color things, an actual crawl in the EGP, a few things like that. For others, it's better ProRes RAW or AV1 or MKV ... whatever.

For the staff, looking at the entire user base, it's a very different 'view'. They have limited resources, will always have 'relatively' limited resources compared to our want lists. So they have to prioritize.

Thee & me are not going to agree with their prioritization list. But then, we don't see the user data they see. So some things that look stupid to use are actually sensible from their viewpoint.

And yes, I'm as frustrated about that as anyone, but apparently more of a realist than many others.

As AV1 is coming up, so to speak, I would be surprised if that isn't added sometime in the next two years. MKV ... maybe not, as that is realistically far more used as an archivist's tool than an editing tool.

The funniest thing is that AV1, unlike HEVC, is open source and even free... I also find the fact that it took them so long to get MKV support for the current price just **** xd

I just looked at this video from 2020 where Gary explains that encoding in AV1 is the main culprit:

https://www.youtube.com/watch?v=ibXKKllz4xQ

I have no idea how much work has been done to speed this up, but given that this is an open source codec, there may be very little incentive for companies to pursue this. This could be the answer to your question.

loooolll

still no av1

wtf

AYO, we got AI in Premiere Pro before AV1. 

It's a question but it's being posted as an idea because I want to see if we can push this, yet again, up to a threshold that Adobe will actually implement it. Why is it such a bother and why are we getting generative AI for video when we can't even get AV1 video importing, which so much of media uses, especially in my line of work. 

https://community.adobe.com/t5/premiere-pro-ideas/support-av1-video-encoding-and-decoding/idi-p/14133873

This was last year, there's been more from years before, and still nothing is done. AV1 is a format that is present day, better optimized in size and performance.

Give us AV1 support, let me drag a video into my timeline and it not say, "sorry no can do!" It's not good enough in 2024, esp when a free program can do it no problem. Not my first time seeing this talked about, and not my first time speaking to Adobe about it either, so you told me to post my suggestion, one you've been given many times, there it is. Posted. 

Wise and experienced post there ...

Apple is also part of that group, and they didn't implement support for AV1 on macOS or iOS until years later.

As a general rule, it's safe to assume the following about "crazy" decisions inside big business (or any business):

• Research: These companies do their homework. They know that, for every angry customer who speaks up, there there are many more who are silent. I don't know about Adobe, but every BigCorp I've worked for accounts for this when making business decisions (which is exactly what implementing support for any given codec is).
• Money: This is where it all happens. Which makes sense: Adobe is in business; not charity. When you plonk down an idea for a decision maker, they're going to judge your idea on its merits and its cost. Even a good value proposition can get shot down because of margins. From the outside, we have to infer: make our determinations in the absence of the confidential business context. If you had all the data Adobe does internally, you might see things differently.

The frustration? Understandable. But it's bidirectional. "Do unto others..." and all that.

A little politeness goes a long way. As does research.

@kalamazandy 

H.265 is very effective for creating a viewing copy, but needs to be carefully considered for replacement of ProRes.

If transocding ProRes 422 HQ footage to H.265, it's very important to be aware of the following, permanant changes to the picture and sound:

• Interframe video (all i-frame) is changing to intraframe video (frames with a GOP structure)
• Deep peak signal noise ratio (PSNR) is being reduced to very shallow PSNR
• Audio channels may change (for example, 4-channel mixed down to stereo)

If storage space cannot be made to accomodate ProRersHQ clips (be it source used in a locked cut or an edited master), I would transcde to ProRes 422 LT or ProRes 422 Proxy.