Announcement

Collapse
No announcement yet.

YouTube Begins Rolling Out AV1 Support In Beta

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • YouTube Begins Rolling Out AV1 Support In Beta

    Phoronix: YouTube Begins Rolling Out AV1 Support In Beta

    YouTube has begun transcoding videos into the new royalty-free AV1 video codec...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Why is it only in MP4 and not webm/matroska?

    Comment


    • #3
      The WebM spec is not finished yet, whereas the MP4 spec was just finished, IIRC just the day before YouTube started using it.

      As for why the MP4 spec was finished first, probably because Netflix wants to use it with DRM, and all DRM schemes (except Google's Widevine) assume we live in an MPEG world. MPEG Common Encryption is the umbrella standard. It helps little that Widevine supports WebM when content providers must support every DRM scheme to cover all platforms and devices.

      It was at least Netflix who wanted VP9 in mp4.
      Last edited by andreano; 13 September 2018, 12:49 PM.

      Comment


      • #4
        I wonder what encoder they're using. libaomedia-av1 or Rav1e?

        Comment


        • #5
          Originally posted by geearf View Post
          Why is it only in MP4 and not webm/matroska?
          I think this has to do with MPEG-DASH, which supports arbitrary codecs. That specification defines using either MP4 or M2TS, and YouTube seemingly uses MP4.

          Comment


          • #6
            What else do i need to make it work?

            Comment


            • #7
              For some reason i cant post attachment, nor links. I wanted to show screesnshot with all conditions fullfileld yet no AV1 playback.

              Comment


              • #8
                Well Youtube-dl seems to work okay.
                Code:
                $ youtube-dl -F 'https://www.youtube.com/watch?v=sUTismgsGpk' | grep av01
                394          mp4        256x144    144p  209k , av01.0.05M.08, 24fps, video only, 4.04MiB
                396          mp4        640x360    360p  894k , av01.0.05M.08, 24fps, video only, 15.11MiB
                397          mp4        854x480    480p 1519k , av01.0.05M.08, 24fps, video only, 25.27MiB
                It complained about formats though, probably the WebM issue that andreano mentioned.
                Code:
                $ youtube-dl -f 397+251 'https://www.youtube.com/watch?v=sUTismgsGpk' 
                ...
                WARNING: Requested formats are incompatible for merge and will be merged into mkv.
                The video played with mpv and VLC (on Debian Sid here). It's great to see the birth of a new codec!

                Comment


                • #9
                  Originally posted by Imroy View Post
                  It complained about formats though, probably the WebM issue that andreano mentioned.
                  Code:
                  $ youtube-dl -f 397+251 'https://www.youtube.com/watch?v=sUTismgsGpk'
                  ...
                  WARNING: Requested formats are incompatible for merge and will be merged into mkv.
                  The video played with mpv and VLC (on Debian Sid here). It's great to see the birth of a new codec!
                  Try 397+140, that will save into .mp4.

                  Comment


                  • #10
                    Originally posted by andreano View Post
                    The WebM spec is not finished yet, whereas the MP4 spec was just finished, IIRC just the day before YouTube started using it.

                    As for why the MP4 spec was finished first, probably because Netflix wants to use it with DRM, and all DRM solutions assume we live in an MPEG world.
                    Do the containers require specific work per new codec? I imagined they wouldn't but I guess I was wrong.
                    I didn't know DRM stuff only worked with MP4, that's interesting, though it's a bit strange to use a codec made to not be part of the MPEG world with a container coming from there

                    Originally posted by wswartzendruber View Post

                    I think this has to do with MPEG-DASH, which supports arbitrary codecs. That specification defines using either MP4 or M2TS, and YouTube seemingly uses MP4.
                    Now I am confused.
                    Wiki states
                    DASH is audio/video codec agnostic.
                    and Mozilla has a test page for AV1 and DASH: https://demo.bitmovin.com/public/firefox/av1/

                    MPEG-DASH also has a patent pool, so I don't get why it should be mixed with AV1. On that note, is there something FOSS coming out to replace it? Because it seems a really good concept, one that could also be useful for processing power I guess.

                    Comment

                    Working...
                    X