Announcement

Collapse
No announcement yet.

VP9 Added To VA-API's Encode Capabilities For FFmpeg

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

  • VP9 Added To VA-API's Encode Capabilities For FFmpeg

    Phoronix: VP9 Added To VA-API's Encode Capabilities For FFmpeg

    The latest Git code for FFmpeg now supports VA-API accelerated VP9 encoding...

    http://www.phoronix.com/scan.php?pag...peg-VP9-Encode

  • #2
    And what was the motive for Canonical to pursue that proprietary Intel API?

    Comment


    • #3
      I want a high security sandboxed video player that can only access the ~/Videos/ directory with read permissions.

      Comment


      • #4
        Originally posted by uid313 View Post
        I want a high security sandboxed video player that can only access the ~/Videos/ directory with read permissions.
        Nominally even docker can foot your bill. However you are probably looking for things like firejail (https://firejail.wordpress.com/) or (http://sandbox.libvirt.org)

        Comment


        • #5
          Originally posted by M@GOid View Post
          And what was the motive for Canonical to pursue that proprietary Intel API?
          vaapi is supported by the amd drivers and all major video players. it would be a surprise to use vdpau or whatever else

          Comment


          • #6
            What about AMD cards?

            Comment


            • #7
              Originally posted by M@GOid View Post
              And what was the motive for Canonical to pursue that proprietary Intel API?
              I don't know... maybe because it is open source and used by other vendors besides Intel?

              Comment


              • #8
                Originally posted by shmerl View Post
                What about AMD cards?
                They were supposed to enable it with a firmware update in their latest hardware but still nothing AFAIK. bridgman or anyone else from AMD might be able to tell more.

                Comment


                • #9
                  Originally posted by gbcox View Post
                  I don't know... maybe because it is open source and used by other vendors besides Intel?
                  What M@GOid means by "proprietary Intel API" is *not* VAAPI, but QSV/Intel SDK. QSV is indeed proprietary and very much not used by other vendors. And he's questioning why Canonical is messing with that, rather than focusing on VAAPI.

                  BTW, ffmpeg supports QSV too, but why go through the hassle with that (kernel patches, proprietary fork of libva), when there's VAAPI. The only thing is, QSV support has been in ffmpeg since quite some time, while VAAPI encoding is a relatively new addition to ffmpeg.

                  Comment


                  • #10
                    Originally posted by M@GOid View Post
                    And what was the motive for Canonical to pursue that proprietary Intel API?
                    The same urge that pushes them to do incompatible and not-that-used software in the latest decade or so, I guess. They try to make something unique that only them have to attract something (users or sponsors or both).

                    Too bad that in opensource it does not usually work like that in the low levels of the OS.

                    Comment

                    Working...
                    X