UPDATE: 9/14 5 PM ET: Adding information regarding Netflix videos transcoded using AV1.

YouTube has uploaded about a dozen videos that were transcoded using the AV1 codec, whcih was introduced earlier this year. The test sequences are expected to give Google as well as developers of browsers, decoders, and encoders an understanding how to better use the new royalty-free codec. Netflix is also testing AV1 codec and offers everyone a video in different resolutions and featuring various color depth.

To date, YouTube has added 14 videos transcoded using the AV1 codec to a special playlist. The list includes various types of content, including a talking-head program, musical clips, action videos, and demo footages from RED and Blackmagic Design. YouTube says that this type of content represents a large share of videos hosted by the service, so it makes a lot of sense for the company to learn how they behave on various devices in terms of performance, power consumption, and overall stability.

At present, AV1 support is available only in those Chrome 70 and Firefox Nightly builds released after September 12th. Meanwhile, the test videos use AV1 for resolutions that are lower than 480p, underscoring the fact that they are meant to test decoders that, for the moment, are going to be anything but optimized. This is on top of the fact that at the moment there are no hardware decoders that support AV1, so everything is being handled in software by the CPU to begin with. Eventually the codec will be used for content in 4K+ ultra-high-def resolutions, along with HDR and wide color gamuts.

Netflix's approach to the AV1 codec is a bit different. The company is offering just one video, but in from 432p all the way to 1080p and featuring 8 or 10 color depth.

Finally, YouTube is promising to expand the collection of AV1-transcoded videos over time.

Related Reading:

Source: YouTube (via SH SOTN)

Comments Locked

52 Comments

View All Comments

  • DanNeely - Friday, September 14, 2018 - link

    This article's headline reminds me of why I thought av1 was a terrible name from the beginning. I read it as "AVI", and was all "LOLWUT!" because AVI is a really old format.
  • poohbear - Friday, September 14, 2018 - link

    me too! i was like 4 realz??? could they be anymore confusing???
  • Duwelon - Friday, September 14, 2018 - link

    AVI file is just a container that could hold video/audio encoded in many formats. AV1 is one such codec.

    *puffs chest, walks away*
  • inighthawki - Friday, September 14, 2018 - link

    Probably makes it even more confusing for those who don't understand the difference :)
  • stephenbrooks - Friday, September 14, 2018 - link

    Ugh. Yes, the file extension being the container type not the codec was a mistake IMO, since whenever I run into incompatibility issues with video files, it's due to missing a particular codec.

    I think they thought there'd be a billion different codecs that magically were supported everywhere so no-one would have to care what codec a video is, which is of course not true in an era when some codec support is even in hardware.
  • Santoval - Saturday, September 15, 2018 - link

    You are right about the missing codecs problem (for which the expensive proprietary codecs like HEVC are to blame), however since containers such as mkv support just about any codec, things are kept much simpler and tidier. If each codec was container-less, each with its own extension, the situation would be quite messier due to the many more file extensions.
    The only arguable benefit would be that it would be easier to know if our system, video player or browser supported the x or y codec, but at the trade-off of a much higher video related clutter.
  • SleepyFE - Saturday, September 22, 2018 - link

    Also, the container holds video, audio and subtitles. So having one video codec, 4 audio codecs and 28 subtitles without a container would be annoying, unsightly and unmanageable.
  • phoenix_rizzen - Friday, September 14, 2018 - link

    There's a "yo dawg" meme in there somewhere. :)
  • brunis.dk - Saturday, September 15, 2018 - link

    They could have done worse, like those shitty sites that use fonts where you cant tell the difference between non-capital L and capital i, like this site. Lot's of pass generation sites use it too.
  • qlum - Friday, September 14, 2018 - link

    To be fair it is compounded by the font if I type it here in the comments AVI and AV1 look reasonably different.

    A personal note here I hate font ambiguity between characters like I and l or in deed I and 1

Log in

Don't have an account? Sign up now