VDPAU vs VAAPI relationship
Basically, open source ATI drivers (), open source NVIDIA drivers ( ) and proprietary NVIDIA drivers ( ) support natively VDPAU, whereas the Intel drivers ( ) and proprietary ATI drivers ( AUR) support natively VAAPI. Then, to fill in the missing support, there is to use VAAPI as a backend for VDPAU, and to use VDPAU as a backend for VAAPI.
Further, are the last two rows of the table specific only to VA-API or is it possible even with VDPAU?
- Yeah I too guess that merging the articles would make things clearer, however how would you name the new article? Some ideas, "Hardware accelerated video processing", "Hardware video acceleration"...
- I'm sorry I can't answer your last question.
- -- Kynikos (talk) 01:55, 27 October 2013 (UTC)
- I was thinking about "Hardware video acceleration"; note that XvMC would also fall into this category, however it is now useful only for very old graphic cards.
- I've found no information about encoding with VDPAU, which actually makes sense as it stands for "Video Decode and Presentation API for Unix"...
- -- Lahwaacz (talk) 14:34, 28 October 2013 (UTC)
- I agree with this. It seems that most of the needed information is there on the page but the formatting of this group of articles makes it a bit confusing to determine which packages are necessary to make hardware acceleration work depending on situation. I agree that they should be merged into one singe "hardware video acceleration" page.
- Yeah that should be how it works, though for AMD's gallium there's also which implements VA-API. So, now that Catalyst is deprecated, it's Intel VA-API, NVIDIA VDPAU and AMD both. If I find time I might merge the two (three) sites together.
- Also, please check my revision and remove the flags if it's sufficient.
- -- DoctorJellyface (talk) 18:21, 5 May 2016 (UTC)