Talk:Video Acceleration API

This is the talk page for discussing improvements to the Video Acceleration API article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Computing Stub‑class

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

Articles for creation Stub‑class

	This article was reviewed by member(s) of WikiProject Articles for creation. The project works to allow users to contribute quality articles and media files to the encyclopedia and track their progress as they are developed. To participate, please visit the project page for more information.Articles for creationWikipedia:WikiProject Articles for creationTemplate:WikiProject Articles for creationAfC
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.
	This article was accepted on 21 November 2007 by reviewer Graeme Bartlett (talk · contribs).

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)[reply]

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)[reply]

MPlayer still does not support VA-API.--Regression Tester (talk) 22:37, 14 September 2010 (UTC)[reply]

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)[reply]

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)[reply]

Clarify and rewrite

Clarify

This article needs to be rewritten. Before we can do that, we need to clarify some things missing from the article.

As can be seen here video decoding can be done
- on the CPU by executing an implementation of the video codec on the CPU, feeding it the video file, getting a bit-stream back
- 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
- 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:

Functional range of the interface (instead of "Features")
Implementation by device drivers
1. Supported video acceleration modules
2. Operating systems
Adoption by end-user software (instead of "Software that supports VAAPI")
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)[reply]