From ArchWiki
Jump to: navigation, search

VDPAU vs VAAPI relationship

We have two very similar pages, VDPAU and VA-API, with no clear description of the relationship between VDPAU and VAAPI.

Basically, open source ATI drivers (ati-dri), open source NVIDIA drivers (nouveau-dri) and proprietary NVIDIA drivers (nvidia-utils) support natively VDPAU, whereas the Intel drivers (intel-dri) and proprietary ATI drivers (catalyst-utilsAUR) support natively VAAPI. Then, to fill in the missing support, there is libvdpau-va-gl to use VAAPI as a backend for VDPAU, and libva-vdpau-driver to use VDPAU as a backend for VAAPI.

Assuming this is correct, VDPAU and VA-API should be merged into one article and describe these differences properly. Having two articles on such a similar subject is pretty confusing.

Further, are the last two rows of the table specific only to VA-API or is it possible even with VDPAU?

-- Lahwaacz (talk) 11:13, 26 October 2013 (UTC)

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)
True, XvMC should probably be merged too. About encoding with VDPAU, your reasoning seems pretty fair (also confirmed by googling it around), and anyway users will still have the chance to update the article, in case it's really an available feature. -- Kynikos (talk) 13:36, 29 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.
-- --TheChickenMan (talk) 19:17, 25 April 2016 (UTC)
Yeah that should be how it works, though for AMD's gallium there's also libva-mesa-driver 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)