DirectX Video Acceleration

From MultimediaWiki
(Redirected from DXVA)
Jump to navigation Jump to search

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

DXVA works in conjunction with the video rendering model used by the video card. DXVA 1.0, which is available for Windows 2000 or later, can use either the overlay rendering mode or VMR 7/9.<ref name="dxva2">Template:Citation/core{{#if:|}}</ref> DXVA 2.0, available only on Windows Vista and later OSs, integrates with Media Foundation (MF) and uses the Enhanced Video Renderer (EVR) present in MF.<ref name="dxva2"/>

Architecture overview

The DXVA is used by software video decoders to define a codec-specific pipeline for hardware-accelerated decoding and rendering of the codec. The pipeline starts at the CPU which is used for parsing the media stream and conversion to DXVA-compatible structures. DXVA specifies a set of operations that can be hardware accelerated and device driver interfaces (DDIs) that the graphic driver can implement to accelerate the operations. If the codec needs any of the supported operations, it can use these interfaces to access the hardware-accelerated implementation of these operations. If the graphic driver does not implement one or more of the interfaces, it is up to the codec to provide a software fallback for it. The decoded video is handed over to the hardware video renderer where further post-processing might be applied to it before being being rendered to the device. The resulting pipeline is usable in a DirectShow compatible application.

DXVA specifies the Motion Compensation DDI, which specifies the interfaces for iDCT operations, Huffman coding, color correction, motion compensation, alpha blending, inverse quantization, colorspace conversion and frame-rate conversion operations, among others.<ref name="intro">Template:Citation/core{{#if:|}}</ref><ref>Template:Citation/core{{#if:|}}</ref> It also includes three sub-specifications: Deinterlacing DDI, COPP DDI and ProcAmp DDI.<ref>Template:Citation/core{{#if:|}}</ref> The Deinterlacing DDI specifies the callbacks for deinterlacing operations. The COPP (Certified Output Protection Protocol) DDI functions allow the pipeline to be secured for DRM-protected media, by specifying encryption functions. The ProcAmp DDI is used to accelerate post-processing video. The ProcAmp driver module sits between the hardware video renderer and the display driver and provides functions for applying post-processing filters on the decompressed video.

The functions exposed by DXVA DDIs are not accessible directly by a DirectShow client, but are supplied as callback functions to the video renderer. As such, the renderer plays a very important role in anchoring the pipeline.

DXVA 2.0 in enhances the implementation of the video pipeline and adds a host of other DDIs, including a Capture DDI for video capture. The DDIs it shares with DXVA 1.0 are also enhanced with support for hardware acceleration of more operations. Also, the DDI functions are directly available to callers and need not be mediated by the video renderer.<ref name="new">Template:Citation/core{{#if:|}}</ref> As such, pipelines for simply decoding the media (without rendering) or post-processing and rendering (without decoding) can also be created. These features require the need of WDDM drivers, which limit DXVA to Windows Vista and Windows Server 2008 only.<ref name="new"/><ref name="dxva2"/> DXVA supports only Enhanced Video Renderer as the video renderer.<ref name="dxva2"/> DXVA integrates with Media Foundation and allows DXVA pipelines to be exposed as Media Foundation Transforms (MFTs). Even decoder pipelines or post-processing pipelines can be exposed as MFTs, which can be used by the Media Foundation topology loader to create a full media playback pipeline. DXVA 1.0 is emulated using DXVA 2.0.<ref name="dxva2"/> DXVA 2.0 does not include the COPP DDI, rather it uses PVP for protected content.

See also

References

External links


Template:Microsoft APIs Template:Windows Components