Announcement

Collapse
No announcement yet.

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

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

  • #11
    Originally posted by Gusar View Post
    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.
    (◔_◔) Oh, it was a non sequitur.

    Comment


    • #12
      What does Canonical have to do with this discussion? FFmpeg supports various hardware accelerated encode and decode capabilities, Nvidia has worked with ffmpeg to add support for both nvenc_h264 and nvenc_hevc for a while now; ffmpeg also support encoding via Quick Sync using Intel's libmfx but that's only for mpeg-2, h264 and hevc, and hevc is limited to 1000 frames unless one buys the pro version of the Intel SDK for $5000. There is an alternative interface for using the underlying hardware, va-api, which allows h264 and hevc encoding on select AMD cards as well as mjpeg, mpeg-2, h264, hevc, vp8 and vp9 on supported hardware. Sky Lake supports up to vp8 encoding, Kaby Lake supports up to vp9 encoding.

      Those that have Kaby Lake with integrated gpu's and use Linux and do a lot of encoding are sitting very pretty right now.

      Comment


      • #13
        Originally posted by Spooktra View Post
        What does Canonical have to do with this discussion?
        It's called flamebait.

        Comment


        • #14
          Originally posted by defaultUser View Post

          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)
          I don't know why video players aren't sandboxed by default to be read-only.

          Comment


          • #15
            Originally posted by uid313 View Post
            I don't know why video players aren't sandboxed by default to be read-only.
            Players are usually read-only in their own code, sandboxing is an enforcement of that on the outside.

            Comment


            • #16
              Hi Guys,

              Running Kabylake testbed with VA-API (0.40) libva
              Trying to encode 4K /10bit /yuv420p /30fps video
              Encoding speed is 0.4 to 0.5 x that is encoding is around 14 frames per second

              hevc_vaapi on kabylake is supposed to encode 4k@30fps

              Any Clue??

              Comment

              Working...
              X