Fact-checked by Grok 2 weeks ago

Unified Video Decoder

The Unified Video Decoder (UVD) is a dedicated hardware video decoding application-specific integrated circuit (ASIC) developed by Advanced Micro Devices (AMD) and integrated into its Radeon graphics processing units (GPUs) and accelerated processing units (APUs). It provides bit-accurate, hardware-accelerated decoding of compressed video streams, offloading the computational load from the CPU to enable efficient playback of high-definition content while reducing power consumption and system heat. Introduced in 2007 with the GPUs, UVD marked AMD's entry into dedicated video , initially supporting codecs such as H.264/AVC and for smooth playback from sources like Blu-ray and . Over successive generations, UVD evolved to broaden codec support and performance capabilities; for instance, the UVD+ variant in the 2008 HD 3000 series added HDCP compatibility for protected high-resolution streams, while UVD2 in the HD 4000 and 5000 series enhanced dual-stream decoding for multitasking. Further advancements included UVD3 in the 2010 Radeon HD 6000 series, which incorporated decoding for , MPEG-4 ASP (such as and ), and MVC for stereoscopic 3D Blu-ray content, alongside post-processing features like de-interlacing and to improve video quality. Later iterations included UVD 4.2 in the 2013 Hawaii-based R9 290/390 series, UVD 5 in the 2014 Tonga-based R9 285 with full hardware support for H.264 decoding at up to 60 frames per second (level 5.2), and UVD 6 in the 2016 Polaris-based RX 400/500 series adding support for emerging formats including HEVC/H.265 Main profile decoding up to . The technology was succeeded in 2018 by AMD's (VCN) engine starting with the Raven Ridge , which unified decoding and encoding functions for broader multimedia acceleration.

Introduction

Definition and Purpose

The Unified Video Decoder (UVD) is AMD's dedicated hardware video decoding (ASIC), integrated into GPUs and accelerated processing units () since its introduction with the in 2007. This technology is based on Xtensa configurable processor cores, originally licensed by in 2004 for applications. The primary purpose of UVD is to enable hardware-accelerated decoding of compressed video streams, such as those used in HD-DVD and Blu-ray formats, thereby offloading the computational burden from the CPU to the GPU. By handling decoding entirely in hardware, UVD significantly reduces CPU utilization—for instance, from around 85% to 16% during H.264 playback—while lowering overall power consumption compared to software-based methods. This efficiency is particularly advantageous for mobile devices and home theater systems, promoting quieter operation and extended battery life. Key benefits of UVD include its ability to support simultaneous decoding of multiple video codecs, facilitating seamless playback of high-resolution content like and videos in later implementations, and freeing GPU shader resources for parallel graphics rendering or compute tasks. Through successive versions, UVD has evolved to enhance codec compatibility and performance, building on its foundational role in efficient .

Historical Development

The origins of the Unified Video Decoder (UVD) trace back to ' Xilleon video processor, a dedicated ASIC for video decoding that was integrated into prior to 's acquisition of ATI in July 2006. Following the acquisition, AMD incorporated elements of the Xilleon technology into its graphics processing units, marking an early step toward on-die video acceleration. This laid the groundwork for UVD's debut in the GPUs, released in May 2007, which introduced dedicated decoding for H.264 and codecs to offload CPU-intensive tasks. UVD's development accelerated in response to surging demand for high-definition video playback, particularly for Blu-ray and HD-DVD formats requiring efficient handling of advanced codecs like H.264 and VC-1. positioned UVD as a competitive alternative to Nvidia's technology, which had established hardware decoding leadership, while anticipating emerging rivals like Intel's Quick Sync Video introduced in 2011. Key milestones included the UVD+ enhancement in the Radeon HD 3000 series in 2008, which improved power efficiency and added support for additional profiles; major architectural updates in the in 2012 under the (GCN) framework; and the final iteration, UVD 7.2, integrated into the Vega 20 GPU in 2018. By the mid-2010s, UVD had achieved widespread adoption across AMD's consumer GPUs and , enabling seamless and video playback in millions of systems and solidifying AMD's role in multimedia acceleration. However, starting with the Raven Ridge in January 2018, AMD began phasing out UVD in favor of the (VCN) architecture, which unified video decoding and encoding capabilities into a single, more efficient block to better support modern workflows like streaming and .

Architecture and Versions

Core Design Principles

The Unified Video Decoder (UVD) is implemented as an (ASIC) integrated into graphics processing units, leveraging multiple Xtensa LX2 configurable processor cores to handle core video decoding operations. These cores are optimized for tasks including decoding via Context-Adaptive Binary Arithmetic Coding (CABAC) or Context-Adaptive Variable-Length Coding (CAVLC), for inter-frame prediction, and inverse discrete cosine transforms (IDCT) for reconstruction. The decoding pipeline in UVD emphasizes hardware acceleration for computationally intensive stages, such as bitstream parsing to extract syntax elements, in-loop deblocking filters to reduce artifacts, and IDCT operations, all performed entirely in dedicated hardware to minimize latency and CPU involvement. Post-processing functions, including scaling, deinterlacing, noise reduction, and edge enhancement, are offloaded to the GPU's programmable shaders for flexibility and quality enhancements tailored to display requirements. UVD's design prioritizes power efficiency by confining decoding to a low-overhead block, significantly reducing overall system power draw compared to software-based that heavily tax the CPU; for instance, H.264 1080p playback drops CPU utilization from around 85% to 16% with UVD enabled, enabling quieter operation and longer life in mobile devices. This efficiency stems from the ASIC's streamlined , which avoids the overhead of general-purpose . Scalability is a key principle, with UVD supporting multi-instance decoding—up to two simultaneous streams in versions starting from UVD 2—for scenarios like playback, alongside seamless integration with the (DXVA) API to leverage ecosystems for accelerated rendering. Security is addressed through built-in support for (HDCP) versions 1.x and 2.x, ensuring secure transmission of protected content over interfaces. Later versions introduce enhancements like improved MVC handling for stereoscopic video, but the foundational principles remain centered on hardware-software partitioning for broad codec compatibility and efficiency.

UVD 1.0 to UVD 3.0

The initial generations of AMD's Unified Video Decoder (UVD) marked the transition from software-dependent video decoding to dedicated hardware acceleration, focusing on high-definition content up to 1080p resolution. Introduced in 2007 with the Radeon HD 2000 series, UVD 1.0 provided basic hardware decoding for H.264 and VC-1 codecs, supporting up to 1080p at 8-bit color depth, while relying on shader-assisted post-processing for deinterlacing and scaling. This version was absent from high-end models like the Radeon HD 2900 XT due to die space constraints on the R600 GPU. In 2008, UVD+ debuted with the HD 3000 series, enhancing the original design by adding HDCP 1.3 support for protected high-definition streams and improving decoding through shader assistance, though still capped at (2048x1536). These updates addressed content protection needs for Blu-ray and playback while maintaining low power overhead on 55nm process nodes. The UVD evolved significantly with versions 2.0 and 2.1 in the 2008-2009 , introducing full hardware decoding for alongside H.264 and , enabling dual-stream playback for functionality and compliance with BD-Live for interactive Blu-ray features. UVD 2.1 offered minor refinements for mobility variants, all fabricated on 55nm processes to balance performance and efficiency for 1080p content at 60 with minimal GPU utilization. A sub-variant, UVD 2.2, appeared in 2009 on lower-end HD 4000 chips like the RV710 (HD 4350) and RV730 (HD 4670), featuring a redesigned local memory interface to boost compatibility with and formats via improved MPEG-4 handling, alongside reduced artifacts in decoding. This iteration prioritized artifact reduction and broader format support without expanding resolution limits. UVD 3.0 arrived in 2010 with the , incorporating hardware entropy decoding for to offload more computational burden from the CPU, alongside (MVC) support for Blu-ray playback and 120Hz stereo output. It marked the first integration into accelerated processing units (), debuting in the Llano platform's Sumo graphics core for hybrid CPU-GPU systems. Built on a 40nm process, UVD 3.0 enabled efficient 1080p60 decoding with under 10% GPU utilization, emphasizing scalability for emerging content.

UVD 4.0 to UVD 7.2

The period from UVD 4.0 to UVD 7.2 marked significant advancements in AMD's Unified Video Decoder, transitioning from high-definition enhancements to full support for ultra-high-definition (UHD) content, including resolutions, (HDR), and improved efficiency for modern codecs like HEVC. These versions were integrated into AMD's (GCN) architectures, enabling hardware-accelerated decoding that offloaded computational burdens from the CPU, particularly beneficial for consumer and professional video playback in GPUs and APUs. Building on the foundations of earlier UVD iterations, this era emphasized scalability for emerging ecosystems and power-efficient processing on shrinking process nodes. UVD 4.0, introduced in 2012 with the based on the first-generation GCN architecture, featured improvements in for smoother video playback, with continued support for (MVC) from prior versions to enable stereo 3D decoding. It was implemented in GPUs such as (Radeon HD 7700 series) and Pitcairn (Radeon HD 7800/7900 series), fabricated on a 28 nm process node. These enhancements allowed for more robust handling of H.264 content in immersive formats, representing a step up in capabilities for mid-range discrete graphics. In 2014, UVD 4.2 debuted alongside the Radeon R9 200 series and APUs, introducing enhanced error resilience to better manage corrupted video streams and marking the first widespread integration of UVD into low-power APUs like Kabini. This version maintained with prior codecs while improving reliability for integrated graphics in laptops and systems, facilitating broader adoption in . The design prioritized seamless playback in error-prone network environments, such as streaming applications. UVD 5.0 arrived later in 2014 with the R9 285 based on the GPU, providing full hardware support for H.264 decoding up to Level 5.2 at 60 frames per second () in depth. This capability addressed the growing demand for UHD content, enabling high-frame-rate playback on displays without taxing the host CPU. The revamped decoder offered up to 47% better performance compared to previous generations, underscoring AMD's focus on efficiency for workflows. From 2015 to 2016, UVD 6.0 powered the Radeon R9 Fury series ( GPU) and certain like Carrizo, adding native decoding for HEVC (H.265) Main10 profile to support video with 10-bit . Integrated into like Carrizo and discrete GPUs such as , it enabled vibrant playback for emerging streaming services and media players. This version significantly reduced power consumption for 10-bit processing, making it suitable for high-end consumer setups. UVD 6.3, specific to the 2016 Radeon RX 400 series (Polaris GPUs), extended capabilities with shader-assisted decoding for Profile 2, allowing efficient handling of up to @60 Hz VP9 content commonly used in web video platforms. It also ensured compatibility with metadata passthrough when paired with HEVC streams, enhancing color accuracy and in supported displays. This hybrid approach bridged hardware limitations for newer codecs while maintaining . UVD 7.0, launched in 2017 with Vega 10 and Vega 12 GPUs, optimized HEVC 10-bit decoding for lower power usage during @60 fps playback, though it lacked native hardware support for , relying instead on hybrid CPU-GPU assistance. Deployed in high-performance discrete cards and , it emphasized on the 14 nm process, achieving sustained UHD performance with minimal thermal overhead. These refinements catered to power-sensitive applications like gaming consoles and professional workstations. Finally, UVD 7.2 appeared in 2018 with the Vega 20 GPU in the Radeon Instinct MI50 accelerator, incorporating dual UVD instances to enable simultaneous multi-4K decoding streams, targeted at and use cases. Fabricated on a 7 nm node, this version supported for high-throughput video workloads, such as virtual desktop infrastructure. The enterprise orientation highlighted UVD's evolution toward scalable, professional-grade video handling. Overall, these UVD iterations shifted from 28 nm to 14 nm and 7 nm processes, progressively enhancing decode efficiency for @60 fps 10-bit content through dedicated offload, reducing CPU utilization to under 5% in optimized scenarios.

Integration with Video Coding Engine

The (VCE) was introduced by in 2011 alongside the graphics processors, serving as a dedicated encoder to complement the UVD's decoding capabilities. VCE provided fixed-function encoding primarily for H.264/AVC, enabling efficient video compression without relying on the general-purpose GPU compute units. In combined decode-encode workflows, UVD handled the decoding of incoming video streams, passing reconstructed frames directly to VCE via shared system memory buffers for subsequent encoding, which minimized data transfer overhead and latency in pipelines. This integration allowed for seamless processing where decoded pixel data from UVD could be fed into VCE's and transform units without CPU intervention, optimizing for applications. Key use cases included real-time in streaming software such as , where UVD decoded source content and VCE re-encoded it for live broadcasts, and in professional tools like , which leveraged the pair for accelerated H.264 and HEVC workflows starting from version 14.2. These setups supported encoding up to in H.264 and HEVC formats, facilitating high-quality output for broadcast and . Despite their synergy, UVD and VCE operated as distinct on the GPU die, leading to increased area compared to later unified designs and requiring separate driver interfaces for control. There was no single unified for managing both until the introduction of (VCN) in 2018. In architectures like (UVD 6.0 with VCE 2.0) and (UVD 7.0 with VCE 3.0), the combination enabled HEVC decode and encode at frame rates of 30-60 , suitable for consumer tasks. As of 2025, legacy UVD and VCE functionality remains supported in Software Adrenalin Edition 25.x drivers and open-source Mesa 25.0 for older hardware, ensuring compatibility for maintenance and niche applications.

Technical Features

Decoding Pipeline

The decoding pipeline of the Unified Video Decoder (UVD) processes compressed video s through a series of hardware-accelerated stages to reconstruct frames efficiently. The initial stage focuses on entropy decoding, where incoming data is parsed to extract syntax elements and coefficients. This is performed using configurable Xtensa processor cores licensed from , which handle variable-length coding (), context-adaptive variable-length coding (CAVLC), and context-adaptive binary arithmetic coding (CABAC) for s like H.264 and VC-1. These cores enable flexible adaptation to different requirements while maintaining high throughput for real-time decoding. Following decoding, the proceeds to quantization and transform operations, reconstructing the coefficients from the quantized data. Dedicated fixed-function hardware units perform (IDCT) or discrete sine transform (iDCT), depending on the , to convert frequency-domain coefficients back to spatial-domain pixel s. This stage ensures bit-accurate compliance with standards such as H.264 and , offloading computationally intensive operations from the CPU to specialized ASIC blocks within the UVD. The core reconstruction occurs in the and intra-prediction stage, where reference frames are accessed from on-chip buffers to generate predicted blocks. Inter-frame uses vector data to interpolate pixels from previously decoded frames, while intra-prediction synthesizes blocks from neighboring pixels within the current frame. These operations leverage high-bandwidth internal memory and fixed-function accelerators to assemble complete macroblocks, supporting resolutions up to in later UVD iterations. Codec-specific adaptations, such as multi-hypothesis prediction in , are handled here without delving into detailed profile variations. Artifact reduction follows in the filtering stage, applying a to mitigate blocking effects at boundaries, followed by sample adaptive offset (SAO) in HEVC-supporting versions to correct pixel-level distortions and improve visual quality. The adaptively adjusts based on boundary strength and quantization parameters, while SAO applies category-based offsets to residual samples post-reconstruction. These in-loop filters enhance compression efficiency and output fidelity directly within the hardware pipeline. The pipeline culminates in outputting uncompressed YUV frames to the GPU's , where programmable shaders handle subsequent tasks like , conversion to RGB, and preparation. This integration allows seamless handoff to the for rendering. The full UVD process achieves significant efficiency gains over software decoding by employing fixed-function units optimized for parallel processing, reducing CPU utilization by up to 70% and enabling low-power HD playback. Additionally, built-in error concealment mechanisms detect and mitigate corrupted segments by substituting affected areas with data from adjacent or frames, ensuring robust playback of error-prone streams.

Post-Processing and Scalability

The Unified Video Decoder (UVD) employs GPU shader-based post-processing to enhance decoded video quality prior to display. is handled through advanced algorithms that incorporate temporal analysis to convert interlaced content into frames, outperforming simpler techniques like or basic bobbing by reducing artifacts and preserving motion fidelity. Noise reduction utilizes Temporal Noise Reduction (TNR), which targets artifacts from capture, transmission, or processes while balancing detail retention and avoiding ghosting effects. sharpens video boundaries to boost perceived clarity without introducing excessive ringing. These operations are executed efficiently on the GPU to minimize CPU involvement and support smooth playback. Scalability in the UVD enables handling of multiple concurrent video streams, a feature introduced with dual-stream decoding in UVD 2.0 for applications like playback. Subsequent iterations, including UVD 3.0 and later, maintain this capability while optimizing for higher workloads, such as decoding one high-definition stream alongside a secondary stream. conversion, such as adapting content to 60 , is performed via programmable GPU shaders to ensure fluid output across displays. Bandwidth management is facilitated by , which allocates resources dynamically to prevent bottlenecks during multi-stream operations. Support for H.264 decoding at up to 60 (level 5.2) was introduced in UVD 5, with later versions like UVD 6.3 and 7.0 enabling configurations such as two simultaneous streams under controlled bandwidth conditions. HDR support emerges in UVD 6.0 and subsequent versions, enabling passthrough for and formats with wide color gamut (WCG) preservation. is achieved through GPU that adapt content for compatible displays, converting peak brightness levels while maintaining color accuracy and contrast. This integration allows legacy UVD hardware to handle workflows without full hardware decoding of advanced , relying on shader flexibility for compatibility. For multi-monitor setups, UVD firmware coordinates stream distribution to support up to four outputs or dual displays simultaneously in later versions like UVD 7.0, optimizing memory and bandwidth to sustain performance across extended desktops. However, the UVD lacks native AI-driven upscaling, distinguishing it from the successor (VCN), which incorporates more advanced processing units for such features; complex effects thus depend on the host GPU's general-purpose shaders. As of 2025, enhancements in legacy drivers, including Mesa 25, add advanced encoding features such as B-frame support and rate control options to UVD/VCE, improving usability for older hardware.

Codec and Format Support

Evolution of Supported Codecs

The Unified Video Decoder (UVD) initially launched with version 1.0 in the graphics processors in 2007, providing hardware-accelerated decoding for H.264 High Profile up to level 4.0 and Advanced Profile, enabling efficient playback of high-definition content without relying on CPU resources for core decoding tasks. With UVD 2.0 introduced in the in 2008, support expanded to include iDCT acceleration for Simple and Main Profiles, alongside full bitstream decoding for H.264 and , which marked a significant step toward broader compatibility with legacy broadcast formats. Subsequent iterations in UVD 3.0 and 4.0, debuting with the in 2010 and HD 7000 series in 2011 respectively, further broadened codec coverage by adding full bitstream decoding for , MPEG-4 Advanced Simple Profile (ASP) support for and formats, as well as (MVC) for stereoscopic 3D Blu-ray playback. These versions also enhanced level support across H.264, , and up to level 4.1, facilitating smoother handling of content at resolutions suitable for early HD streaming. Advancements in UVD 5.0 and 6.0, rolled out with GCN-based architectures like the R9 285 in and R9 Fury series in 2015, introduced (HEVC/H.265) Main and Main10 Profiles in UVD 6.0, supporting 10-bit for HDR applications and enabling 4K decoding at up to 60 fps. Additionally, UVD 6.3 added shader-assisted decoding for VP9 Profiles 0 and 2, primarily through acceleration on the GPU shaders, which became essential for web-based 4K video delivery platforms like . Throughout its evolution, UVD maintained support for entropy decoding methods such as CABAC and CAVLC in both H.264 and HEVC, ensuring compatibility with a range of complexities, though it notably lacked support for interlaced HEVC content. Early implementations prior to UVD 2.0 relied on partial shader-based processing for , which was improved with iDCT acceleration in UVD 2.0 and full decoding in UVD 3.0 to improve efficiency. decoding, a more recent , was never integrated into UVD and instead required the successor (VCN) architecture. As of 2025, UVD 7.0 in Vega-based processors continues to support legacy codecs like for in drivers such as Adrenalin, but emphasis has shifted toward HEVC and for efficient and beyond streaming, with ongoing software optimizations in open-source stacks like Mesa to sustain performance on older hardware. This progression reflects UVD's role in adapting to evolving video standards while prioritizing power efficiency and broad format .

Resolution, Bit Depth, and Profile Limitations

The Unified Video Decoder (UVD) in its initial iterations, from versions 1.0 to 3.0, was constrained to resolutions up to 2048x1536 (approximately 2K), supporting 8-bit color depth exclusively for codecs like H.264 up to level 4.1, with no capability for 10-bit decoding. These early versions focused on efficient handling of high-definition content at the time, such as 1080p streams, but lacked support for higher resolutions or deeper color pipelines, limiting their use for emerging ultra-high-definition formats. With the advent of UVD 5.0 and subsequent versions, introduced support for at 4096x2160 and up to 60 frames per second for H.264 decoding, aligned with level 5.2 specifications, marking a significant expansion for mainstream consumer hardware. This upgrade enabled smoother playback of content without excessive CPU load, though initial implementations in UVD 5 were still limited to 8-bit processing. By UVD 6.0, (HEVC) support extended to the Main10 profile, incorporating 10-bit for enhanced in compatible streams. UVD 7.0 and later variants, integrated into architectures like , further refined these capabilities to handle at 60 fps with 10-bit decoding for both HEVC and codecs, while maintaining a maximum bitrate around 500 Mbps for content to ensure stable performance within hardware constraints. Notably, UVD across all versions does not support 8K resolutions, capping practical applications at for high-end decoding scenarios. These advancements prioritized legacy and workflows over next-generation ultra-high-definition demands. Profile limitations in UVD implementations restrict full hardware acceleration to specific subsets: for H.264, support extends up to the High 4:4:4 Predictive profile, though with partial limitations on advanced chroma subsampling; for VC-1, decoding is capped at Advanced Profile Level 3 (AP@L3). Broader YUV 4:2:2 or 4:4:4 formats receive no comprehensive support, often requiring software fallback for non-standard streams, which underscores UVD's design focus on mainstream broadcast and Blu-ray compatible profiles rather than professional-grade color spaces. Bit depth handling evolved progressively, with versions 1.0 through 5.0 confined to 8-bit processing for all supported codecs, ensuring compatibility with standard content but excluding workflows. Starting with UVD 6.0, 10-bit decoding became available for -enabled HEVC streams, while 12-bit remains limited to passthrough modes without full . As of 2025, UVD's specifications render it outdated for 8K or decoding requirements in modern streaming and production pipelines, though it remains adequate for legacy content playback in supported ecosystems.
UVD VersionMax ResolutionBit Depth SupportKey Profile/Level Limits
1.0–3.02048x1536 (2K)8-bit onlyH.264 up to level 4.1; up to AP@L3
5.0+4096x2160 @ 60 fps (H.264)8-bit (initial); 10-bit from 6.0 (HEVC Main10)H.264 up to level 5.2; limited High Predictive
7.0–7.24096x2160 @ 60 fps (HEVC/VP9, 10-bit )10-bit for ; 12-bit passthroughNo 8K; ~500 Mbps bitrate cap for 4K; no full YUV 4:2:2/

Hardware Availability

Discrete Graphics Processors

The Unified Video Decoder (UVD) was first integrated into AMD's discrete GPUs with the HD 2000 series in 2007, marking the introduction of dedicated for video decoding on standalone graphics cards. Specifically, UVD 1.0 was incorporated into chips such as the RV630 ( HD 2600) and RV670 ( HD 3870), enabling support for H.264 and decoding while offloading tasks from the CPU. However, the high-end HD 2900 XT, based on the R600 chip variant, notably excluded the UVD block to prioritize raw graphics performance, as confirmed by early hardware analyses. This initial implementation occupied a dedicated portion of the GPU die, facilitating efficient playback of high-definition content without relying on software decoding. The HD 3000 series (2008) introduced UVD+, a variant of UVD 1.0 with added HDCP support for protected content. The subsequent (2008-2009) evolved the technology with UVD 2.0 and 2.1 in R700-based architectures like the RV710 ( HD 4550) and RV770 ( HD 4850). UVD 2 added full decoding, enhancing compatibility with Blu-ray and broadcast standards. By the (2009-2010), UVD 2.2 in Evergreen chips such as ( HD 5770) provided refined H.264/ handling and initial stereoscopic video support up to 1080p. The HD 6000 and 7000 series (2010-2012), utilizing Northern Islands and Southern Islands architectures, introduced UVD 3.0 and 3.1 in codenames like Cayman (Radeon HD 6970) and ( HD 7970), enabling full 1080p decoding including MVC profiles for Blu-ray 3D. These advancements were driven by the need for smoother multi-stream playback in applications.
GPU SeriesRelease YearsKey CodenamesUVD VersionNotable Features
Radeon HD 20002007RV630, RV6701.0H.264, VC-1 decoding
Radeon HD 30002008VariousUVD+HDCP addition
Radeon HD 40002008-2009RV710, RV7702.0-2.1MPEG-2 decoding, HDCP
Radeon HD 50002009-2010, 2.21080p stereoscopic
Radeon HD 6000/70002010-2012Cayman, Tahiti, Pitcairn3.0-3.1Full 1080p MVC support
In the R7 and R9 200/300 series (2013-2016), UVD progressed to versions 4.2 through 6.0 across GCN 1.0 to 1.2 architectures, including (Radeon R7 260X, UVD 4.2), (Radeon R9 390, UVD 4.2), (Radeon R9 380, UVD 5.0), and (Radeon R9 Fury, UVD 6.0). These integrations supported entry-level decoding for H.264 and introduced HEVC (H.265) main profile handling, allowing for higher efficiency in ultra-high-definition video streams. The UVD block in these GPUs formed a fixed-function unit within the die, typically clocked independently to balance power and performance during video workloads. For instance, the 10 chip in the RX 480 (2016), fabricated on a , included UVD 6.3 for robust playback. The final major UVD implementations in discrete GPUs appeared in the RX 400/500 series (2016-2017) and Vega series (2017-2018), with UVD 6.3 in 10/11/12 (e.g., RX 580) and UVD 7.0 in Vega 10 (e.g., RX Vega 64) or UVD 7.2 in Vega 20. These versions added HEVC decoding, including 10-bit color and main 10 profile support, enabling premium video experiences on consumer cards. Vega's UVD further optimized for multi-view and scalable extensions, though it represented the endpoint for UVD before the shift to (VCN) in subsequent architectures. As of 2025, UVD remains supported in legacy modes for pre-RDNA discrete GPUs via open-source drivers, ensuring compatibility for older hardware in , while VCN handles primary video tasks in RX 5000 series and beyond.

Integrated Graphics in APUs

The integration of the Unified Video Decoder (UVD) in AMD's Accelerated Processing Units () prioritized power efficiency for laptops and desktops, enabling hardware-accelerated video decoding on shared CPU-GPU dies to minimize drain and output. Early designs focused on offloading decode tasks from the CPU, allowing APUs to maintain low TDPs while supporting workloads in and embedded systems. This approach contrasted with discrete GPUs by emphasizing idle and to achieve sub-system-level consumption during playback. The inaugural APUs, Llano for desktops and Zacate for low-power devices released in 2011, featured UVD 3.0 integrated with and Desna cores on a 32nm process, delivering basic decode capabilities with to reduce active draw. These units marked AMD's initial push for efficient integrated video in consumer platforms, handling standard-definition and streams without significantly impacting overall APU power budgets. Subsequent mid-range offerings, including the 2013-2015 and Carrizo families based on and cores, upgraded to UVD 4.2 and 6.0 on a 28nm node. For instance, 's UVD 4.2 shared the die directly with the CPU, enabling decode operations in ultra-low-power modes suitable for 15W TDP configurations. Carrizo further refined this with enhanced , including UVD self-gating and low-power states, to support extended playback in battery-constrained laptops. Higher-end APUs from 2016, such as Bristol Ridge based on Excavator cores, incorporated UVD 6.0 for more demanding scenarios, including dual-stream support in 35W envelopes for multi-monitor productivity. These were optimized for FM2+ sockets in desktop variants, balancing performance and efficiency for home theater PCs (HTPCs). Low-end variants like Beema excluded full UVD implementations to further cut power in sub-10W designs. The transition to Zen-based APUs, starting with Raven Ridge in 2018, replaced UVD with Video Core Next (VCN) for advanced multimedia acceleration. By 2025, UVD persists as a legacy component in older pre-Zen Ryzen APUs, supplanted by VCN in modern Phoenix and Strix Point for continued power-optimized decoding.

Software Support

Windows Drivers

AMD's proprietary Windows drivers have historically provided support for the Unified Video Decoder (UVD) through integration with Microsoft's (DXVA) API, enabling hardware-accelerated video decoding on compatible graphics hardware. The driver suite, spanning from 2008 to 2015, introduced and expanded UVD capabilities, starting with UVD 2.0 in the for decoding formats like H.264, , and via DXVA. This support was further enhanced in subsequent releases, such as version 10.2, which included a fix for system freezing during UVD decoding in Windows environments. In 2016, transitioned from to (initially branded as Edition), which continued seamless UVD integration while introducing a modernized and improved performance tuning for video workloads. UVD's API integration in Windows drivers achieves full compliance with DXVA2 for versions UVD 2 and later, allowing applications to offload decoding tasks to hardware for efficient playback of high-definition content. For UVD 6 and subsequent iterations, introduced in the Radeon RX 400 and Vega series, drivers enable HEVC (H.265) decoding within Windows 10 and 11's Media Foundation framework, supporting up to 4K resolutions with minimal CPU overhead. This compliance ensures broad compatibility with media players and browsers, facilitating smooth hardware-accelerated streaming and playback. Recent driver updates, such as Software Adrenalin Edition 25.6.3 released in June 2025, maintain UVD functionality for legacy hardware including the RX 400 and series, with enhancements for stability in modern applications. These updates also incorporate automatic selection in software like , optimizing UVD usage based on content type and system capabilities. Additionally, embedded UVD firmware is included within the driver package. As of November 2025, the latest Software Adrenalin Edition 25.11.1 continues support for pre-VCN UVD hardware. Additionally, 2024 driver iterations, including version 24.7.1, address compatibility with 24H2, resolving potential playback interruptions. Early implementation challenges were resolved through updates by 2011, improving reliability for Blu-ray playback. Overall, these Windows drivers emphasize UVD's role in delivering low-power, high-quality video decoding while evolving alongside operating system advancements.

Linux Kernel Integration

The integration of AMD's Unified Video Decoder (UVD) into the began with proprietary drivers and evolved toward open-source implementations, enabling hardware-accelerated video decoding on GPUs. Initial support arrived in October 2008 through the fglrx driver (version 8.10), which utilized closed-source UVD to accelerate video playback via the XvMC extension for compatible applications. This proprietary approach provided basic decoding for formats like H.264 and MPEG on early series GPUs but limited broader adoption due to its closed nature and lack of integration with open-source components. The shift to open-source drivers marked a significant transition, starting with partial UVD integration in the kernel driver around 2010, though full functionality awaited availability. By April 2013, released open-source UVD for GPUs from the R700 (Radeon HD 3000/4000 series) through the R8000 (HD 7000 series), enabling hardware decoding in the mainline via the driver and API in Mesa. Full open-source support expanded in with the introduction of the amdgpu driver in 4.0, targeting UVD 4 and later generations on (GCN) architectures, including comprehensive exposure for H.264, , and MPEG decoding. Firmware advancements continued to enhance capabilities, with support for HEVC (H.265) decoding added through the radeonsi Gallium3D driver in Mesa around 2016, allowing efficient handling of high-efficiency video streams on compatible hardware. As of 2025, Mesa 25.0 includes improvements to UVD for older hardware, enhancing video acceleration reliability. Additionally, VA-API support for VP9 decoding via UVD became robust in applications like , leveraging Mesa's gallium drivers for smooth WebM playback in modern browsers. Performance under achieves approximately 95% of Windows driver speeds for video decoding tasks, with benchmarks showing near-parity in frame rates and CPU offload efficiency on equivalent . Multi-stream decoding support arrived in Mesa 25.0 (2025) and later, facilitating concurrent playback of multiple videos in pipelines for media servers and players. Major distributions like and provided full UVD integration via amdgpu since 2016, coinciding with the deprecation of fglrx and default adoption of open-source stacks, though very old kernels (pre-3.10) exclude UVD features entirely.

Legacy and Evolution

Predecessor Technologies

Prior to the introduction of the Unified Video Decoder (UVD) in 2007, developed several technologies to accelerate video decoding, addressing the escalating computational demands of emerging codecs like H.264 while building on lessons from software and early hardware approaches. initial approach to hardware video acceleration relied on programmable units within the , introduced in 2005 with the R500-generation GPUs, to perform decoding tasks for and MPEG-4 formats. This shader-based offload avoided a dedicated (ASIC) but imposed high CPU overhead for bitstream parsing and , as the GPU resources were shared with rendering workloads, limiting efficiency for complex streams. Building on this, ATI's Avivo video engine, launched in 2005 alongside the , represented the company's first integrated hardware video processing block with support for shader-accelerated H.264 decoding up to resolution. Avivo incorporated programmable video processors for and scaling, but its dependence on GPU s led to elevated power consumption and scalability challenges, particularly for higher resolutions or multi-stream playback, as shader utilization diverted cycles from graphics tasks and increased overall thermal output. Complementing these GPU-integrated efforts, ATI's Xilleon family of standalone system-on-chip (SoC) processors, introduced around 2001 for digital televisions and set-top boxes, provided dedicated ASICs for MPEG-2 decompression and advanced image processing. The Xilleon designs featured low-power cores, including licensed Tensilica Xtensa configurable processors licensed by ATI in 2004, which influenced the programmable entropy decoding and bitstream handling in later integrated solutions like UVD. These predecessors emerged in response to the inefficiencies of pure software decoding, where tools like FFmpeg struggled with the high of H.264, often requiring substantial CPU resources—up to several times more than prior standards like —for playback on mid-2000s hardware. Early dedicated from competitors, such as Nvidia's VP1 video processor introduced in 2004, further underscored the need for specialized acceleration to handle bitstream parsing and inverse transforms without overwhelming the host CPU. Avivo's shader-centric limitations in power efficiency and ability to scale to full HD content ultimately drove the shift to UVD's dedicated ASIC architecture, enabling more efficient, GPU-independent decoding for broader support.

Transition to Video Core Next

In the period from 2017 to 2018, AMD pursued the transition from the Unified Video Decoder (UVD) to (VCN) primarily to address the limitations of having separate hardware blocks for video decoding (UVD) and encoding (, or VCE), aiming for a more integrated accelerator that could natively support emerging codecs like and prepare for efficient handling of 8K resolutions. This shift was motivated by the need for improved power efficiency and in modern GPUs and , as the standalone UVD design, while effective for its era, had become outdated amid rising demands for unified encode/decode pipelines in consumer and professional applications. VCN 1.0 was introduced in 2018 with the Raven Ridge , directly succeeding UVD 7 by inheriting its core decoding capabilities for codecs such as H.264/AVC and H.265/HEVC while adding native hardware support for decoding at up to with 10-bit color depth in P010 format. This version marked the unification of encoding and decoding into a single hardware block, enabling more streamlined and driver support compared to the prior segregated architecture. Key differences included a consolidated ASIC for both functions, which reduced complexity and improved power consumption, particularly as subsequent iterations aligned with the RDNA architecture for further efficiency gains; later VCN generations also phased out support for legacy codecs like to prioritize modern formats. Backward compatibility for pre-2018 hardware remained robust, with UVD firmware integrated into the open-source amdgpu driver, ensuring continued support for older GPUs through at least 2025 via ongoing Linux kernel and Mesa updates. The evolution of VCN progressed rapidly: VCN 2.0, debuting in 2019 with the Navi-based Radeon RX 5000 series, extended resolution support to 8K for H.264 and HEVC while enhancing overall encode/decode throughput. By VCN 5.0 in the RDNA 4 architecture (with driver support continuing into 2025), Linux driver patches indicated preparations for AI-accelerated video processing enhancements, building on prior generations' foundations. This transition had significant impacts, notably enabling full AV1 encoding and decoding at 8K resolutions in the powered by VCN 4.0, which facilitated high-efficiency streaming and workflows. Meanwhile, UVD's legacy persisted for a substantial portion of the user base relying on pre-Raven Ridge hardware, underscoring the gradual adoption of VCN across AMD's ecosystem.

References

  1. [1]
    AMD Unified Video Decoder | PDF - Slideshare
    The white paper discusses AMD's Unified Video Decoder (UVD) technology, which enhances HD video playback efficiency on PCs by offloading decoding from the ...
  2. [2]
    AMD Unleashes the ATI Radeon(TM) HD 3400 ... - Investor Relations
    Jan 23, 2008 · Blu-ray or HD DVD disc playback can be enjoyed in full HD glory (1080p)(4) thanks to AMD's proprietary unified video decoder (UVD) ...
  3. [3]
    AMD Releases Open-Source UVD Video Support - Phoronix
    Apr 2, 2013 · ... AMD will be publishing open-source driver code that exposes their Unified Video Decoder (UVD) engine on modern Radeon HD graphics cards.
  4. [4]
    AMD Introduces ATI Mobility Radeon(TM) HD 3000 Series
    Jan 7, 2008 · ... Unified Video Decoder (UVD) offering full hardware acceleration of video decode for smooth playback of full 1080p content from HD DVD and ...
  5. [5]
    Unified Video Decoder 2 - HIS Graphic Cards
    The UVD 2 features full bitstream decoding of H.264/MPEG-4 AVC and VC-1 video streams, and in addition it also supports dual video stream decoding and Picture- ...
  6. [6]
    AMD Extends Graphics Performance Lead, Launches World's ...
    Mar 8, 2011 · Enhanced video quality features: AMD Radeon HD 6990 graphics cards feature Unified Video Decoder 3 (UVD3), a dedicated video playback ...
  7. [7]
    AMD Radeon R9-285 review (Page 4) - www.guru3d.com
    Rating 5.0 · Review by Hilbert Hagedoorn (Guru3D)Sep 2, 2014 · The Radeon R9 285 is AMD's first discrete GPU with a redesigned fixed-function decoder (UVD – Unified Video Decoder) that supports full hardware decode of 4K H ...
  8. [8]
    Unified Video Decoder (UVD) engine - CPU-World
    May 6, 2025 · Unified Video Decoder, or UVD, is an integrated hardware unit, responsible for decoding of video streaming data. The UVD was introduced in ...
  9. [9]
    Vega-Based Renoir APU Has The Same VCN Video Encode ...
    Sep 9, 2019 · VCN is the combined video encode/decode block that succeeded AMD's earlier UVD and VCE hardware. Besides accelerating the various ...
  10. [10]
    AMD Unleashes Enthusiast Gaming Performance for the Masses ...
    Nov 15, 2007 · ... Unified Video Decoder (UVD). The addition of UVD ensures exceptional platform efficiency and image quality in HD-DVD and Blu-ray(TM) ...
  11. [11]
    ATI Licenses Tensilica's Xtensa Configurable Processor
    ONTARIO, Canada – October 18, 2004 – Tensilica, Inc. today announced that ATI Technologies Inc. (NASDAQ: ATYT) has licensed the Xtensa configurable ...
  12. [12]
    Graphics Specifications - AMD
    AMD Product Specifications · Graphics Specifications ...
  13. [13]
    HD2000 - The First GPU's Under the AMD Name - Bjorn3D.com
    May 14, 2007 · This is done with a new chip called the UVD (Unified Video Decoder). AMD has also added HDMI v 1.2 support as well as HDCP support over Dual- ...Missing: history Xilleon
  14. [14]
    AMD Introduces World's First Comprehensive, Cutting-Edge PC ...
    Nov 19, 2007 · The addition of UVD ensures exceptional platform efficiency and image quality in HD-DVD and Blu-ray decoding for both H.264 and VC-1 ...
  15. [15]
    Why You Need Hardware Acceleration to Fast Rip DVD Disc to Digital
    In the second year of CVT's appearance, namely 2007, AMD rolled out UVD (Unified Video Decoder) aiming to handle H.264 and VC1 used in Blu-ray and HD-DVD.
  16. [16]
    AMD Publishes Open-Source Driver Support For Vega 20 - Phoronix
    May 15, 2018 · The patches enable a new version of UVD video decoding as well, version 7.2, for this Vega 20 hardware. There are six PCI IDs currently ...
  17. [17]
    AMD Posts Linux Driver Patches For Video Core Next 5 "VCN 5.0"
    Feb 8, 2024 · The Video Core Next engine was introduced with Raven Ridge APUs for unifying the Unified Video Decoder (UVD) and Video Coding Engine (VCE) ...
  18. [18]
    Tensilica Drives Multimedia and Communications Products at CES ...
    Jan 9, 2009 · AMD uses Tensilica's processors in the ATI Radeon graphics chips with Avivo-HD UVD technology, including the Radeon HD-2400, HD-2600, HD-2600-XT ...
  19. [19]
    [PDF] AMD Video Technologies
    This 3rd generation, named UVD3, provides acceleration for MPEG-2 bitstream, MPEG-4 part 2. ASP (also known as DivX/xVid) and Multi-View Codec (MVC) formats.
  20. [20]
    AVIVO PureVideo HD DXVA GPU Acceleration Guide
    Nov 27, 2009 · Here at Benchmark Reviews, we will teach you how to use your GPU to playback and enhance HD video content, and we´re not limited to DVD or Blu- ...
  21. [21]
    [PDF] AMD Embedded G-Series SOC (Family 16h Models 00h-0Fh ...
    • Dedicated hardware (UVD) for H.264, MPEG4, VC-1, MVC, and MPEG2 decode ... 10 HDCP content protection support is available only to HDCP licensees and ...
  22. [22]
    H264 support on Radeon X1950 XT? | AnandTech Forums
    Feb 22, 2008 · Unfortuntately, the 1900 series does not support Unified Video Decoder (UVD). Only the 2000 (except the 2900) and 3000 series of ATI cards ...
  23. [23]
    AMD 硬件加速编解码支持表 - 诺德美地流媒体系统 - NodeMedia
    AMD has also stated that the UVD component being incorporated into the GPU core only occupies 4.7 mm² in area on 65 nm fabrication process node. A variation ...Missing: implementation | Show results with:implementation
  24. [24]
    None
    ### Summary of UVD and UVD 2 for Radeon HD Series
  25. [25]
  26. [26]
    ATI RV730 GPU Specs - TechPowerUp
    With a die size of 146 mm² and a transistor count of 514 million it is a small chip. RV730 supports DirectX 10.1 (Feature Level 10_1).
  27. [27]
    ATI Graphics video decoder and AMD Polaris / Vega GPU VP9 ...
    Nov 22, 2021 · On December 8, 2016, AMD released Crimson ReLive drivers (Version 16.12.1), which make GCN-GPUs support VP9 decode acceleration up to 4K@60 Hz.
  28. [28]
    Radeon HD 6000 Series | Encyclopedia MDPI
    In the HD 6000-series cards, AMD's Universal Video Decoder was upgraded to version 3.0 which supported Blu-ray 3D codecs, hardware decoding for DivX / XviD and ...Missing: MPEG- entropy 120Hz Sumo
  29. [29]
    True Fusion: AMD A8-3800 APU Review - XbitLabs
    Aug 28, 2014 · Secondly, the UDV (Unified Video Decoder) unit in Sumo has been replaced with a newer version. Version 3 of the video decoder in Llano ...
  30. [30]
    AMD Llano A-Series APU Sabine Notebook Platform Review
    Jun 13, 2011 · The A-Series APU features UVD3 which is the third generation Unified Video Decoder. This is a hardware decoder with support for H.264, VC-11, MPEG2, WMV, DivX, ...
  31. [31]
    AMD Radeon HD 6000 Series Gallium3D Attempts To ... - Phoronix
    Jul 14, 2011 · In this article are our first benchmarks of the AMD Northern Islands and Cayman graphics processors using the open-source Mesa Gallium3D driver.
  32. [32]
    The 30 Year History of AMD Graphics, In Pictures - Tom's Hardware
    Aug 19, 2017 · From the ATI Wonder in 1986 to the AMD Radeon RX in 2016, we take a look at the evolution of AMD graphics.
  33. [33]
    AMD Pitcairn GPU Specs - TechPowerUp
    AMD's Pitcairn GPU uses the GCN 1.0 architecture and is made using a 28 nm production process at TSMC. With a die size of 212 mm² and a transistor count of ...
  34. [34]
    AMD Radeon R9 FURY Specs - GPU Database - TechPowerUp
    The Radeon R9 FURY was a high-end graphics card by AMD, launched on July 10th, 2015. Built on the 28 nm process, and based on the Fiji graphics processor.
  35. [35]
    AMD Radeon Instinct MI50 Specs | TechPowerUp GPU Database
    The Radeon Instinct MI50 is a professional graphics card by AMD, launched on November 18th, 2018. Built on the 7 nm process, and based on the Vega 20 graphics ...Missing: UVD multi-
  36. [36]
    RadeonSI UVD/VCE Video Acceleration Improvements Merged For ...
    Jan 17, 2025 · These patches rework the Video Coding Engine (VCE) and Unified Video Decoder (UVD) support found with older AMD Radeon graphics processors.Missing: introduction replaces 2018
  37. [37]
    OBS branch with AMD VCE support.
    May 2, 2014 · Next, go to the AMD VCE settings tab and check "use Custom settings", Check the preset selector (speed,Balanced,quality) at the upper-right.Question / Help - Does OBS Studio support AMD's VCE?Best Settings for AMD CPU/GPU Twitch | OBS ForumsMore results from obsproject.com
  38. [38]
    FAQ: All about Hardware Encoding in Premiere Pro 14.2
    May 21, 2020 · To enable Hardware Encoding, navigate to Export Settings and select H.264 or H.265 as Format. Under the Video tab scroll down to Encoding Settings and set ...Any decoding improvements on Premiere Pro V.22 for AMD systems ...Discuss : AMD Hardware Accelerated Encode for H264/HEVCMore results from community.adobe.comMissing: UVD | Show results with:UVD
  39. [39]
    Here are some sample HEVC Encodes Using Polaris' VCE ... - Reddit
    Aug 19, 2016 · And yeah the speed is fantastic. Always over 120fps, over 350fps for lower resolutions. Compare to software x265 encoding on my FX 8320 where ...AMD Raven APUs leave behind UVD (Unified Video Decoder) and ...New Linux Patches Enhance AMD Radeon Video Encode/Decode ...More results from www.reddit.comMissing: UVD | Show results with:UVD
  40. [40]
    AMD Software: Adrenalin Edition 25.10.2 Release Notes
    AMD Software: Adrenalin Edition 25.10.2 is a notebook reference graphics driver with limited support for system vendor specific features. AMD ...Highlights · Installing Amd Software... · Radeon Product CompatibilityMissing: UVD VCE
  41. [41]
    Innovative Tensilica-Based Products on Display at CES 2008 - EDN
    Jan 7, 2008 · Tensilica's announced licensees include Afa Technologies, ALPS, Aquantia, Astute Networks, Atheros, AMD (ATI), Avision, Bay Microsystems, ...
  42. [42]
    ATi UVD with bad H.264 error concealment - AVS Forum
    Feb 6, 2010 · ATi UVD with bad H.264 error concealment Live streams via satellite are always more prone to errors, for example due to the influence of ...Two Audio Streams via both GPU HDMI Out? - AVS ForumHow much data in audio stream? | AVS ForumMore results from www.avsforum.com
  43. [43]
  44. [44]
    AMD/ATI Radeon 4870 X2 Review - www.impulsegamer.com -
    AMD ... 2nd generation Unified Video Decoder (UVD 2). Enabling hardware decode acceleration of H.264, VC-1 and MPEG-2; Dual stream playback (or Picture-in-picture).
  45. [45]
    New Linux Patches Enhance AMD Radeon Video Encode/Decode ...
    Jan 3, 2025 · This newly opened merge request adds a number of features for older AMD GPUs with VCE and UVD to better match functionality that until now was ...
  46. [46]
    UVD-Based HEVC Video Encoding Main Now Supported In Mesa 18.1
    Feb 24, 2018 · Earlier this month AMD developers landed VCN-powered video encode support for the HEVC main format while now this has come to the UVD engine ...
  47. [47]
    Codecs - AMD
    AMD supports video codecs like H.264/H.265, JPEG 2000, and Apple ProRes, and audio codecs like AAC, USAC, MP3, and WMA.
  48. [48]
    DXVA not functional with resolutions greater than 1080 on AMD GPUs
    AMDs fixed function video decoder engine (UVD) has supported H.264/VC-1/WMV decoding at 4K resolution since 5.0 version, which was introduced in Tonga ASIC.
  49. [49]
    AMD GPU | Jellyfin
    This tutorial guides you on setting up full video hardware acceleration on AMD integrated GPU and discrete GPU via AMF or VA-API.<|separator|>
  50. [50]
    AMD Hardware Components Information per Product
    On this page, you can find the AMD product name and which component version is part of it. ... VCE/UVD/VCN version. SDMA version. MP0 version. MP1 version. Radeon ...Missing: history | Show results with:history
  51. [51]
    AMD Vega 10 GPU Specs - TechPowerUp
    UVD: 7.0. VCE: 4.0. SDMA: 4.0.0. MP0: 9.0.0. CLRX: GCN 1.4.0. Render Config. Shading Units: 4096. TMUs: 256. ROPs: 64. Compute Units: 64. ACEs: 4. HWSs: 2. GEs ...
  52. [52]
    Sixth time lucky: AMD details the Carrizo APU - Ars Technica
    Jun 3, 2015 · ... and compact fashion, resulting in a reported 23 percent decrease in die area. ... Previously, AMD's Unified Video Decoder (UVD)—a part of the GPU ...
  53. [53]
  54. [54]
    [PDF] energy efficient graphics and multimedia in 28nm carrizo apu
    Aug 27, 2015 · “Carrizo” UVD and power gates itself off and puts DRAM into low power mode ... Driver version Catalyst 14.12 & BIOS of WBL4709N for KV ...
  55. [55]
    AMD Carrizo Mainstream APUs Overview - Notebookcheck
    Jun 3, 2015 · The new UVD 6 (Universal Video Decoder) now supports the decoding of HEVC/H.265 videos with up to 4K, and H.264 and MJPEG videos up to 4K ...
  56. [56]
    Mesa VCN JPEG Decode Patches Posted For AMD Raven Ridge
    Oct 17, 2018 · With the imminent Linux 4.19 kernel release there is VCN JPEG decode support within the AMDGPU DRM driver for use with Raven Ridge APUs.
  57. [57]
    [PDF] ATI Catalyst™ Software Suite Version 10.2 Release Notes - AMD
    Note: The ATI Catalyst™ driver includes TV/Capture driver support for many ATI Theater 600 and ATI Theater 650 products under. Windows 7 (in addition to ATI ...
  58. [58]
    AMD Radeon™ Software Crimson Edition 16.2.1 Beta Driver
    This article provides information on the latest posting of the AMD Radeon Software Crimson Edition 16.2.1 Beta Driver for non GCN products.
  59. [59]
    About DXVA 2.0 - Win32 apps | Microsoft Learn
    Jan 7, 2021 · In this article · If the graphics driver conforms to the Windows Display Driver Model (WDDM), DXVA 1 API calls are converted to DXVA 2 DDI calls.Missing: AMD UVD
  60. [60]
    Radeon™ RX 470 Drivers and Downloads | Latest Version - AMD
    ... Unified Video Decoder (UVD) , Video Code Engine (VCE) , AMD Virtual Super Resolution , The Vulkan® API , AMD ZeroCore Power Technology , AMD Gaming Evolved ...<|separator|>
  61. [61]
    AMD Software: Adrenalin Edition 25.6.3 Optional Update Release ...
    Intermittent system or application crash maybe observed while playing Black Myth: WuKong on Radeon™ RX 7650 GRE graphics products. Texture flickering or ...Missing: June UVD
  62. [62]
  63. [63]
    AMD Software: Adrenalin Edition 24.7.1 Release Notes
    Version 24.7.1 adds Windows 11 24H2 support, fixes shader caching issues, and some Vulkan game crashes. Some DirectX 12 crashes with non-English usernames are ...
  64. [64]
  65. [65]
    Yes, Catalyst 8.10 Is Out There - Phoronix
    Oct 16, 2008 · It does have UVD Linux support enabled to accelerate video playback via the XvMC extension and their own HD video interface. However, all ...
  66. [66]
    drm/amdgpu AMDgpu driver — The Linux Kernel documentation
    The amdgpu driver provides a sysfs API for reading how busy the GPU is as a percentage. The file gpu_busy_percent is used for this. The SMU firmware ...
  67. [67]
    H.265/HEVC Main 10 Decode Support Added To Radeon UVD ...
    Mar 8, 2016 · AMD developers have today sent out patches for implementing HEVC Main 10 provide video decode support to the open-source RadeonSI UVD driver ...
  68. [68]
    Linux 6.11-rc7 To Fix A "Massive Performance Regression" For AMD ...
    Sep 6, 2024 · This week's DRM fixes with this AMDGPU patch and the other fixes should be merged today to Linux Git and be found in Sunday's Linux 6.11-rc7 ...Missing: UVD 7
  69. [69]
    Windows 11 vs. Ubuntu Linux Performance On The AMD Ryzen AI ...
    Jun 19, 2025 · Ubuntu 25.04 was faster in 66% of the benchmarks. For the wins that Microsoft Windows did enjoy, it typically involved a subset of the graphics benchmarks.
  70. [70]
    Ubuntu 16.04 Deprecates AMD fglrx Driver Support - PC Perspective
    Mar 9, 2016 · AMD has been transitioning their kernel driver from the closed-source fglrx to the open-source AMDGPU driver that was announced last year. This ...
  71. [71]
    Video Shader - Wikipedia
    Video Shader is a graphics card feature that ATI advertises on their R300 and R400 cards. The R500 card is advertised as having Video Shader HD.
  72. [72]
    Review: ATI Avivo Winter 2005 Update - Graphics - HEXUS.net
    Dec 16, 2005 · H.264 AVC HD Decoding. Until today, ATI haven't had a supported H.264 AVC decoder that used Avivo hardware, that's publically available.Missing: X1000 | Show results with:X1000
  73. [73]
    ATI AVIVO. Part 0: Introduction and Description of Video Technologies
    Dec 30, 2005 · ATI video chips take up part of H.264 decoding job, which is usually performed by a CPU. ATI RADEON X1000 chips supporting AVIVO technologies ...
  74. [74]
    Nvidia decodes H.264 in hardware | bit-tech.net
    Jan 7, 2006 · Avivo? This is different from ATI's Avivo technology, which decodes H.264 video on Radeon X1000 series cards. Avivo uses pixel shaders to decode ...
  75. [75]
    Avivo vs. Purevideo, Round 1: The Radeon X1000 vs. Geforce 7000 ...
    Jan 10, 2007 · The short answer is that an X1600 is supposed to be able to hardware-accelerate 720p, I think you need an X1950 PRO or X1900 GT to accelerate ...
  76. [76]
    Embedded Processor and System-on-Chip Quick Reference Guide
    Oct. 17, 2001 — The ATI XILLEON 220 includes a 300MHz MIPS core with MMU, along with ...<|control11|><|separator|>
  77. [77]
    Overview of VP1 video processor - envytools git documentation
    VP1 is basically a vector processor with PFIFO interface and custom ISA designed for video decoding. It's made of the following units: the processor proper:.Missing: 2001 | Show results with:2001
  78. [78]
    Radeon VCN Encode Support For RadeonSI Gallium3D - Phoronix
    Nov 7, 2017 · VCN is a new media block with the upcoming Raven Ridge (Zen+Vega) APUs for both video encode and decode. In the past there was UVD for video ...Missing: successor | Show results with:successor<|control11|><|separator|>
  79. [79]
    Radeon VCN Video Decode Support Lands In Mesa - Phoronix
    May 25, 2017 · AMD developers have landed their work on supporting VCN video decoding in Mesa. VCN is the new video decode engine with the upcoming Raven Ridge ...Missing: successor | Show results with:successor
  80. [80]
  81. [81]
    Video Production Advanced by AMD Radeon™ Graphics
    Use AMD high-performance Radeon™ graphics with full encode/decode support for HEVC, H.264 and AV1 to help create and edit your next cinematic masterpiece.Create A Compelling Story In... · Gpu-Accelerated Playback... · Recommended Graphics For...Missing: UVD Vega<|separator|>
  82. [82]
    AMD Posts Linux Driver Patches For New "VCN 4.0" IP Block
    May 2, 2022 · The AV1 decode is limited to 8K and lower. We'll see what future patch series bring to the VCN4 features. This initial VCN4 bring-up patch ...