Announcement

Collapse
No announcement yet.

Mesa 18.3.4 Brings VA-API VP9 Improvements, More Coffeelake/Icelake IDs For Intel

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

  • Mesa 18.3.4 Brings VA-API VP9 Improvements, More Coffeelake/Icelake IDs For Intel

    Phoronix: Mesa 18.3.4 Brings VA-API VP9 Improvements, More Coffeelake/Icelake IDs For Intel

    For those sticking to the Mesa 18.3 series until the Mesa 19.0 release is officially out and sufficiently matured, Mesa 18.3.4 is now available as the latest point release for these open-source 3D drivers...

    http://www.phoronix.com/scan.php?pag...8.3.4-Released

  • #2
    Do any AMD GPUs support VPx through VA-API? I don't see anything like that with vainfo for Vega 56.

    Comment


    • #3
      shmerl No, unless anything changed with the Radeon VII but I find that very unlikely.

      Comment


      • #4
        Originally posted by Brisse View Post
        shmerl No, unless anything changed with the Radeon VII but I find that very unlikely.
        Is it because AMD are waiting to settle on AV1, so they don't bother with VPx, or some other reasons?

        Comment


        • #5
          The problem is that there is absolutely no documentation on VCE 4.0 onward...

          Comment


          • #6
            Originally posted by shmerl View Post
            Do any AMD GPUs support VPx through VA-API?
            Raven Ridge
            Code:
            vainfo: VA-API version: 1.4 (libva 2.4.0)
            vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD RAVEN (DRM 3.27.0, 4.20.6-arch1-1-ARCH, LLVM 7.0.1)
            vainfo: Supported profile and entrypoints
                  VAProfileMPEG2Simple            : VAEntrypointVLD
                  VAProfileMPEG2Main              : VAEntrypointVLD
                  VAProfileVC1Simple              : VAEntrypointVLD
                  VAProfileVC1Main                : VAEntrypointVLD
                  VAProfileVC1Advanced            : VAEntrypointVLD
                  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
                  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
                  VAProfileH264Main               : VAEntrypointVLD
                  VAProfileH264Main               : VAEntrypointEncSlice
                  VAProfileH264High               : VAEntrypointVLD
                  VAProfileH264High               : VAEntrypointEncSlice
                  VAProfileHEVCMain               : VAEntrypointVLD
                  VAProfileHEVCMain               : VAEntrypointEncSlice
                  VAProfileHEVCMain10             : VAEntrypointVLD
                  VAProfileJPEGBaseline           : VAEntrypointVLD
                  VAProfileVP9Profile0            : VAEntrypointVLD
                  VAProfileVP9Profile2            : VAEntrypointVLD
                  VAProfileNone                   : VAEntrypointVideoProc

            Comment


            • #7
              Originally posted by Gusar View Post
              Raven Ridge
              So why not discrete GPUs? It's weird they put more hardware in mobile ones. Or their idea is that in desktop use case hardware video encoders and decoders aren't needed?

              Comment


              • #8
                Originally posted by shmerl View Post
                So why not discrete GPUs?
                Because they haven't made any yet since they created VCN (the video engine in Raven Ridge). Even Radeon VII is an old design, despite being released just recently. Navi will very, very likely have VCN and thus VP9 decoding.

                Comment


                • #9
                  Originally posted by Gusar View Post
                  Because they haven't made any yet since they created VCN (the video engine in Raven Ridge). Even Radeon VII is an old design, despite being released just recently. Navi will very, very likely have VCN and thus VP9 decoding.
                  Why bother when VC1 is the successor to VP9--the same codec that Google has abandoned further development on?

                  Comment


                  • #10
                    Originally posted by Marc Driftmeyer View Post
                    Why bother when VC1 is the successor to VP9--the same codec that Google has abandoned further development on?
                    You mean AV1. VC1 is an old codec that originated at Microsoft.

                    And the reason for "why bother" is simple - they bothered already, VCN 1.0 has VP9 decoding. And just because Google is focusing on AV1 doesn't mean that VP9 video will disappear anytime soon. So VCN 2.0, or however it'll be called, will keep the VP9 decoder and maybe (though I doubt it, it's too soon) add AV1 decoding.

                    Comment

                    Working...
                    X