Talk:Video Acceleration API

intel??
I find it disturbing that intel (the creator of VA API) is only mentioned in the sources, unlike the NVIDIA and ATI/AMD wiki pages. —Preceding unsigned comment added by 207.172.176.168 (talk) 02:55, 22 February 2009 (UTC)

MPlayer
MPlayer currently (2010-04-16) does not support VA-API. There are patches that add support on third-party web sites, but this cannot count as supported. --Regression Tester (talk) 13:37, 16 April 2010 (UTC)
 * MPlayer still does not support VA-API.--Regression Tester (talk) 22:37, 14 September 2010 (UTC)
 * There has been mplayer vaapi support for more than a year. http://www.splitted-desktop.com/~gbeauchesne/mplayer-vaapi/ Jeff Carr (talk) 19:10, 17 November 2010 (UTC)

FFmpeg
FFmpeg does not support VA-API. There is no command line option that uses or activates VA-API. libavcodec contains code that is used by several applications to use VA-API. --Regression Tester (talk) 23:43, 3 July 2010 (UTC)

Clarify
This article needs to be rewritten. Before we can do that, we need to clarify some things missing from the article.
 * 1) As can be seen here video decoding can be done
 * 2) * on the CPU by executing an implementation of the video codec on the CPU, feeding it the video file, getting a bit-stream back
 * 3) * on the "3D engine" (i.e. the GPU) by executing an implementation of the video codec on the 3D engine, feeding it the video file, getting a bit-stream back
 * 4) * on the "video acceleration module", be it a distinct chip or SIP block on the die of the GPU/CPU/APU/SoC (Nvidia PureVideo, Unified Video Decoder or Texas Instruments "Ducati" are SIP blocks, and I think Intel Quick Sync Video is a distinct SIP block as well) by simply feeding the video file through an API, getting a bit-stream back

The last two methods are often confused by Marketing, since both SIP blocks, "3D engine" and "video acceleration module" are part of the GPU's die. But they do differ in the amount of electrical current consumed and heat dissipated, and also, the latter, should not require a software implementation of the codec, because it is already implemented as IC/on some firmware.

AFAIK, VDPAU and VAAPI are interfaces to do both: using the "3D engine" as all well the "video acceleration module" but I am not completely sure since both methods are very different. I would not define one API to do both.

Rewrite
Once this is clarified, this article needs some structure, I suggest:
 * 1) Functional range of the interface (instead of "Features")
 * 2) Implementation by device drivers
 * 3) Supported video acceleration modules
 * 4) Operating systems
 * 5) Adoption by end-user software (instead of "Software that supports VAAPI")
 * 6) History

At least the article VDPAU should be rewritten accordingly. Maybe X-Video Bitstream Acceleration and X-Video Motion Compensation as well, but these are extension of an extension for X11 making the whole stuff probably more complicated. A Navbar could also be nice, replacing the current sausage under the "See also" section. User:ScotXW t@lk 09:21, 28 June 2014 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 1 one external link on Video Acceleration API. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20120620155937/http://intellinuxgraphics.org/h264.html to http://intellinuxgraphics.org/h264.html

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).

Cheers.— InternetArchiveBot  (Report bug) 07:37, 21 July 2016 (UTC)