Announcement

Collapse
No announcement yet.

NVIDIA VA-API 0.0.6 Driver Works On Multi-Threaded Decode, Improved GPU Selection

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

  • NVIDIA VA-API 0.0.6 Driver Works On Multi-Threaded Decode, Improved GPU Selection

    Phoronix: NVIDIA VA-API 0.0.6 Driver Works On Multi-Threaded Decode, Improved GPU Selection

    The open-source, unofficial project providing a NVIDIA VA-API driver on Linux systems built atop the proprietary driver's NVDEC video decode interface is out with a new feature release. This NVIDIA-VAAPI-Driver effort continues to be driven in large part for allowing GPU-accelerated video acceleration in Firefox and other software only targeting the open Video Acceleration API...

    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
    VAAPI is controlled by Intel. The designer of the hardware provides and supports an API and it is VDPAU.

    Comment


    • #3
      I think this is good news!

      Comment


      • #4
        Originally posted by zoomblab View Post
        VAAPI is controlled by Intel. The designer of the hardware provides and supports an API and it is VDPAU.
        VDPAU is probably what should have been standardized years ago, but no, all 3 GPU vendors had to make their own. Sigh..

        Comment


        • #5
          Originally posted by zoomblab View Post
          VAAPI is controlled by Intel. The designer of the hardware provides and supports an API and it is VDPAU.
          Just like VDPAU is controlled by Nvidia. Designers of other hardware provides and supports VAAPI.

          Both VAAPI and VDPAU are open standards that can be implemented by different cards. Since VAAPI is supported by more applications and Nvidia doesn't look very interested in VDPAU or any other API than NVDEC, then it's probably better to stick to VAAPI and project like this is needed unless Nvidia provide support for VAAPI natively which we can safely assume they probably won't.

          Comment


          • #6
            Originally posted by dragon321 View Post

            Just like VDPAU is controlled by Nvidia. Designers of other hardware provides and supports VAAPI.

            Both VAAPI and VDPAU are open standards that can be implemented by different cards. Since VAAPI is supported by more applications and Nvidia doesn't look very interested in VDPAU or any other API than NVDEC, then it's probably better to stick to VAAPI and project like this is needed unless Nvidia provide support for VAAPI natively which we can safely assume they probably won't.
            Why would Nvidia support an competing solution that is driven by Intel? Apps that want to take advantage of video acceleration on Nvidia hardware should be using VDAPU because it is the officially supported and guaranteed to work thing.

            Comment


            • #7
              Originally posted by zoomblab View Post

              Why would Nvidia support an competing solution that is driven by Intel? Apps that want to take advantage of video acceleration on Nvidia hardware should be using VDAPU because it is the officially supported and guaranteed to work thing.
              Thinking like that is why nvidia is where it is right now with linux. By that logic why does nvidia support vulkan?

              Comment


              • #8
                Originally posted by zoomblab View Post

                Why would Nvidia support an competing solution that is driven by Intel? Apps that want to take advantage of video acceleration on Nvidia hardware should be using VDAPU because it is the officially supported and guaranteed to work thing.
                Why Intel or AMD should support VDPAU then?

                Comment

                Working...
                X