VDPAU

Last updated
VDPAU
Original author(s) Nvidia
Developer(s) freedesktop.org
Initial releaseSeptember 17, 2009;15 years ago (2009-09-17) [1]
Stable release
1.5 / March 7, 2022;2 years ago (2022-03-07) [2]
Written in C, C++
Operating system Cross-platform
Type
License MIT License
Website www.freedesktop.org/wiki/Software/VDPAU/

Video Decode and Presentation API for Unix (VDPAU) is a royalty-free application programming interface (API) as well as its implementation as free and open-source library (libvdpau) distributed under the MIT License. [1] VDPAU is also supported by Nvidia. [3]

Contents

The VDPAU interface is to be implemented by device drivers, such as the Nvidia GeForce driver, nouveau, or amdgpu, to offer end-user software, such as VLC media player or GStreamer, a standardized access to available video decompression acceleration hardware in the form of application-specific integrated circuit (ASIC) blocks on graphics processing units (GPU), such as Nvidia's PureVideo or AMD's Unified Video Decoder and make use of it.

VDPAU is targeted at Unix-like operating systems (including Linux, FreeBSD, and Solaris). [4] [5] [6]

Functional range of the interface

VDPAU allows video programs to access the specialized video decoding ASIC on the GPU to offload portions of the video decoding process and video post-processing from the CPU to the GPU. [7]

Currently, the portions capable of being offloaded by VDPAU onto the GPU are motion compensation (mo comp), inverse discrete cosine transform (iDCT), VLD (variable-length decoding) and deblocking for MPEG-1, MPEG-2, MPEG-4 ASP (MPEG-4 Part 2), H.264/MPEG-4 AVC and VC-1, WMV3/WMV9 encoded videos. [4] Which specific codecs of these that can be offloaded to the GPU depends on the generation version of the GPU hardware.

History

VDPAU was originally designed by Nvidia for their PureVideo SIP block present on their GeForce 8 series and later GPUs. [8]

On March 9, 2015, Nvidia released VDPAU version 1.0 which supports High Efficiency Video Coding (HEVC) decoding for the Main, Main 4:4:4, Main Still Picture, Main 10, and Main 12 profiles. [9]

Device drivers and video controllers implementing VDPAU

VDPAU is implemented in X11 software device drivers, but relies on acceleration features in the hardware GPU.

All Nvidia graphic cards for which the driver implements VDPAU are listed in Nvidia PureVideo. [10]

S3 Graphics added VDPAU to the Linux drivers of their Chrome 400 video cards. As of version 14.02.17 of its Linux device driver, VDPAU is available with the S3 Chrome 430 GT, S3 Chrome 440 GTX, S3 Chrome 530 GT and the S3 Chrome 540 GTX hardware. [11]

ATI/AMD released an open source driver for Radeon HD 4000+ graphic cards featuring VDPAU acceleration. [12] [13]

Intel does not offer VDPAU drivers, they only support their VA-API. It is, however, possible to use Intel's VA-API drivers by way of libvdpau-va-gl.

Nvidia hopes other GPU designers will make their products compatible with the open source VDPAU library and provide drivers with VDPAU acceleration by mentioning example names of hardware specific drivers for Intel and ATI: libvdpau_intel.so and libvdpau_ati.so. [14] Intel has stated they are considering VDPAU. [15]

sunxi SoCs (Allwinner) have experimental VDPAU implementation. [16]

Mesa as of v8.0 includes VDPAU for video cards that utilize Gallium3D.

Generic VDPAU driver

As of late 2013, there is an independently developed back-end driver that in turn uses OpenGL (for drawing and scaling), and VA-API if available (for decoding). [17] It has been reported to work on some Intel graphics and Adobe Flash Player. [18]

The accelerated scaling with just OpenGL functionality is needed mostly because of Flash player, which uses un-accelerated scaling if VDPAU is unavailable. Almost all other video software that runs on Linux or FreeBSD supports Xv. It's essential for full-screen video on slower computers without native VDPAU support.

The VDPAU to VA-API translation for HW decoding is useful with recent Intel graphics hardware, as some software supports HW decoding through VDPAU but not VA-API.

Software that supports VDPAU

VDPAU can also be used as a backend for VA-API and OpenMAX IL, which themselves cover a subset of the VDPAU capabilities; so any software that uses the VA-API or OpenMAX IL is also partly capable of using VDPAU (e.g., VLC media player). [31]

Nvidia VDPAU Feature Sets

Nvidia VDPAU Feature Sets [32] are different hardware generations of GPU's supporting different levels of (Nvidia PureVideo) hardware decoding capabilities. For feature sets A, B and C, the maximum video width and height are 2048 pixels, minimum width and height 48 pixels, and all codecs are currently limited to a maximum of 8192 macroblocks (8190 for VC-1/WMV9). Partial acceleration means that VLD (bitstream) decoding is performed on the CPU, with the GPU only performing IDCT, motion compensation and deblocking. Complete acceleration means that the GPU performs all of VLD, IDCT, motion compensation and deblocking.

Feature Set A
Supports complete acceleration for H.264 and partial acceleration for MPEG-1, MPEG-2, VC-1/WMV9.
Feature Set B
Supports complete acceleration for MPEG-1, MPEG-2, VC-1/WMV9 and H.264.
Note that all Feature Set B hardware cannot decode H.264 for the following widths: 769-784, 849-864, 929-944, 1009-1024, 1793-1808, 1873-1888, 1953-1968, 2033-2048 pixels.
Feature Set C
Supports complete acceleration for MPEG-1, MPEG-2, MPEG-4 Part 2 (a.k.a. MPEG-4 ASP), VC-1/WMV9 and H.264.
Global motion compensation and Data Partitioning are not supported for MPEG-4 Part 2.
Feature Set D
Similar to feature set C but added support for decoding H.264 with a resolution of up to 4032 × 4080 and MPEG-1/MPEG-2 with a resolution of up to 4032 × 4048 pixels.
Feature Set E
Similar to feature set D but added support for decoding H.264 with a resolution of up to 4096 × 4096 and MPEG-1/MPEG-2 with a resolution of up to 4080 × 4080 pixels. GPUs with VDPAU feature set E support an enhanced error concealment mode which provides more robust error handling when decoding corrupted video streams. [33]
Feature Set F
Introduced dedicated HEVC Main (8-bit), Main 10 (10-bit) and VP9 Profile 0 (8-bit) video decoding up to 4096 × 2304 pixels resolution. [34]
Feature Set G
Hardware support for HEVC Main 12 (12-bit) and VP9 Profile 2 (12-bit) video decoding are added. [34]
Feature Set H
Feature Set H are capable of hardware-accelerated decoding of 8192x8192 (8k resolution) H.265/HEVC video streams. [35]
Feature Set I
Similar to feature set H. [34]
Feature Set J
Feature Set J adds HEVC 444 decode support. [34]
Feature Set K
Feature Set K are capable of hardware-accelerated decoding of 8192x8192 (8k resolution) AV1 MAIN Profile video streams. [34]

libvdpau standalone VDPAU library

The libvdpau standalone VDPAU library is distributed by Nvidia independently of their proprietary Linux graphics driver in an effort to help the adoption of VDPAU by those outside of Nvidia. This open source library package contains a wrapper library and a debugging library allowing other manufacturers to implement VDPAU in their device drivers. [8] [36] [37] [38]

See also

Related Research Articles

<span class="mw-page-title-main">Graphics processing unit</span> Specialized electronic circuit; graphics accelerator

A graphics processing unit (GPU) is a specialized electronic circuit initially designed for digital image processing and to accelerate computer graphics, being present either as a discrete video card or embedded on motherboards, mobile phones, personal computers, workstations, and game consoles. After their initial design, GPUs were found to be useful for non-graphic calculations involving embarrassingly parallel problems due to their parallel structure. Other non-graphical uses include the training of neural networks and cryptocurrency mining.

OpenMAX, often shortened as "OMX", is a non-proprietary and royalty-free cross-platform set of C-language programming interfaces. It provides abstractions for routines that are especially useful for processing of audio, video, and still images. It is intended for low power and embedded system devices that need to efficiently process large amounts of multimedia data in predictable ways, such as video codecs, graphics libraries, and other functions for video, image, audio, voice and speech.

<span class="mw-page-title-main">Mesa (computer graphics)</span> Free and open-source library for 3D graphics rendering

Mesa, also called Mesa3D and The Mesa 3D Graphics Library, is an open source implementation of OpenGL, Vulkan, and other graphics API specifications. Mesa translates these specifications to vendor-specific graphics hardware drivers.

<span class="mw-page-title-main">Free and open-source graphics device driver</span> Software that controls computer-graphics hardware

A free and open-source graphics device driver is a software stack which controls computer-graphics hardware and supports graphics-rendering application programming interfaces (APIs) and is released under a free and open-source software license. Graphics device drivers are written for specific hardware to work within a specific operating system kernel and to support a range of APIs used by applications to access the graphics hardware. They may also control output to the display if the display driver is part of the graphics hardware. Most free and open-source graphics device drivers are developed by the Mesa project. The driver is made up of a compiler, a rendering API, and software which manages access to the graphics hardware.

DirectX Video Acceleration (DXVA) is a Microsoft API specification for the Microsoft Windows and Xbox 360 platforms that allows video decoding to be hardware-accelerated. The pipeline allows certain CPU-intensive operations such as iDCT, motion compensation and deinterlacing to be offloaded to the GPU. DXVA 2.0 allows more operations, including video capturing and processing operations, to be hardware-accelerated as well.

X-Video Motion Compensation (XvMC), is an extension of the X video extension (Xv) for the X Window System. The XvMC API allows video programs to offload portions of the video decoding process to the GPU video-hardware. In theory this process should also reduce bus bandwidth requirements. Currently, the supported portions to be offloaded by XvMC onto the GPU are motion compensation and inverse discrete cosine transform (iDCT) for MPEG-2 video. XvMC also supports offloading decoding of mo comp, iDCT, and VLD for not only MPEG-2 but also MPEG-4 ASP video on VIA Unichrome hardware.

CoreAVC was a proprietary codec for decoding the H.264/MPEG-4 AVC video format.

Unified Video Decoder is the name given to AMD's dedicated video decoding ASIC. There are multiple versions implementing a multitude of video codecs, such as H.264 and VC-1.

PureVideo is Nvidia's hardware SIP core that performs video decoding. PureVideo is integrated into some of the Nvidia GPUs, and it supports hardware decoding of multiple video codec standards: MPEG-2, VC-1, H.264, HEVC, and AV1. PureVideo occupies a considerable amount of a GPU's die area and should not be confused with Nvidia NVENC. In addition to video decoding on chip, PureVideo offers features such as edge enhancement, noise reduction, deinterlacing, dynamic contrast enhancement and color enhancement.

Video Acceleration API (VA-API) is an open source application programming interface that allows applications such as VLC media player or GStreamer to use hardware video acceleration capabilities, usually provided by the graphics processing unit (GPU). It is implemented by the free and open-source library libva, combined with a hardware-specific driver, usually provided together with the GPU driver.

X-Video Bitstream Acceleration (XvBA), designed by AMD Graphics for its Radeon GPU and APU, is an arbitrary extension of the X video extension (Xv) for the X Window System on Linux operating-systems. XvBA API allows video programs to offload portions of the video decoding process to the GPU video-hardware. Currently, the portions designed to be offloaded by XvBA onto the GPU are currently motion compensation (MC) and inverse discrete cosine transform (IDCT), and variable-length decoding (VLD) for MPEG-2, MPEG-4 ASP, MPEG-4 AVC (H.264), WMV3, and VC-1 encoded video.

<span class="mw-page-title-main">Intel Graphics Technology</span> Series of integrated graphics processors by Intel

Intel Graphics Technology (GT) is the collective name for a series of integrated graphics processors (IGPs) produced by Intel that are manufactured on the same package or die as the central processing unit (CPU). It was first introduced in 2010 as Intel HD Graphics and renamed in 2017 as Intel UHD Graphics.

Intel Quick Sync Video is Intel's brand for its dedicated video encoding and decoding hardware core. Quick Sync was introduced with the Sandy Bridge CPU microarchitecture on 9 January 2011 and has been found on the die of Intel CPUs ever since.

<span class="mw-page-title-main">Distributed Codec Engine</span>

Distributed Codec Engine (DCE) is an API and its implementation as software library ("libdce") by Texas Instruments. The library was released under the Revised BSD License and some additional terms.

Video Code Engine is AMD's video encoding application-specific integrated circuit implementing the video codec H.264/MPEG-4 AVC. Since 2012 it was integrated into all of their GPUs and APUs except Oland.

High Efficiency Video Coding implementations and products covers the implementations and products of High Efficiency Video Coding (HEVC).

<span class="mw-page-title-main">Broadcom Crystal HD</span>

Crystal HD is Broadcom's hardware semiconductor intellectual property (SIP) core that performs video decoding.

Nvidia NVENC is a feature in Nvidia graphics cards that performs video encoding, offloading this compute-intensive task from the CPU to a dedicated part of the GPU. It was introduced with the Kepler-based GeForce 600 series in March 2012.

Nvidia NVDEC is a feature in its graphics cards that performs video decoding, offloading this compute-intensive task from the CPU. NVDEC is a successor of PureVideo and is available in Kepler and later NVIDIA GPUs.

Video Core Next is AMD's brand for its dedicated video encoding and decoding hardware core. It is a family of hardware accelerator designs for encoding and decoding video, and is built into AMD's GPUs and APUs since AMD Raven Ridge, released January 2018.

References

  1. 1 2 "Announcing libvdpau 0.2". freedesktop.org . 2009-09-17.
  2. ↑ "[VDPAU][ANNOUNCE] libvdpau 1.5". Freedesktop.org. 7 March 2022. Retrieved 8 March 2022.
  3. ↑ "GStreamer Adds NVDEC NVIDIA GPU Decoding Support - Phoronix".
  4. 1 2 Michael Larabel (2008-11-14). "NVIDIA Driver Brings PureVideo Features To Linux". Phoronix . Retrieved 2009-03-13.
  5. ↑ Michael Larabel (2008-11-14). "NVIDIA VDPAU Benchmarks". Phoronix . Retrieved 2009-03-13.
  6. ↑ "VDPAU: Video Decode and Presentation API for Unix". Nvidia.
  7. ↑ "Video4Linux2: Path to a Standardized Video Codec API" (PDF). Events.linusfoundation.org\accessdate=2016-05-25. Archived from the original (PDF) on 2014-01-06. Retrieved 2013-12-04.
  8. 1 2 "NVIDIA Releases Standalone VDPAU Library – Phoronix". Phoronix.
  9. ↑ Larabel, Michael (9 March 2015). "NVIDIA Announces VDPAU 1.0 With HEVC/H.265 Decoding". Phoronix. Retrieved 9 March 2015.
  10. ↑ "PureVideo Support Table" (PDF). Nvidia. Retrieved 2014-05-22.
  11. ↑ "Archived copy". Archived from the original on 2012-07-08. Retrieved 2010-02-28.{{cite web}}: CS1 maint: archived copy as title (link)
  12. ↑ "[PATCH] drm/radeon: UVD support for RV710-SI". Lists.freedesktop.org. 2 April 2013. Retrieved 2016-05-25.
  13. ↑ "AMD Releases Open-Source UVD Video Support – Phoronix". Phoronix. Retrieved 2016-05-25.
  14. ↑ "VDPAU: X11 Window System Integration Layer". Download.nvidia.com.
  15. ↑ "Intel Considering VDPAU Support For X.Org Driver – Phoronix". Phoronix. Retrieved 2016-05-25.
  16. ↑ "GitHub – linux-sunxi/libvdpau-sunxi: Experimental VDPAU for Allwinner sunxi SoCs (WiP)". GitHub. Retrieved 2016-05-25.
  17. ↑ "GitHub – i-rinat/libvdpau-va-gl: VDPAU driver with OpenGL/VAAPI backend". GitHub. Retrieved 2016-05-25.
  18. ↑ "Adobe Flash Player Hardware Acceleration on Intel Graphics Cards". WebUpd8. 5 September 2013. Retrieved 2016-05-25.
  19. ↑ "Boxee blog » boxee for windows, moving up to the Major Leagues". Archived from the original on June 26, 2009. Retrieved June 26, 2009.
  20. ↑ "Fluendo's New Codecs Support VDPAU, VA-API – Phoronix". Phoronix.com. Retrieved 2016-05-25.
  21. ↑ Michael Larabel (2008-11-29). "MythTV Adds Support For NVIDIA VDPAU". Phoronix . Retrieved 2009-03-13.
  22. ↑ "XBMC for Linux VDPAU – NVIDIA GPU video decoding support (now in the mainline SVN)". Xbmc.org. Archived from the original on 2009-02-28. Retrieved 2016-05-25.
  23. ↑ "Kodi – Open Source Home Theater Software". Xbmc.org. Archived from the original on 2009-04-14. Retrieved 2016-05-25.
  24. ↑ "XBMC Receives Mainline Support For VDPAU – Phoronix". Phoronix.
  25. ↑ "XBMC Receives Mainline Support For VDPAU". Phoronix.com. 2009-03-23. Retrieved 2016-05-25.
  26. ↑ Michael Larabel (2008-12-17). "Xine Picks Up Support For NVIDIA's VDPAU". Phoronix . Retrieved 2009-03-13.
  27. ↑ "xine-lib/xine-lib-1.2: changeset 11335:9b68f6efb713". Debian.org. Archived from the original on July 8, 2012. Retrieved 2016-05-25.
  28. ↑ ddennedy (2009-11-30). "VDPAU for MLT 0.4.11 Git version". MLT. Archived from the original on 2010-02-27. Retrieved 2009-11-30.
  29. ↑ "Flash Player 10.2 beta – with VDPAU acceleration! : linux". reddit. December 2010.
  30. ↑ "mpv Reference Manual" . Retrieved 2016-04-09.
  31. ↑ Michael Larabel (2009-02-03). "A NVIDIA VDPAU Back-End For Intel's VA-API". Phoronix . Retrieved 2009-03-13.
  32. ↑ "Appendix G. VDPAU Support". Nvidia. 2016-12-14. Retrieved 2017-01-03.
  33. ↑ "VDPAU For NVIDIA's Maxwell GPU On Linux". Phoronix.com. 2014-03-03. Retrieved 2016-05-25.
  34. 1 2 3 4 5 "Appendix G. VDPAU Support". us.download.nvidia.com. Retrieved 2022-06-02.
  35. ↑ http://www.nvidia.com/download/driverResults.aspx/104284/en-us Nvidia LINUX X64 (AMD64/EM64T) DISPLAY DRIVER Version:367.27
  36. ↑ "[ANNOUNCE] libvdpau 0.2". Lists.freedesktop/org. 17 September 2009. Retrieved 2016-05-25.
  37. ↑ "NVIDIA Proposes VDPAU For DRI2 Patches – Phoronix". Phoronix. Retrieved 2016-05-25.
  38. ↑ "[PULL] Add VDPAU drivers to the server's DRI2 implementation". xorg. 23 October 2009. Retrieved 2016-05-25.
  39. ↑ "VideoToolbox - Apple Developer Documentation". developer.apple.com. Retrieved 2018-08-05.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.