AMD Unified Video Decoder (UVD, legacy)

UVD names AMD’s legacy dedicated video-decoder family, while related identifiers can persist in software interfaces that run on later supported devices.

Unified Video Decoder, or UVD, is AMD's legacy dedicated video-decoder family. Its role is reconstruction of supported compressed video into pictures.

AMD's 2017 multimedia presentation identifies UVD as the decoder and VCE as the encoder. Later hardware uses VCN-family media blocks, while older UVD terminology remains useful in documentation and software identifiers.

Recognize the hardware role

Name in the older architecture Role to associate with it
UVD Supported video reconstruction
VCE Supported video compression
Graphics/compute resources Programmable processing and graphics work

This is a role distinction. The accepted codecs, profiles and formats depend on the actual UVD generation and exposed driver path.

A UVD decoder's output can be used for playback or another encoding stage. Decode support alone does not establish the target encoder.

Component identifiers can preserve old names

AMD's current AMF decoder documentation still uses names such as AMFVideoDecoderUVD_H264_AVC. That is a component identifier supplied to the framework.

Its spelling is not a report that the device contains a particular old UVD block. The application creates a supported component through its runtime and device context.

The current documentation also uses HW-prefixed identifiers for other decoder configurations. Both styles belong to the public software interface rather than a universal naming rule for physical media hardware.

Interpret an older acceleration description by stage

An older Emby-related discussion might mention UVD decoding and an AMD encoder in the same conversion. The first name concerns the input reconstruction stage; the second concerns newly created output.

The selected device and source configuration establish what could actually be decoded. The intervening picture operations and encoder establish the rest of the route.

VCN and AMF provide the hardware-family and software-interface context for reading those names in newer stacks.

See Also

References