Video Acceleration API: Difference between revisions

Revision as of 02:05, 21 January 2021

Revision as of 09:22, 28 February 2021

Line 22:

== Overview ==

[[File:Vainfo screenshot.png|thumb|An example of vainfo output, showing supported video codecs for VA-API acceleration]]

The main motivation for VA-API is to enable hardware-accelerated video decode at various entry-points ([[Variable-length code|VLD]], [[IDCT]], [[motion compensation]], [[Deblocking filter (video)|deblocking]]<ref name="MPlayer, FFmpeg Gain VA-API Support">{{cite web|url=https://www.phoronix.com/scan.php?page=article&item=xorg_vaapi_mplayer&num=1|title=Mplayer, FFmpeg Gain VA-API Support - Phoronix|website=Phoronix.com|access-date=23 February 2019}}</ref>) for the prevailing coding standards today ([[H.262/MPEG-2 Part 2|MPEG-2]], [[MPEG-4 Part 2|MPEG-4 ASP]]/[[H.263]], [[H.264/MPEG-4 AVC|MPEG-4 AVC/H.264]], [[High Efficiency Video Coding|H.265/HEVC]], and [[VC-1|VC-1/WMV3]]). Extending XvMC was considered, but due to its original design for MPEG-2 [[Motion Compensation|MotionComp]] only, it made more sense to design an interface from scratch that can fully expose the video decode capabilities in today's [[Graphics processing unit|GPU]]s.<ref name="freedesktop.org">{{cite web|url=https://www.freedesktop.org/wiki/Software/vaapi/|title=vaapi|website=Freedesktop.org|access-date=23 February 2019}}</ref>