Announcement

Collapse
No announcement yet.

Vulkan Video Support Progressing For Open-Source Intel, AMD Radeon Hardware

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

  • #11
    Originally posted by ResponseWriter View Post
    Maybe it's a bug but the AV1 decoding through VA-API with mpv on 6800 XT results in very choppy video for me. Apart from that, VA-API does work OK on AMD but I hope Vulkan will become the future target for all vendors.
    If you have at least Mesa 21.3, FFmpeg 4.4 and preferably the latest mpv version, then it's probably a bug.

    Comment


    • #12
      And once again, the priority is given to patent-encumbered non-free codecs such as h.264 and h.265, while treating the royalty-free VP9 and AV1 codecs as second-rate afterthoughts.

      We don't pay royalties for pictures, do we? Or for vector-based graphics formats? Or file systems? Or 3D acceleration APIs? Then why is it okay for everyone to tolerate having to pay royalties for video codecs? Bah.

      Comment


      • #13
        Originally posted by SteamPunker View Post
        And once again, the priority is given to patent-encumbered non-free codecs such as h.264 and h.265, while treating the royalty-free VP9 and AV1 codecs as second-rate afterthoughts.
        Unfortunately, if you want hardware-accelerated video, which is kinda the whole point of this, you need there to actually be, y'know, hardware support. And regardless of how much better you think VP9 etc are, no manufacturer is going to waste design time and die space on formats that users don't care about because nothing uses them.

        Not saying you're wrong in concept, but AV1 was so late to market that it lost by simply never even showing up. That's not the fault of the hardware designers, and certainly not arlied's fault either.

        Comment


        • #14
          Originally posted by [TV] View Post

          If you have at least Mesa 21.3, FFmpeg 4.4 and preferably the latest mpv version, then it's probably a bug.
          I'm on Mesa git as of about a week ago, current ffmpeg and mpv. Looks like this bug.

          Comment


          • #15
            Originally posted by arQon View Post

            Unfortunately, if you want hardware-accelerated video, which is kinda the whole point of this, you need there to actually be, y'know, hardware support. And regardless of how much better you think VP9 etc are, no manufacturer is going to waste design time and die space on formats that users don't care about because nothing uses them.

            Not saying you're wrong in concept, but AV1 was so late to market that it lost by simply never even showing up. That's not the fault of the hardware designers, and certainly not arlied's fault either.
            The entire industry (including Microsoft and even Apple, go figure) have been rallying behind AV1.

            In the case of h.264 vs. VP8, you may have a point w.r.t. being late to market. But VP9 already competes with h.265 and actually had a bit of a head start over it, while h.265 uptake has been hampered by headaches and bickering over patent licensing, which is even worse than was the case with h.264.

            As for AV1, which is newer and was specifically designed to beat h.265, both YouTube and Netflix (arguably the two most popular video streaming services on the Internet) have already started to adopt it, in anticipation of products with AV1 hardware acceleration support reaching the market.

            The licensing woes around h.265 make it even more baffling to me that the industry is still trying to push h.265 over AV1 right now.

            Long story short: yeah, you really can't avoid having to make h.264 a priority, but open source developers and standard committees should really be prioritizing both VP9 and AV1 over h.265/HEVC.
            SteamPunker
            Phoronix Member
            Last edited by SteamPunker; 30 November 2021, 04:56 PM.

            Comment

            Working...
            X