Based on AV1's trajectory, hardware encode isn't necessary (though it is nice). The current encoder is a reference encoder. Now that the spec is finalized, expect significant speed improvements from production encoders (realtime likely won't happen until we get it in hardware though)

> The biggest thing it does add though is multi-stream support

I would have thought this would be a part of the container format rather than the video codec?

The way things are going, we can pretty much forget about AV2 hardware encoders in PCs anytime soon. All the newest, best chip capacity is being completely hogged by Apple and AI companies.

Unless chipmakers port the AV2 design to older, cheaper nodes, it’s just not happening for average users. We’ll probably see some Chinese TV chip makers throw in an AV2 decoder just to check a box, but as an actual encoder? I wouldn't count on it anytime soon.

Not always https://tonisagrista.com/blog/2023/jpegxl-vs-avif/

Maybe libavif will pick up AV2 support, so all one needs to do is update it to v2.0.0 or something and bam! Extra efficiency!

>........I'd say that AV2 isn't worth it.

Unless they have hardware encoder and decoder design done in parallel, otherwise it would be 2028 before a hardware block design is done and 2030 for the earliest product to ship with it. In reality I think 2031 or 2032 is more likely.

And I have been saying the same for quite some time that 20-30% for a generational codec improvement isn't worth it. I think they originally aimed at 50%, and then 40% and then 30%.

Patent trolls are nasty. How long will it take for one to get the full support of those shaking the independence of the US judiciary for their own gain? Let's hope the rot stops before that.

AVIF is for sure my favorite image format right now. No other format has the quadfecta of lossless, HDR, transparency, browser support. Plus as you said, for very compressed images it looks amazing. It blows my mind how small AVIF files can be. Also, unlike HEIC and Ultra HDR JPEG, it actually supports HDR natively as part of the file format rather than doing the hacky sidecar gain map trick. I know it doesn't matter to everyone, but I just love HDR and AVIF is the only format that I feel like really takes it seriously.

My 10 year old iPhone 7 can play 1080p AV1 video in software for more than 200 minutes with VLC. The iPhone 7 was released a year and a half before AV1 was.

So I think it's a safe bet the current Apple TV devices are capable of playing AV1 video in software. There's a VLC release for Apple TV:

https://www.videolan.org/vlc/download-appletv.html

https://apps.apple.com/us/app/vlc-media-player/id650377962?p...

Honestly AVIF2 is the last thing we need now. There are way too many minority image formats already.

It took 7 years for the first patent assertion claim against AV1 to go to the courts and it will probably take a while for that case to resolve. Funnily enough, it wasn't from the pool constantly putting itself in the news about it over the years. I.e. it can take quite a while before attempts are made.

Looking at how GPU development has been sidetracked for NPU, I worry that this is 2035 target at best. Manufacturers will push for maximising matrix operation silicon area. In the era of trillion dollar investments into datacenters, traffic cost is afterthought. The only benefitors might be YouTube, Netflix and such, but on their scale investment into ISP level caches might be cheaper.

> The biggest thing it does add though is multi-stream support

This was supported in H.264 MVC but only saw real use for 3D movies on physical BluRays. With almost no content available outside that.

I strongly disagree with it not being required. I run a small social news site - AV1 is still prohibatively expensive both for the server and clients for software encoding/decoding. Without hardware encoding, the tradeoff for better compression ratios in exchange for massive battery use + very long processing times for encoding simply isn't worth it. In order to get AV1 out, I have to often process a h264 version of a video first anyway, just so the client isn't left waiting for their video upload to finish encoding. This means to support AV1 I'm not saving anything on the storage side. Even youtube only does AV1 encodes for extremely popular videos - it only makes sense to do at significant scale.

I love AV1, don't get me wrong, and I can't wait til I can switch over to it as a single unified format for both images and video, but for now the cost is too high until hardware acceleration becomes ubiquitous

Dolby's patents are garbage, and they know it. They managed to patent entropy coding somehow. This will not stand to challenges, and they managed to poke a well-resourced company.

Has nothing to do with video codec.

Download the video with yt-dlp & play it in mpv you'll see it even flies on a potato.

Play the same in browser and it'll be dropping frames left and right.

Outside the apple ecosystem, AV1 is supported nearly everywhere.

> enabling high-quality video delivery at significantly lower bitrates

> likely will remain so til ~2028 when the first av2 hardware accelerated chips start dropping

This might sound dumb, but whats the point if its intended for slower devices, but those slower devices don't even exist yet?

That's fine and not anything new for codecs, they always take a long time before mass adoption.

Take a look at AV1 itself, you can't even say it's really ubiquitous on all hardware. It's quite well along in adoption compared to early days, but some mobile devices are still lacking hardware acceleration for it.

I feel like in 2030 it's more likely that we send 480p and just upscale with ai on the other end

In HW accelerated chips, what part of the calculations they usually accelerate? Could it be possible to repurpose old HW?

Hardware encode is required if you want things like video calls, camera recording and such to use it.

It isn’t required for content distribution platforms which aren’t realtime and the cost of encode is easily made up by hundreds of thousands of streams.

Anything running on a battery will need hardware acceleration

This will always happen. There are just some entities that can't stand not seeking rent.

Do you think advanced users should consider AVIF/AVIF2 along JPEGXL for long term pictures archival ?

Which kind of encode settings do you suggest for conversion from high resolution RAWs or JPEGs ?

I really don't.

1. Lossless AVIF is a joke often beaten by WebP and even PNG. Even worse for grayscale.

2. Chroma subsampling remains a bad idea for still images unless the resolution is high enough to hide the artifacts.

3. Tooling is the worst part, AV1 encoders are basically focused 99% on video and leave a measly 1% to image; unlike JXL, of course. SVT-AV1 still doesn't do YUV444 and libaom was unusable. Fortunately, the unpaid enthusiasts were here: https://giannirosato.com/blog/post/the-multimedia-renaissanc... (and more recently https://giannirosato.com/blog/post/oavif/)

I don't see AVIF being used for lossless, which is the largest reason I'd prefer JXL to win: one codec to rule them all sure is an alluring future.

>but I just love HDR and AVIF is the only format that I feel like really takes it seriously.

JPEG XL would like a word.

Not especially relevant, as the obvious use of AV1 on the AppleTV is streaming, and the OS frameworks don't request AV1 without hardware decoding. Services which provide their own video decoding (are there any?) don't seem interested providing their own software decoder for the ATV, despite the bandwidth savings.

I wouldn't be so pessimistic, Intel and AMD aren't going to stop making CPUs, and if their integrated graphics adds AV2 it will be motivation enough for others to follow.

PCs don’t need hardware encoders. There are no realtime jobs on these. You can let it encode in however long it takes.

You need hardware encoders for things like cameras because they need to encode in real time since the buffer would quickly overflow otherwise.

Last update seems to be "lawsuit was filed" with zero updates since then. That stuff tends to move slowly.

I use Firefox but YouTube has recently started giving me a pop-up occasionally telling me that they are intentionally slowing down the site because they don't like some of the browser extensions I use.

use the enhanced h264-ify to block the av1 stream, av1 takes a lot of cpu

It was difficult to find a nice name, with av2 :(

It works in French d2vid (Deuvid)

At least it's not D4vd.

daviid - or trim to davii and pronounce it "davey". But tbh I quite like dav2d.

2av2quit?

I like it - not as punny as the first but pretty straightforward.

e2ed

They’ve had hardware decoding since M3 and equivalent A cpus. So I’d say it’s pretty well supported.

Google H264 SVC

> It took 7 years for the first patent assertion claim against AV1

This might just mean that if the claim is found valid, there's seven years' worth of inertia slowing down any effort to move on. Seven years in which HW and SW manufacturers worked to build in the support, and you the user developed your processes or workflows around assumptions specifically tied to that solution. I'd rather know on day one if I should go that way or not.

On that topic: https://arstechnica.com/gadgets/2026/03/av1s-open-royalty-fr...

Sound like a Chrome/Youtube problem. My 2012 Macbook Pro plays 1080p AV1 just fine in VLC (pretty sure Youtube works fine too in Firefox, but I didn't check whether or not it was AV1 or H264).

Unfortunately for you, newer codecs use more CPU than older ones so AV2 would probably be even worse.

I gave up using Chrome a decade ago. It’s a power sucking pig. Safari has its own issues, but at least it’s usable. When I need something that isn’t Safari, I use Firefox.

i'll be surprised if anything comes of it because like... https://aomedia.org/about/members/ if the legal departments of all these corporations haven't made them drop av1 in all these years there's probably not much there?

One of the interesting usage of AV1 was specifically for low bitrate calls, and software encoding was perfectly fine, even on mobile.

With low enough resolution, framerate and bitrate, you can get a quality stream without significant encoding artifacts compared to any other codec. It is in production right now and has been for a while.

The tradeoff CPU / bandwidth is quite advantageous in situations like this. And no, AV1 HW encoders cannot usually be used, they are not designed for a tight bitrate control or realtime communications like software encoding is usually.

Six years ago Apple TV added support for playing 4K YouTube video:

https://9to5mac.com/2020/06/22/tvos-14-brings-support-for-st...

YouTube's 4K videos are only available in VP9 and AV1.

So the YouTube app on tvOS has supported at least VP9 for six years and I wouldn't be surprised if it supports AV1 today.

One of the biggest gains of having dedicated hardware is that the computation doesn’t happen on the general hardware.

This is what makes it viable on mobile devices where system responsiveness and power efficiency are high priority.

Generally these hardware decoders haven’t been retoolalble.

Essentially all of the processing of the video data, barring the container format which the CPU uses to know what part of the data to send to the GPU or the Audio chip or codec.

And HW acceleration is generally a preset baked in version of the encoder or decoder. These are mostly codec specific.

So, no using hardware from previous versions.

Now, you can see some software that tries to use the GPU itself, instead of the dedicated hardware acceleration, to decode, but that isn't the HW accelerated, and may not operate in real time.

At the same time, that will consume much more power, eliminating some of the advantages or the pure HW rendition, especially important for mobile.

I could see an argument being made for encoding, if it is 2x or faster than the CPU, but I haven't looked at any in a while, so don't know the speeds.

Typically things like quantization and motion estimation.

He would like a word, but browsers said no?

There aren’t _that_ many. HEIF has been an unusually large pain in the ass just because it’s both patent encumbered and incredibly popular since the iPhone and many cameras use it.

JPEG is woefully outdated with the lack of HDR and modern compression, HEIF can’t be used without paying a license, webp was designed just for extremely efficient small images rather than local storage, avif I’ve never seen used ever, and JPEG XL is on track to be the next major format.

I agree we don’t need an avif2, but until jpeg xl there really weren’t any decent alternatives for jpeg.

Ram and Ssd is just the start capitalism dictates profits will suck all production to AI. CPu have 3-5 year production timeline ie cpu prices will start going up a lot more as previous production contracts expire you might even get shortages new consumer cpus won't be affordable or spread as fast as you think.

It's a silly idea to not improve on things for something as "too many" formats. There's too many ARM processors out there, should companies stop development and keep using old, less efficient CPUs?

Apple A17 Pro / A18 include AV1 hardware decode.

Use cases for hardware encoders in PCs:

- Video calls

- Screen/webcam recording

- Live streaming

- Real-time transcoding for media servers (don’t know much about this but I’ve heard it’s a thing)

- Game streaming

- Video editing (making exporting less frustrating)

For reference: dav1d 0.5 can decode 143 FPS of a 1080p 8-bit video on a third gen core i7.[1] I doubt there's been much in the way of regressions since then. 10-bit and 4k is obviously a lot more heavy, but not really relevant to older devices.

[1] https://www.phoronix.com/news/dav1d-0.5 (it's mislabled as a core i3, but the 3770K is a core i7).

Chrome has used less power than Safari for a few years now. As far as I know, the only good reason to use Safari is to use FairPlay DRM for sites that need it. For all other purposes, Firefox or Chrome is superior. https://birchtree.me/blog/everyone-says-chrome-devastates-ma...

> One of the interesting usage of AV1 was specifically for low bitrate calls, and software encoding was perfectly fine, even on mobile.

You really want hardware decoding on mobile, otherwise you end up with 40 minutes battery life. Fortunately, for typical videoconference resolutions, VP8 and H.264 are just fine. AV1 is nice to have, though, due to excellent support for synthetic content (screen sharing), and for scalable video coding (a much more elegant solution than simulcast, IMHO).

In the world I live in, the general plan is to stick to VP8 and H.264 for the time being, and to skip to AV1 when it's universally available on mobile. I haven't seen any features of AV2 which would justify waiting for it.

480p ? More like 200i. There's a race to the bottom driven by those "up to" codecs.

Hopefully their patents will be busted and preferably Dolby will be also forced to pay damages for filing invalid lawsuits. That's the only way to teach patent trolls proper lessons.

Newer codecs has generally introduced more ways a video can be encoded, so that the encoder need to work much harder to encode a video, so that it actually achieve the gains that the newer codec allows much more processing will be required. Decoding on the other hand, will mostly stay the same or increase only slightly. It's not likely do decrease though, so if you struggle playing av1 today, you will also struggle with av2.

For encoding, you can always write a simple encoder that use only the features that were present in mpeg2, and it will be about as efficient as mpeg2 as well. Newer codecs has more features that allows more efficient encoding, at the cost of more processing.

Safari has a terrible developer experience and has been behind in implementing the various browser API for years, including AV1 support.

I'd like to think so as well (well, I don't know they'd necessarilymake them "drop" it as much as license those particular patents/accept the risk they may have to pay in the future) but on the other hand history has shown VP8 had a lot of companies behind it too before Google signed to sublicense patents from the MPEG LA & other holders for it.

Have you said this for Audio Codec I would have agreed. I do not know a single Smartphone Video Conferencing software that uses CPU encoding rather than hardware encoding. Neither WhatsApp or FaceTime, perhaps the largest of the two real time Video Call uses AV1.

It's not for slower devices, it's for lower data transfer bills for providers like YouTube.

It is still ironic to me that my Steam Deck has decode AV1 acceleration, on a really old CPU/GPU combo.

Even without encoding, as long as decoding is supported for AV2, streaming sites like Youtube can always transcode uploads. The encoder on mobile hardware is more of a nice bonus as long as we have an AV1 encoder available in the meantime.

Firefox is getting the flag to turn it on in the next release, chromium just added it back now there is a rust decoder. The wheels are turning again. Browser support for jpeg xl is very much in progress again.

It may always happen but it would happen less if we updated patent laws to fine people who filed invalid patents or enforced some kind of similar punishment. If you file a patent, it's up to you to verify that your patent is actually valid, and the courts shouldn't have to do that legwork for you. It also doesn't help that the patent office/components of governments don't review patents as thoroughly as they used to. Same with trademarks.

> There aren’t _that_ many.

https://en.wikipedia.org/wiki/Comparison_of_graphics_file_fo...

The market can handle one new format around every ten years. JPEG XL just came out so everybody should bide their time for a while instead of trying to immediately churn to a slightly better format.

so that new devices can adopt it

They can't adopt it if it doesn't exist.

The latest Apple TV is on the A15:

https://en.wikipedia.org/wiki/Apple_TV_(device)#4K_(3rd_gene...

There may be a new Apple TV released this year.

Almost all of these are historic relics of no relevance today. FLIF for example was a research project that was later the basis of JPEG-XL.

Pretty much only the ones I listed previously are serious contenders in the space right now.

Safari has had AV1 support for a long time. Absolute majority of "various browser API" that they don't support are all kinds of "Web Bluetooth"-like crap that I don't need and which only introduces attack and tracking surface when supported.

It's a win for consumers as well if you can get better video quality or more reliable calls on a slower connection.

And it is already present in Safari (and more generally in iOS and macOS, as part of the standard OS graphics library):

* https://developer.apple.com/documentation/avfoundation/avvid...

* https://petapixel.com/2024/09/18/why-apple-uses-jpeg-xl-in-t...

AMD added AV1 encoding only in later SoCs though. Next Steam Deck will have both.

Even better, software patents should not be allowed in the first place.

> There may be a new Apple TV released this year.

The evergreen prediction in the Apple TV world :p. IIRC, Mark Gruman initially predicted the next model would be out H1 of 2024

How is Dolby a patent troll? :D

Yeah, no production or large scale VC system is running software AV1 encoders on smartphones. You will drain a full phone battery in 1-2 hours of calls.

It just doesn’t make sense and will result in extraordinary power/battery drainage at best, or output that’s worse than hardware encoding.

The only way you could get AV1 to software encode in realtime AND low latency on a mid-range Android chip is by disabling or skipping nearly all of the compression/encoding features that make it good at low bitrate.

While I agree with the general sentiment, I would not classify Dolby as a "patent troll" — they still do invest in research and developing products, right?

Everything here is really niche, except video calls (and even that...).

In other words, unless on smart phones, don't expect broadly distributed AV2 encoding hardware.

If it does happen on PC, it will be most likely some courtesy of the hardware chip designers.

I generally don't like the current patent law but it sounds a bit off to pay the government & wait for them to review your patent claim and then get fined by the government when both of you were wrong about it. There are already processes to additionally fine a company bringing about a truly frivolous patent lawsuit, it's just rare because usually it's not so cut and dry as we'd like it to be.

VP8 was developed by a small company and bought and open sourced by Google on a fairly short timescale because the proprietary codec group had tried to start exerting their control.

So it's not accurate to say that had a lot of companies behind it. That usage came later and even then it was mostly in odd corners of the video industry.

Why patents is a problem, please explain. If you build something that has been patented, then, well, you pay the per piece fee on it.

And what about old devices? I'm sure someone out there is still using an s5 as a daily driver... Future proofing is great and all, but 240p on modern devices looks like trash, even worse than tube tv.

> Yeah, no production or large scale VC system is running software AV1 encoders on smartphones. You will drain a full phone battery in 1-2 hours of calls.

Yeah but, half jokingly, Zoom does that (draining the battery in an hour) already :P

Patent mob seems more fitting.

Another example is Qualcomm

Video calls are niche, and offline encoding of video isn't?

Are you sure this isn't just “things I do are commonplace, and things I don't are incredibly niche”?

I'd classify any patent racketeer as a troll. Dolby has nothing to do with AV1, they just want a parasitic rent on it. Whether the troll actually does anything else besides the trolling part isn't really relevant.

Screen recording is not niche, anyone who works remotely probably does video calls daily and the others are somewhat more niche but I'd guess that at least 50-70% of people do at least one of these things

Who originally developed the codec is only half the story. In 2011, 17 companies created a CCL agreement around VP8+WebM. In 2013 Google signed the sub-licensing agreement to keep it free. Any of the legal teams at those 17 companies had the chance to catch it before then. That there were a lot of legal team reviews by the big tech companies involved did not catch everything. The system isn't designed in a way to make that a solid guarantee like it should be.

Because they have nothing to do with AV1, they simply want to leech on it. It's fitting to call them a patent troll.

> In the 1980s, when IBM accused Sun of violating seven patents, Sun examined the patents and argued that IBM didn't have a case. The reply of IBM's lawyers was "maybe you don't infringe these seven patents. But we have 10,000 U.S. patents. Do you really want us to go back to Armonk [IBM headquarters in New York] and find seven patents you do infringe? Or do you want to make this easy and just pay us $20 million?" And Sun paid out.[4]

240p for someone’s webcam thumbnail in Microsoft teams is perfectly sufficient though.

I mean my idea isn't the only one in that solution space. My reasoning was to ensure that the government actually reviewed the patent and ensured it was valid instead of rubber stamping it. Or, even better, the filer of the patent application would do that. Although the best is probably to make software unpatentable anyway.

So, status remains quo, the commons remain tragic, and glory to H.264 forever?

They can keep using whatever they're currently using.

This doesn't take away anything. It's a new standard.

Based on your argument, one should add new safety standards to cars like seat belts, because old cars might not have them.

At least until a better codec has widespread enough hardware support, I think.

Yeah, I wouldn't mind getting rid of software patents. Or, at least, making the patent reviews more rigorous before assignment.

one shouldn't*

One shouldn't add new safety standards*

writing before coffee...

To be fair, some municipalities do actually require old cars to be fitted with seatbelts... air bags, not so much, because apparently changing a steering column is too hard?

Well, I just noticed I said 'should' and not 'shouldn't' which I wanted to say

But to your point,

While they might not be required to retrofit, one shouldn't stop defining new safety standards.