Support AV1 Video Encoding and Decoding

@Raphael297215156mgc thank you for your reply, you said: "Is just not true that AV1 is heavier in the processor. "

And here's what Google AI Overview said, with the search: 'av1 vs h.264'

It's also known for its advanced prediction and encoding methods, and its ability to produce excellent quality at low bitrates. However, AV1 requires more computing resources than H.265 and H.264. (emphasis mine)

I'm going to spend the rest of the day, weighing what google said, and what you say and, gee, which one do I go with... you know, when you say something exact opposite of reality. Indeed, does Truth matter anymore?

Priority based on user frequency alone would cause Adobe to completely lose professionals. How many people actually use ProRes 4444? That's a very specialized format that a Vast majority of Adobe users will not, and Should not use. But it's important to have for those professionals who rely on it. 
If we always wait until we see a demand for something before pulling the trigger on doing it then we would have very few innovations. The masses didn't want a motorized vehicle, they just wanted a faster horse. 
Adobe probably supported H264 well before hardware really handled it. That's why so many people say things like "No, you need prores for proxies because h264 will grind your timeline to a halt." And there are still quite a few people who still say that, just because that's what it was and they haven't tested it since. It may be true if they are working on a machine that's more than 10 years old, but on anything that is capable of reasonably editing 4k+, it is doubtful that they don't have hardware encoding/decoding specific to h264. 

Sir, makes absolutely no sense to wait for more GPUs with AV1 encoder to show up, think with me, how will AV1 be used if the software does not support it? There are a lot a cheap GPUs with AV1 support, we are talking about the RTX 4000 series (including RTX 4060, which is cheap), the AMD RX 7000 and intel Ark. Plenty of options on basically every price range. 

All creators i know use GPUs with AV1 support, they just don't use AV1 because adobe, one of the CREATORS of AV1, does not support it on Premiere. 

Would make a lot of sense if Premiere received the support before the GPUs and that would make people upgrade, the other way around makes absolutely no sense. 

It's been tree years since AV1 encoding is available on all price ranges. That is simply not acceptable. 

The argument for lower priority is rather supported by the hardware information in the above comments.

As the above comment makes clear, full AV1 support is only in a few of the most expensive GPUs. Which would currently be used by only a tiny fraction of the user base.

But in time, that will trickle down to more computers, and then ... it will become more useful to more users ... meaning time to move it up the priority list.

That's how prioritization works. Done it myself in my own biz for years. And often, even I don't like the priority decisions I have to make.

That's a great point. If the argument against it is that it requires specialized hardware then why in the world would Adobe support Mercury Transport monitors, for example? 
They choose things with balance between what their mass users use and what their professional users use. Sometimes the mass users ends up being what the professional users use as well. AV1 is likely something that social media content creators would use, and large studio editors will likely not. And that's ok. It's kind of like normal users wanting adaptive cruise control, and an indy car driver yelling at everyone telling them how dumb they are for wanting that in their vehicles because they wouldn't use that. Recognize there are multiple groups of users, request what you want, and help the regular requests along in a way that would potentially benefit you in the long run If you would like to. 
I don't have a 4000 series yet, so this doesn't benefit me Now, but it could in the future. Plus, if someone were to give me a slew of files, I'd love to not have to jump through hoops to use them whenever possible.

Is just not true that AV1 is heavier in the processor. Is about the chip used. On Nvidia RTX 4000 series AV1 is way faster and lighter on the hardware than H264 and H265. 

Mismatching audio, for sure, can't be used for doing an audio mix...sort of. Adobe could handle it several ways. The most obvious would be to highlight mismatching audio so the user knows that they would be able to understand Some information from the proxy, but shouldn't go adjusting different settings of individual channels for the audio. There are some easy one also like if the original has no audio, but your proxy has audio channels. Ignore them automatically, or at Least do a check for data. Yeah, there's an audio stream, and it's completely silent, so go ahead and ignore it. Maybe just warn me if the original has no audio, but my proxy does? And Still let me use it if I want to. Maybe someone decided to create a proxy of the original video and include the lav mic audio in it or something just to use as a stand-in for something else. That could be a good idea, maybe that works for them. I just wouldn't do something like that because "that's not the way people work with premiere." I get Canon footage all the time with 4 channel audio and only 1 is being used. So my proxy Has to have matching audio. Again, those 3 channels are garbage because they are silent. Adobe Could have a method of flagging silent tracks and allow mismatches for them. In fact, I would Prefer to let it spend the time to check for audio signal on ingest and automatically remove them (as an option). If someone mistakenly recorded a mic to stereo audio and it's only on one channel, it would be great if I had the option of just eliminating the right channel and treating left channel where there actually was signal as mono. I have to change that manually in Premiere AND leave the original alone, OR run it through ffmpeg to change the stream of the original, which I don't have time to do 99% of the time and wouldn't trust someone that does have the time to do that kind of task. 

Again, this should just be optional. I'm sure some people Do want to keep the original audio format even when it isn't used, or if the video file was S&Q so has no audio stream at all then they have some process that requires their proxy file to Also have no audio streams. I don't know why that is useful, but it very well could be for someone, and the software should support that workflow. 

Indeed, AV1 is more processor intensive than even h.264/5. Exactly what we don't need.

I could probably join, but I can't find the benefit of widespread AV1 support. This is a very slow codec that requires the latest hardware solutions. While there is no translation function, no voice cloning, and many advanced things needed to create content, codec support without an alpha channel does not seem so urgent. For the rest, there is webm with VP9.

Hello Adobe, its nearly 2025. Even my iPhone supports AV1 nowadays. Every Recording Program on Windows Supports AV1, so why is not implemented in Premiere Pro? Makes 0 sense to me.