Support AV1 Video Encoding and Decoding

The real point is, do we need another lousy to edit in codec. When you transcode, you'll get much better performance using something like ProRes LT or even Proxy - that's a codec made for editing. H.264 and 5 or equally not good for editing. So, I'm not for Adobe spending time on this kind of thing. But you never know.

@MyerPj 

I think you're missing the point - and are wrongbin this, too.

It's not about making money or being expensive in 1st place. It's about the fact that all that work is completely unnessecary because one wouldn't need it at all, if the AV1 codec would be supported. NVIDIA supports it in hardware and all my players can play it. And I need free 3rd party software for workarounds because Adobe doesn't provide support itself. That's the point.

And your workaround advice is wrong: wrapping is only for the container (MKV to MP4). OBS and others do that, too, and it also works with simple ending renaming by hand on Windows. But that doesn't change the codec. So you still have an AV1 MP4 which Adobe still can't read. The only working solution is using Shutter or Handbrake to transcode to H.264 (or alike). And that is very time consuming. And that's the point, too.

<<so time consuming and therefore expensive?>>

Maybe you want it that way, make more $$?

Using Shutter Encoder, drop them all into the window

Choose Function = Rewrap

Click Start Function

It all happens very quickly.

You can charge for that too. (it may even be expensive!)

🙂

What, is it really true?
End of 2024 and still no AV1 within Adobe CC?
Please tell me I missread something...

Got tons of AV1 encoded MKVs here (hello, Adobe, MKVs won't work either).
From MKV to MP4 it's a snap - if I don't have to transcode which I have as CC still doesn't know AV1.
How do I tell the customer, that handling simple screen captures is so time consuming and therefore expensive?

The whole suite is so far behind, it's SO sad (poor performance, not using CPU/GPU propperly - if at all, see e.g. InDesign).

Yes, AV1 would be good to have as an export possibility. No question about that.

one day please

That's total BS, but understandable due to the clumsy wording of their legal department. Which is getting reworked. They work with too many large companies, including both broadcast and defense industries, where that sort of thing bluntly is not allowed. They just can't do it and maintain those clients.

But of course, people like to make snarky comments.

How about simply accepting that not everyone else sees your priorities as essential? That's something we all need to learn to get by in Life, comfortably. And allowing others to simply be other.

Good point. Adobe's engineering time is being spent setting up spyware like functions so they can see everything you are working on. Great use of development resources!

Looking at a 4 year old video explaining that encoding in a new format is the culprit? Well, that may have been included, but AV1 can now be encoded by GPU. WebM was definitely in the same boat. If you look at which cards can encode which things, so long as you have a card within the last 2-3 years that is reasonably good, then you'll have no problem with encoding speeds. 

It's probably likely that Adobe splits things into two categories: Mass users, and professional users. Mass users are likely your youtubers and cheaper wedding/church videographers (it's suprising how many of those there are). Those are mostly going to be, on Average, using H.264 and whatever is straight out of cammera.

Professional users are going to use as original files as possible mostly, so whatever they are getting straight from the camera or an external recorder like Atomos type device. A good number of those will be ProRes, and things that aren't, like if you needed a racing style drone to get footage, will likely be H.264. 

Unless something causes the mass users to start switching to another editor because they support AV1, then the driving point will likely be if a camera manufacturer puts a hardware encoder in their camera system to capture AV1 12bit 4:2:2. I can't quite remember, but I thought it also supported 4:4:4, which is a one up on ProRes, which only offers that in 4:4:4:4. This is very annoying, because there's no point in that last 4 unless you've got alpha. 

Premiere supports H.264 10bit, BUT there are a Ton of variations involved in how things are packaged. It is fast with some, and slow with anything I've tried getting out of ffmpeg, or similar. 

Resolve, is aware that H.265 can actually be a good edit format if you have reasonably current hardware, and it is one of the options for edit proxies. Resolve may be another driving factor, because Premiere Does need to compete with them a bit. 

We would definitely switch to Resolve if we didn't use AfterEffects so often. The ability to copy and paste between them (with Some degree of success), or import AE files directly, create mogrt files when needed, speeds up just enough to make the annoyances in color workflow and needed extra hardrive space for Resolve workflows not worth it for our studio.....yet. Project success can always shift things a bit right? 

Only if the codec supports the alpha channel, it can be supported. Anything that does not have alpha channel support should be thrown into the trash.