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.
> 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.
Some Sony TV's only hardware accelerate AV1 content through streaming services, and not through Blueray and USB...
Right now, I have a drive filled with H264 content that I can hook up to any old hotel TV and play back. It's gonna be a while before I switch to AV1. And is H264 by now largely out of patent anyway?
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.
Are you aware that you are barking up the wrong tree? AOMedia already made AV1 a free and open standard, if Adobe does not want to do an engineer's afternoon worth of work to link a C library into their executable, then that's on their head, not AOMedia's.
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.
AdobeWebM is adding AV1 support for webm files in premiere and after effects btw. It already has vp9 and 8 support! But yeah I'm hoping it becomes ubiquitous in the future.
I recently learnt that one can download WOFF files from any website that uses them, and convert them into TTF files (using an online tool like CloudConvert) if we wanted to use them in say a MS Word or Powerpoint slide deck.
This allowed me to create a custom powerpoint theme / template that captures the essence of a particular brand.
Well, VP8 was only released as an open codec in 2010, and subject of patent lawsuits until late 2014.
In 2010 the majority of (YouTube and other) videos were still served as H.264, because no major browser supported it back then and the majority of video playback devices were already smartphones (without vp8 decoding capabilities)
iOS for example didn't support VP8 until iOS12 in 2019, Firefox and MS IE only added it in 2011. Even Google only added VP8 to Chrome in September 2010.
There's actually two Engineering Emmy Awards. There's also the 'Primetime Engineering Emmy Awards' given by the ATAS (Academy of Television Arts and Sciences) while 'Technology and Engineering Emmy Awards' are given by NATAS (National Academy of Television Arts and Sciences), not confusing at all.
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 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).
To you a 33% drop from 1.5 to 1 is not much, but when you're paying for bandwidth usage that is a pretty good bit of savings. I'm not sure of anyone legitimate that's pushing that kind of data isn't using a licensed encoder.
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.
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
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…
video decoding on a general-purpose cpu is difficult, so most devices that can play video include some sort of hardware video decoding chip. if you want your video to play well, you need to deliver it in a format that can be decoded by that chip, on all the devices that you want to serve.
so it takes a long time to transition to a new codec - new devices need to ship with support for your new codec, and then you have to wait until old devices get lifecycled out before you can fully drop support for old codecs.
The whole video/movie industry is rife with mature, hardware-implemented patents. The kind that survive challenges. They are also owned by deep pockets (not fly-by-night patent trolls). Fortunately, the industry is mature enough, that some of the older patents are aging out.
The image processing industry is similar, but not as mature. I hated dealing with patents, when I was writing image processing stuff.
For whatever reason, the file sharing community seems to strongly prefer H.265 to AV1. I am assuming that either the compression at a preferred quality, or the quality at preferred bitrates is marginally better than AV1, and that people who don't care about copyright also don't care about patents.
Timing. Patent encumbered codecs get a foothold through physical media and broadcast first. Then hw manufactures license it. Then everyone is forced to license them. Free codecs have a longer path to market as they need to avoid the patents and get hw and sw support.
Backwards compatibility. If you host a lot of compressed video content, you probably didn't store the uncompressed versions so any new encoding is a loss of fidelity. Even if you were willing to take that gamble, you have to wait until all your users are on a modern enough browser to use the new codec. Frankly, the winner that takes all is H.264 because it's already everywhere.
AV1 is still worse in practice than H.265 for high-fidelity (high bitrate) encoding. It's being improved, but even at high bitrates it has a tendency to blur.
> In 1990, both Ritchie and Thompson received the IEEE Richard W. Hamming Medal from the Institute of Electrical and Electronics Engineers (IEEE), "for the origination of the UNIX operating system and the C programming language".
> In 1997, both Ritchie and Thompson were made Fellows of the Computer History Museum, "for co-creation of the UNIX operating system, and for development of the C programming language."
> On April 21, 1999, Thompson and Ritchie jointly received the National Medal of Technology of 1998 from President Bill Clinton for co-inventing the UNIX operating system and the C programming language
> 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?
[+] [-] drmpeg|3 months ago|reply
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
[+] [-] KronisLV|3 months ago|reply
> 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.
[+] [-] brnt|3 months ago|reply
Right now, I have a drive filled with H264 content that I can hook up to any old hotel TV and play back. It's gonna be a while before I switch to AV1. And is H264 by now largely out of patent anyway?
[+] [-] reisse|3 months ago|reply
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.
[+] [-] bmn__|3 months ago|reply
[+] [-] zoeysmithe|3 months ago|reply
[+] [-] adzm|3 months ago|reply
[+] [-] ErroneousBosh|3 months ago|reply
[+] [-] dchest|3 months ago|reply
[+] [-] albert_e|3 months ago|reply
This allowed me to create a custom powerpoint theme / template that captures the essence of a particular brand.
[+] [-] charcircuit|3 months ago|reply
Youtube has used vp8 since 2010. Openly licensed video codes were in use through the mid-2010s.
[+] [-] rickdeckard|3 months ago|reply
In 2010 the majority of (YouTube and other) videos were still served as H.264, because no major browser supported it back then and the majority of video playback devices were already smartphones (without vp8 decoding capabilities)
iOS for example didn't support VP8 until iOS12 in 2019, Firefox and MS IE only added it in 2011. Even Google only added VP8 to Chrome in September 2010.
So the statement is correct IMO
[+] [-] tosh|3 months ago|reply
https://en.wikipedia.org/wiki/Technology_and_Engineering_Emm...
[+] [-] notpeter|3 months ago|reply
https://en.wikipedia.org/wiki/Primetime_Engineering_Emmy_Awa...
https://en.wikipedia.org/wiki/National_Academy_of_Television...
[+] [-] bobdvb|3 months ago|reply
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.
[+] [-] andsoitis|3 months ago|reply
https://theemmys.tv/tech/
[+] [-] codedokode|3 months ago|reply
[+] [-] dylan604|3 months ago|reply
[+] [-] giantrobot|3 months ago|reply
[+] [-] ksec|3 months ago|reply
[+] [-] taeric|3 months ago|reply
[+] [-] xiphmont|3 months ago|reply
[+] [-] alastairp|3 months ago|reply
[+] [-] oscord|3 months ago|reply
[+] [-] Dwedit|3 months ago|reply
* Multi-Symbol Entropy Coder
* Chroma from Luma
* CDEF filter (directional dering filter)
What didn't make it in?
* Lapped Transform
* Use of vector quantization for residuals (aligning the vectors)
[+] [-] brcmthrowaway|3 months ago|reply
Who still uses paten encumbered codecs and why?
[+] [-] notatoad|3 months ago|reply
so it takes a long time to transition to a new codec - new devices need to ship with support for your new codec, and then you have to wait until old devices get lifecycled out before you can fully drop support for old codecs.
[+] [-] ChrisMarshallNY|3 months ago|reply
The image processing industry is similar, but not as mature. I hated dealing with patents, when I was writing image processing stuff.
[+] [-] NoGravitas|3 months ago|reply
[+] [-] bubblethink|3 months ago|reply
[+] [-] DoctorOW|3 months ago|reply
[+] [-] MallocVoidstar|3 months ago|reply
[+] [-] bibimsz|3 months ago|reply
[+] [-] looperhacks|3 months ago|reply
> In 1997, both Ritchie and Thompson were made Fellows of the Computer History Museum, "for co-creation of the UNIX operating system, and for development of the C programming language."
> On April 21, 1999, Thompson and Ritchie jointly received the National Medal of Technology of 1998 from President Bill Clinton for co-inventing the UNIX operating system and the C programming language
https://en.wikipedia.org/wiki/Dennis_Ritchie#Awards
I think that's also good ;) Ritchie and Thompson also received a Turing Award; not for the C-language, but for UNIX and OS development in general.
[+] [-] unknown|3 months ago|reply
[deleted]
[+] [-] DonHopkins|3 months ago|reply
[+] [-] ambicapter|3 months ago|reply
[+] [-] andsoitis|3 months ago|reply
https://news.ycombinator.com/item?id=46155135
[+] [-] ChrisArchitect|3 months ago|reply
AV1 powers approximately 30% of Netflix viewing
https://news.ycombinator.com/item?id=46155135
[+] [-] shmerl|3 months ago|reply
I wish adoption was better. When will Wikipedia support AVIF?
[+] [-] bjoli|3 months ago|reply
[+] [-] gsich|3 months ago|reply