Announcement
Collapse
No announcement yet.
Experimental VA-API Implemented Over NVIDIA's NVDEC - Allows Firefox Video Acceleration
Collapse
X
-
VDPAU has no encoding features since it's Video Decoding and Presentation API for UNIX.
-
Originally posted by Quackdoc View Post
that's already being worked on, but vulkan extensions only supports h264 and h265 right now, vp9 and av1 isn't out yet as far as I am aware.
Leave a comment:
-
Originally posted by bug77 View PostI never understood why Nvidia felt like removing VDPAU. They could have just kept it as it was, perhaps in deprecated/legacy mode or something
- Likes 2
Leave a comment:
-
Originally posted by shmerl View PostSomething that occurred to me. Why bother with VAAPI over NVDEC/NVENC? It's a waste of effort. Why not make it over Vulkan video extensions? Then it would work in the future for all GPUs until everyone will switch to Vulkan proper.
Leave a comment:
-
Something that occurred to me. Why bother with VAAPI over NVDEC/NVENC? It's a waste of effort. Why not make it over Vulkan video extensions? Then it would work in the future for all GPUs until everyone will switch to Vulkan proper.
- Likes 1
Leave a comment:
-
Originally posted by Hibbelharry View PostThats not totally right, VA-API always had a broader scope than VDPAU.
Leave a comment:
-
Originally posted by birdie View Post
Originally posted by DanL View PostMaybe, but I think the real issue was that Intel never adopted VDPAU, even on the Linux/opensource side. The VDPAU mesa driver worked very well on my RadeonHD 4550. It was so much better than the fglrx/Catalyst driver. Even Adobe/Flash tried the VDPAU route (VAVDA?), but it didn't gain much traction when Intel said no joy.
Intel had no reason to push VA-API other than selfishness and NIH BS.
Originally posted by piotrj3 View PostAs far as I know API wise VAAPI doesn't provide anything above VPDAU. They are both simple APIs that only pass information to relevant low level code where real things are happening. Introducing VAAPI basicly gave us fragmentation.
- Likes 2
Leave a comment:
-
Originally posted by DanL View Post
Maybe, but I think the real issue was that Intel never adopted VDPAU, even on the Linux/opensource side. The VDPAU mesa driver worked very well on my RadeonHD 4550. It was so much better than the fglrx/Catalyst driver. Even Adobe/Flash tried the VDPAU route (VAVDA?), but it didn't gain much traction when Intel said no joy.
Intel had no reason to push VA-API other than selfishness and NIH BS.
Leave a comment:
-
Originally posted by smitty3268 View PostI have my suspicions it's because AMD started using it on Linux, and it was a way for them to screw with AMD.
Intel had no reason to push VA-API other than selfishness and NIH BS.
- Likes 1
Leave a comment:
Leave a comment: