Talk:X-Video Motion Compensation
 | This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
Cleanup intro
editXvMC is a software library provided by the X11 system to provide user applications with a standard Application Programming Interface, or API, to hardware specific features." XvMC is not the library, it is only the API that each proprietary hardware must plug into, using their XvMC library. I think something more accurate would be: XvMC is an API within the X11 system, which allows compute intensive operations in video decoding to be offloaded to hardware. The library to integrate the hardware acceleration must be developed for each GPU, interfacing the proprietary hardware to the standard XvMC API. —Preceding unsigned comment added by Gamester17 (talk • contribs)
Additional information
edit- Mac OS X also support XvMC
No, it doesn't. Mac OS X has no supported APIs to allow MPEG2 acceleration. Apple's DVD Player application does have the ability to use MPEG2 acceleration hardware, but this is not using the XvMC API, and is not open for any other application to use. There has been an effort to reverse engineer that interface, which has had some success, but is not stable enough for real usage.
- XvMC 2.0 -- Discussed on Xorg mailing list. Status? (standard API regardless of hardware, VLD support, etc.) http://lists.freedesktop.org/archives/xorg/2005-February/thread.html#6007
- Page on the PenLUG wiki http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoNvidia5200 that might help explain how to get good playback of interlaced 1080 with mplayer and xine using the proprietary Nvidia driver for the 5200 card —Preceding unsigned comment added by Gamester17 (talk • contribs)
- VAAPI -- Intel developers have proposed a new video acceleration API, which improves upon many XvMC limitations. http://www.freedesktop.org/wiki/Software/vaapi
- AMD/ATI open drivers. ATI/AMD have released a lot of information about their hardware. Has any of this enabled XvMC support in Radeon GPUs?
Request made to NVIDIA to open up their PureVideo API
edithttp://forums.nvidia.com/index.php?showtopic=35695 http://forums.nvidia.com/index.php?showtopic=35698 —Preceding unsigned comment added by Gamester17 (talk • contribs)
Edits
edit", which is better suited to this kind of decoding than modern general-purpose CPUs. " I removed this because i cant see that the difference is _that_ big honestly.
"Even on the most modern of general-purpose CPUs, the use of XvMC is required to decode video at native 1080p resolutions in real time.[citation needed]" I removed this because its not true, i can play full hd content on my old 1,8GHz Athlon XP. 83.223.19.13 20:24, 28 May 2007 (UTC)
VIA Correction
editCorrection: MPEG-4 AVC (H.264) isn't supported at all. Neither in the OpenChrome Project, MultiChrome, nor the VIA's own closed source driver. This is a absolutely misleading information. People who buy a VIA graphics card in order to play back h.264 content with hardware acceleration on Linux, won't be able to. There is no XvMC, neither any other hardware support for h.264 aka mpeg-4 avc playback!
MythTV
editXvMC support has been dropped from the current release of MythTV (As seen in the Release Notes - 0.25) --108.11.253.161 (talk) 06:15, 30 September 2012 (UTC)
Clarify and rewrite
editPlease see Talk:Video Acceleration API#Clarify and rewrite User:ScotXWt@lk 09:24, 28 June 2014 (UTC)
External links modified
editHello fellow Wikipedians,
I have just modified 6 external links on X-Video Motion Compensation. 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 http://web.archive.org/web/20150926115747/http://www.openchrome.org/trac/wiki/About to http://www.openchrome.org/trac/wiki/About
- Added archive http://web.archive.org/web/20070515081459/http://www.xfree86.org:80/~mvojkovi/XvMC_API.txt to http://www.xfree86.org/~mvojkovi/XvMC_API.txt
- Added archive http://web.archive.org/web/20070515081459/http://www.xfree86.org:80/~mvojkovi/XvMC_API.txt to http://www.xfree86.org/~mvojkovi/XvMC_API.txt
- Added archive http://web.archive.org/web/20110409080000/http://developer.amd.com/gpu/AMDAPPSDK/assets/OpenVideo_Decode_API.PDF to http://developer.amd.com/gpu/AMDAPPSDK/assets/OpenVideo_Decode_API.PDF
- Added archive http://web.archive.org/web/20070509110311/http://www.openchrome.org:80/ to http://www.openchrome.org/
- Added archive http://web.archive.org/web/20070804001102/http://wiki.openchrome.org:80/tikiwiki/tiki-index.php?page=HardwareCaveats to http://wiki.openchrome.org/tikiwiki/tiki-index.php?page=HardwareCaveats
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).
- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—InternetArchiveBot (Report bug) 13:27, 21 July 2016 (UTC)