> AV1 is also the foundation for the image format AVIF, which is deployed across browsers and provides excellent compression for still and animated images
I wish adoption was better. When will Wikipedia support AVIF?
Here's the Emmy that C-Cube Microsystems won back in 1995 for the MPEG-2 (actually unconstrained MPEG-1) encoder chip set used in the roll-out of DirecTV.
The original DirecTV encoder was MPEG-1 at 704x480 using eight CL4000 chips. Then in 1995 when the MPEG-2 capable CL4010 was finished, the encoders were upgraded to MPEG-2 (frame only encoding). Then upgraded again to a 12 chip AFF (Adaptive Field/Frame) encoder when the firmware was completed.
It was for standardising widescreen switching signals, in the early 2000s that was a big issue because each company had a different interpretation of what the flags meant. Thus when you were watching TV you would often get the wrong behaviour and distorted pictures. A small group of us sat down and agreed what the proper behaviour should be. Then every other TV standards body in the world adopted it.
> AV1 fixed a structural problem in the ecosystem at the time, but the work isn’t finished. Video demand keeps rising, and the next generation of open codecs must remain competitive.
> AOMedia is working on the upcoming release of AV2. It will feature meaningfully better compression than AV1, much higher efficiency for screen/graphical content, alpha channel support, and more.
That's all nice and good, but please make AV1 as widespread as H264, so that I can just import it in every editing program as well instead of having Adobe Premiere Pro complain about not knowing what that format is (well, I personally prefer DaVinci Resolve, but my editor is on Adobe). But yeah, I think that AV1 is great but would like support for it across the board, on every device (hardware decoding and encoding) as well as Kdenlive and Resolve and all the other editors and everything on the software side.
tbf AOMedia doesnt really make this call. The steam deck for example doesn't do AV1 natively. It could, but Valve has so far decided not to implement it. I dont know how many other devices and systems that could do AV1 but don't do it exist, but to get this level of support, we really need to pressure these companies.
It's all about hardware support really. AV1 is pretty new (2018), give it some time. E. g. Nvidia supports decoding since 3xxx generation, and encoding only since 4xxx generation.
I still vividly remember what a clusterfk was H264 support on mobile devices just ten years ago, circa 2010-2015. AVC spec was published in 2003, High Profiles standardised in 2005, universally supported only since ~2015. I personally had a 2011 Tegra 2 tablet which did support H264, but didn't support high profiles.
On a similar note Matt Parker recently released a video about Perlin Noise, which won an Oscar (for Technical Achievement) in 1996: https://www.youtube.com/watch?v=JrLSfSh43oA
It really is amazing how far compression has come in the last decades. Would love to see a chart showing the progress as I think quite a bit of it was very recent. At least, I know that the videos I make on a gopro can't be viewed without effort on a chromebook.
I think compression ratio is not as important, as being open-source and patent-free. I would prefer an open codec even if it produces 20-50% larger videos. It's not a big difference between 1 and 1.5 Mbit/s. And if it matters that much for you, then you should be paying for the patents, not everyone else (for example, by using a codec which is free to decode, but encoding software is paid).
What does Netflix has to do with AV1 codec? While Netflix’s Norkin has contributed some minor add-ons like film grain, Daala folks should have been mentioned along with x264/x264 guys who were at the origins on AV1 development, Google VP9 guys for their contributions and Intel maybe for HW porting, among others. Basically whomever pays for the show, gets to wear the crown. Nothing to see here…
21 comments
[ 2.9 ms ] story [ 51.4 ms ] threadAV1 powers approximately 30% of Netflix viewing
https://news.ycombinator.com/item?id=46155135
I wish adoption was better. When will Wikipedia support AVIF?
Who still uses paten encumbered codecs and why?
https://www.w6rz.net/DCP_1235.JPG
The original DirecTV encoder was MPEG-1 at 704x480 using eight CL4000 chips. Then in 1995 when the MPEG-2 capable CL4010 was finished, the encoders were upgraded to MPEG-2 (frame only encoding). Then upgraded again to a 12 chip AFF (Adaptive Field/Frame) encoder when the firmware was completed.
https://www.w6rz.net/videorisc.png
https://en.wikipedia.org/wiki/Technology_and_Engineering_Emm...
It was for standardising widescreen switching signals, in the early 2000s that was a big issue because each company had a different interpretation of what the flags meant. Thus when you were watching TV you would often get the wrong behaviour and distorted pictures. A small group of us sat down and agreed what the proper behaviour should be. Then every other TV standards body in the world adopted it.
I never did get a statue.
Youtube has used vp8 since 2010. Openly licensed video codes were in use through the mid-2010s.
> AOMedia is working on the upcoming release of AV2. It will feature meaningfully better compression than AV1, much higher efficiency for screen/graphical content, alpha channel support, and more.
That's all nice and good, but please make AV1 as widespread as H264, so that I can just import it in every editing program as well instead of having Adobe Premiere Pro complain about not knowing what that format is (well, I personally prefer DaVinci Resolve, but my editor is on Adobe). But yeah, I think that AV1 is great but would like support for it across the board, on every device (hardware decoding and encoding) as well as Kdenlive and Resolve and all the other editors and everything on the software side.
I still vividly remember what a clusterfk was H264 support on mobile devices just ten years ago, circa 2010-2015. AVC spec was published in 2003, High Profiles standardised in 2005, universally supported only since ~2015. I personally had a 2011 Tegra 2 tablet which did support H264, but didn't support high profiles.
https://news.ycombinator.com/item?id=46155135