Fact-checked by Grok 2 weeks ago

Video Coding Engine

The Video Coding Engine (VCE) is a dedicated component developed by and integrated into its graphics processing units (GPUs), providing accelerated video encoding for standards such as H.264/AVC, with subsequent generations adding support for H.265/HEVC; its successor, (VCN), added support for to enable efficient compression of high-resolution video streams for streaming, recording, and content creation. Introduced in December 2011 alongside the GPUs based on the (GCN) architecture, VCE marked AMD's first full hardware implementation of video encoding, capable of handling video at 60 frames per second while offloading computational tasks from the CPU to improve system performance during real-time applications like game capture and live broadcasting. Over multiple iterations, VCE evolved to enhance encoding quality and efficiency; for example, VCE 1.0 focused on baseline H.264 support, VCE 2.0 introduced improvements for higher bitrates and dual-pipe encoding in the R9 200 series, and VCE 3.0 added HEVC encoding in products like the and GPUs, allowing for better compression ratios in workflows. In 2018, with the release of the Raven APUs, AMD replaced VCE and the separate (UVD) with the unified (VCN) architecture, which expanded to include both encoding and decoding while maintaining and introducing features like encoding in later RDNA-based GPUs such as the RX 7000 series. Developers access VCE and its successors through frameworks like the open-source Advanced Media Framework (AMF) SDK, which supports cross-platform integration for video processing in applications including , , and , ensuring low-latency performance and reduced power consumption compared to software-only encoding.

Introduction

Purpose and Capabilities

The Video Coding Engine (VCE) is an (ASIC) developed by for hardware-accelerated video encoding, primarily implementing the to compress high-definition video streams. Introduced as a dedicated hardware block within AMD graphics processors, VCE offloads encoding tasks from the CPU, enabling efficient processing without relying on general-purpose compute resources. VCE supports full hardware encoding of H.264 video up to resolution at 60 frames per second, including profile with CABAC for high-quality compression. It offers two primary modes: a full-fixed mode where the entire encoding pipeline operates on the ASIC for maximum efficiency, and a hybrid mode that combines the VCE's encoding block with GPU compute units (such as 3D shaders) to handle and other tasks, allowing for scalable performance based on workload demands. Integration is facilitated through APIs like IL for fixed-mode access and the APP SDK with support for hybrid operations, enabling developers to leverage VCE in multimedia applications. By performing encoding in dedicated , VCE significantly reduces CPU utilization, power consumption, and compared to software-based methods, supporting transcoding and applications like for streaming and recording. It complements AMD's (UVD) to provide asymmetric encode/decode capabilities in graphics , optimizing overall media workflows. Later iterations expanded support to codecs like HEVC for higher efficiency.

Development History

The Video Coding Engine (VCE) originated from AMD's efforts, building on its acquisition of in 2006, to integrate dedicated video encoding hardware into consumer GPUs amid rising demands for efficient video processing in applications like gaming and streaming. Announced on December 22, 2011, alongside the launch of the (codenamed Southern Islands), VCE marked AMD's entry into hardware-accelerated video encoding for mainstream discrete graphics cards. This introduction coincided with the debut of AMD's (GCN) architecture, which provided the foundational compute framework for VCE's implementation, enabling seamless integration within the GPU die to handle encoding tasks without heavily relying on the CPU. Initially, VCE focused on supporting the H.264/MPEG-4 AVC , prioritizing low-latency encoding suitable for applications such as displays and . Key milestones in its early development included optimizations for compression, with the engine occupying a significant portion of the GPU's die area to deliver performance comparable to software encoders but with lower power consumption and CPU overhead. As iterated on GCN architectures—from the first-generation Southern Islands through subsequent and Volcanic Islands families—VCE evolved to support higher resolutions and frame rates, maintaining compatibility across GPUs and while addressing the growing needs of content creators and broadcasters. Development progressed with the addition of support for emerging standards, notably HEVC/H.265 encoding introduced in 2014-2015 with VCE 3.0 in GPUs like the R9 285 () and R9 (), enabling video handling for ultra-high-definition content, and aligned with industry shifts toward more bandwidth-efficient formats. Further improvements appeared in 2016 GPUs and the 400 series. The primary motivations for VCE's creation stemmed from the inefficiencies of software-based encoding, which strained CPU resources and limited performance in , , and streaming workflows; by offloading these tasks to specialized , AMD aimed to enhance and compete effectively in the market dominated by CPU-bound solutions. This positioned VCE as a direct counterpart to like NVIDIA's NVENC, introduced shortly after in , fostering a competitive that accelerated encoding adoption. Primary development of VCE concluded around 2017-2018, with AMD transitioning to a unified (VCN) engine starting with the Raven Ridge APUs in late 2017, which combined encoding and decoding capabilities for more streamlined media processing.

Version History

VCE 1.0

The Video Coding Engine 1.0 (VCE 1.0) marked AMD's initial foray into dedicated video encoding, debuting in late 2011 alongside the Southern Islands GPU family, such as the Radeon HD 7700 series graphics cards. This version established a foundational block for accelerating H.264 encoding, positioned as a counterpart to Intel's Quick Sync technology, and was later integrated into Piledriver-based Accelerated Processing Units () like the (released in 2012) and Richland (released in 2013) platforms. VCE 1.0 represented the first (ASIC) in AMD's lineup solely dedicated to video encoding, operating independently from the existing (UVD) which handled decoding tasks. At its core, VCE 1.0 supported H.264 (MPEG-4 AVC) encoding in color format, limited to intra-frame (I-frames) and predictive (P-frames) types without bidirectional (B-frames) for . It also incorporated Scalable Video Coding () temporal encoding capabilities for layered scalability in video streams and a basic Display Encode Mode (DEM) with an integrated deblocking engine to reduce compression artifacts. These features were embedded within the (GCN) 1.0 architecture, occupying a notable portion of the die area to enable efficient, low-latency encoding primarily optimized for applications like wireless display streaming. Despite its pioneering role, VCE 1.0 had notable constraints that reflected its early-stage design. It lacked support for 4:4:4 color formats and advanced video scaling operations, restricting its versatility for professional workflows. The maximum output resolution was capped at (1920x1080) at 60 frames per second, aligning with high-definition streaming needs of the era but limiting higher-resolution or frame-rate scenarios. Subsequent iterations, such as VCE 2.0, addressed some of these shortcomings by adding B-frame support for improved compression efficiency. Overall, VCE 1.0 laid the groundwork for AMD's evolving video ecosystem, prioritizing real-time performance over advanced flexibility.

VCE 2.0

VCE 2.0 debuted in 2013 alongside AMD's GPUs, including the mid-range HD 7790, marking the introduction of the GCN 2.0 architecture. This version of the engine was also integrated into Steamroller-based and Godavari APUs, providing hardware-accelerated video encoding capabilities in both discrete graphics and integrated solutions. Built directly into the GCN 2.0 architecture, VCE 2.0 supports scalable hybrid encoding, where and other tasks can offload to the GPU's compute units for improved throughput in resource-intensive scenarios. Key enhancements in VCE 2.0 focused on expanding H.264 encoding flexibility and quality. It added support for H.264 YUV444 encoding in I-frames, enabling higher-fidelity color representation suitable for applications like wireless displays at 60 Hz. Additionally, B-frames were introduced for H.264 YUV420, allowing bidirectional prediction to enhance temporal compression. An upgraded Display Encode Mode (DEM) improved deblocking filters, reducing artifacts and elevating overall visual fidelity during real-time encoding tasks. These upgrades delivered better bit-rate efficiency and visual quality compared to VCE 1.0, particularly through B-frame support that optimized without sacrificing detail in standard H.264 workflows. However, VCE 2.0 remained limited to H.264 encoding, lacking support for emerging codecs like HEVC. This version laid foundational scaling mechanisms that influenced subsequent iterations, such as VCE 3.x.

VCE 3.x

VCE 3.0 was introduced with the GCN 3.0 architecture in the and GPUs, including the R9 285 released in 2014 and the R9 Fury series in 2015. This version featured an updated Video Coding Engine with improved performance for video encoding, supporting H.264 encoding up to resolution. A variant, VCE 3.1, was integrated into the Carrizo launched in 2015, featuring dual H.264 encoder instances capable of encoding, twin front-end pipelines per instance, and up to 350% improvement in throughput compared to the previous generation, with performance reaching 169 for 720p-to-720p and 78 for 1080p-to-720p/ transcoding. VCE 3.4 arrived in 2016 with the GPUs, such as the 470, and added support for HEVC/H.265 encoding up to , marking a shift toward high-efficiency codecs for the 4K era while removing H.264 B-frame support to prioritize HEVC performance. This version improved efficiency for high-resolution encoding in GCN 4.0 architectures, though 10-bit HEVC encoding was not supported in initial implementations, with decoding available on hardware.

VCE 4.x

VCE 4.0 was released in 2017 alongside AMD's GPUs, including models like the , marking a significant advancement in the Video Coding Engine's capabilities for high-performance video encoding. This version integrated into the (GCN) 5.0 architecture, which emphasized improved compute efficiency and memory bandwidth to support demanding multimedia workloads. VCE 4.1 arrived in 2018 with the Vega 20 GPUs, such as the Instinct MI50 accelerator, extending these enhancements to professional and compute-oriented applications. The specifications of VCE 4.x focused on refined HEVC (H.265) encoding, featuring superior rate control mechanisms like constant bitrate (CBR) and (VBR) modes with enhanced quality preservation compared to prior iterations, reducing artifacts in complex scenes. It maintained support for both H.264 (AVC) and HEVC codecs, enabling resolutions up to at 60 fps in standard modes, while hybrid configurations leveraged GPU assistance for scalability in higher-resolution workflows. Improved hybrid encoding scalability allowed seamless integration of with software elements, optimizing throughput for multi-stream scenarios and reducing latency in applications. Key features in VCE 4.x included advanced video preprocessing and analytics capabilities through the AMD Advanced Media Framework (AMF), such as content-adaptive quantization and preprocessing, which boosted compression efficiency and visual fidelity for broadcast and streaming use cases. These optimizations delivered higher throughput for professional workloads, with Vega-based implementations achieving up to 2x faster encoding speeds in HEVC compared to GCN 4.x predecessors, particularly in multi-pass modes for . As part of the GCN 5.0 architecture, VCE 4.x represented the culmination of AMD's dedicated video encoding hardware, incorporating next-generation compute units for better power efficiency and integration with high-bandwidth memory (HBM2). It served as the final major standalone VCE iteration before the transition to the unified (VCN) engine beginning in 2018.

Technical Features

Supported Codecs

The Video Coding Engine (VCE) primarily supports H.264/MPEG-4 AVC as its core across all versions, providing hardware-accelerated encoding for with capabilities such as intra and inter-frame prediction. This operates with profiles including High Profile, accommodating 4:2:0 format at bit depths up to 8-bit, ensuring compatibility with a wide range of broadcast and streaming applications. HEVC/H.265 encoding was introduced in VCE 3.4, marking a significant advancement in compression efficiency for higher resolutions and bit depths. It supports Main and Main10 profiles, enabling up to 10-bit color depth suitable for HDR content, with resolutions reaching 4K at 60 fps. In VCE 4.x iterations, these capabilities were improved for higher efficiency in 4K workflows while maintaining dual compatibility with H.264. Early VCE versions, such as 1.0 and 2.0, offered limited support for Scalable Video Coding () extensions of H.264, primarily for temporal scalability in scenarios. However, VCE does not include native encoding for or formats, with such capabilities emerging in successor technologies like . Over its evolution, VCE shifted from H.264-exclusive encoding to a dual H.264/HEVC framework, broadening applicability for streaming, content distribution, and professional by balancing compression ratios and quality. Encoding modes for these codecs, such as constant bitrate and variable bitrate options, are handled through integrated processes detailed separately.

Encoding Modes and Processes

The Video Coding Engine (VCE) supports two primary encoding modes to balance performance, latency, and flexibility: full-fixed mode and hybrid mode. In full-fixed mode, the entire encoding pipeline is executed exclusively by dedicated ASIC , minimizing latency and enabling real-time encoding without involvement from the GPU's programmable units, which is ideal for applications requiring low power and high-speed processing such as . This mode handles all steps of the through fixed-function logic, similar to Intel's Quick Sync Video, achieving efficient macroblock-level parallelism for resolutions up to at 60 . In contrast, hybrid mode integrates the ASIC with the GPU's 3D or compute shaders, offloading certain computations to programmable units for enhanced features like advanced or custom filtering, though this increases power consumption and complexity. Codecs like H.264 are processed in these modes, leveraging VCE's for core tasks. The encoding process in VCE follows a structured optimized for efficiency, beginning with input preprocessing that includes to match target and color space conversion (e.g., from RGB to ) to prepare raw video for compression. Subsequent stages involve and compensation, where the engine searches for temporal redundancies across using block-matching algorithms to generate motion vectors, typically at or sub-macroblock levels for inter-prediction in P- and B-. Intra- and inter-prediction modes are then applied: intra-prediction uses spatial correlations within the current to predict values from neighboring blocks, while inter-prediction combines motion-compensated from reference , with mode selection based on rate-distortion optimization to minimize encoding cost. Following prediction, the residual data undergoes transform and quantization, where a (DCT) or similar integer transform converts spatial data into frequency coefficients, followed by quantization to reduce precision and control bitrate, with quantization parameters (QP) adjusted dynamically for quality-bitrate trade-offs. Entropy coding concludes the core pipeline, employing Context-Adaptive Binary Arithmetic Coding (CABAC) or Context-Adaptive Variable-Length Coding (CAVLC) to compress the quantized coefficients and syntax elements into a compact , ensuring efficient data packing without loss of essential information. The output generation assembles these elements into a standards-compliant container, ready for transmission or storage. Unique to VCE's design, the hybrid mode allows scalability by utilizing GPU shaders for custom pre- or post-processing filters, such as or temporal denoising, extending beyond fixed-function capabilities. An integrated deblocking engine (DEM) applies in-loop filtering to reduce blocking artifacts at boundaries, improving visual quality by smoothing discontinuities while preserving edges, as part of the reconstruction loop in both modes. Overall efficiency stems from parallelism, where multiple are processed concurrently across pipeline stages, enabling real-time encoding rates (e.g., at 30-60 ) with minimal CPU intervention, thus offloading the host processor for other tasks.

Hardware Implementations

GPUs

The Video Coding Engine (VCE) is embedded as a dedicated hardware block within AMD's (GCN) architectures, from version 1.0 through 5.0, providing fixed-function acceleration for video encoding tasks. This integration occurs alongside the (UVD) on the GPU die, forming a cohesive processing unit that optimizes space and power efficiency for both encoding and decoding operations. The VCE's performance scales with the overall GPU configuration, particularly the number of compute units (CUs); higher-CU designs, such as those in flagship models, support elevated clock speeds and power delivery, enabling greater encoding throughput compared to entry-level variants within the same family. Prominent implementations of VCE span multiple GCN-based discrete GPU generations, each advancing codec support and efficiency. The Southern Islands family, including the , debuted VCE 1.0 with H.264 encoding capabilities. GPUs, such as the Radeon HD 7790, upgraded to VCE 2.0, adding multi-reference frame for improved . In the Volcanic Islands era, and architectures—seen in the Radeon R9 285 and R9 Fury—introduced VCE 3.0 with advanced H.264 features, including dual-pipe encoding. GPUs like the Radeon RX 470 introduced VCE 3.4 with HEVC Main10 encoding support for 10-bit . Vega-based cards, exemplified by the Radeon VII, featured VCE 4.0, unifying further refinements in high-efficiency video coding. In terms of performance, later VCE iterations deliver robust capabilities for modern resolutions, with versions 3.4 and 4.0 supporting HEVC encoding up to (3840x2160) at 60 frames per second, achieving rates suitable for demanding workloads while maintaining low . This enables efficient handling of high-bitrate without significantly impacting GPU compute resources for rendering. Such performance is evident in benchmarks where and GPUs encode HEVC content at speeds exceeding 25-30 under balanced presets, scaling to 60 with optimized settings. VCE finds practical application in gaming and scenarios on discrete GPUs, where its low-overhead design minimizes interference with primary rendering tasks. Within AMD's Software: Adrenalin Edition, VCE powers real-time encoding for streaming and gameplay capture via features like Radeon ReLive, supporting H.264 and HEVC outputs for platforms such as and with frame rates up to 60 at or higher. In professional , it accelerates workflows in , enabling GPU-accelerated HEVC exports and playback, which can reduce render times by up to 50% compared to CPU-only processing on compatible GPUs.

APUs

The Video Coding Engine (VCE) is integrated into Accelerated Processing Units (), combining video encoding hardware with CPU cores on a single die to enable efficient processing in power-constrained environments such as laptops and desktop all-in-one systems. In desktop , VCE shares the FM2 and FM2+ sockets with Piledriver, , and CPU architectures, allowing seamless operation within unified system-on-chip designs. These implementations feature lower clock speeds compared to GPUs, typically operating at reduced frequencies to adhere to (TDP) limits of 65-95W, which optimizes for mobile and compact desktop scenarios. Key VCE implementations in include the and Richland series, based on Piledriver CPU cores with VCE 1.0, introduced in 2012 and 2013 for FM2/FM2+ sockets. These provided foundational H.264 encoding support tailored for integrated graphics. Subsequent generations advanced with the and Godavari APUs, utilizing cores and VCE 2.0 starting in 2014, also on FM2+ sockets, enhancing encode quality and adding features like improved rate control for better efficiency in shared die environments. The mobile-focused Carrizo APU, powered by cores and VCE 3.1 in 2015, further refined these capabilities for laptop platforms with socketless BGA packaging, emphasizing low-power operation. Performance in APU-based VCE is balanced for encoding at 30-60 frames per second, prioritizing thermal and power efficiency over the higher throughput of discrete GPU counterparts. A mode in these leverages shared CPU and GPU resources, including unified access, to distribute encoding tasks and reduce overall system load during multimedia workloads. This approach enables real-time processing without excessive heat generation, contrasting with the performance-oriented designs in standalone GPUs. VCE in supports use cases like video conferencing and light streaming on laptops, where low-latency H.264 encoding ensures smooth real-time communication under battery constraints. In all-in-one PCs, it facilitates content creation tasks such as basic and recording, benefiting from the integrated design's efficiency for everyday applications.

Software Support

Windows

Support for the AMD Video Coding Engine (VCE) on Windows is provided through 's graphics drivers, which enable hardware-accelerated video encoding. The legacy AMD drivers, starting from version 13.10 beta, introduced initial VCE support for H.264 encoding on compatible GPUs. These were succeeded by the AMD Software: Adrenalin Edition drivers, which continue to support VCE hardware in later generations through version 22.6.1 for and subsequent versions for and later as of 2025. VCE accessibility on Windows leverages (DXVA) for decoder integration and for encoder transforms, allowing seamless use in applications. For developer access, VCE is primarily controlled via the AMD Advanced Media Framework (AMF) SDK, which offers an API for video encoding, decoding, and preprocessing on GPUs, including VCE blocks. This SDK integrates with earlier tools like the AMD APP SDK, enabling hybrid CPU-GPU encoding workflows for custom applications on SP1 and later. Low-level control in fixed-function modes can utilize OpenMAX IL interfaces, as implemented in select AMD media pipelines for precise component integration. Several applications natively support VCE for encoding tasks on Windows. added AMD AMF-based VCE encoding for H.264 in version 0.16.2 (2016), with ongoing updates for streaming and recording. XSplit Broadcaster has included VCE since version 1.3, with enhancements in version 4.5 (2025) for HEVC and multi-GPU selection. integrated VCE support starting in version 1.2.0 (2018), configurable via preferences for H.264 and HEVC encoding. (part of Adrenalin Edition) enables real-time VCE encoding for video capture and streaming directly within its interface. MediaShow Espresso utilizes VCE for accelerated video conversion, as optimized in version 6.5 for output to mobile devices. VCE provides full compatibility for H.264 and HEVC encoding on and later, with driver updates maintaining support for legacy VCE hardware through at least 2020 releases like Adrenalin Edition 20.11.2 and continuing in 2025 drivers for supported operating systems. This ensures broad usability across GPUs from the Southern Islands to families, though newer VCN engines have largely superseded VCE in post-2017 hardware.

Linux

Support for the Video Coding Engine (VCE) on is primarily enabled through the open-source AMDGPU kernel module, which has included VCE loading and since its expansion in 2016. The module interfaces with VCE for video encoding tasks, requiring users to install the appropriate from the to enable functionality on compatible AMD GPUs and . VA- (Video Acceleration API) acts as the standard interface for hardware-accelerated encoding, allowing applications to offload H.264 and HEVC encoding to VCE without proprietary dependencies. The libva library provides the core API for integrating VA-API into applications, facilitating direct access to VCE capabilities for encoding workflows. FFmpeg, a widely used framework, incorporates a VA-API backend that leverages VCE for efficient command-line video encoding, supporting rate control modes and profile configurations compatible with hardware. Several open-source applications have adopted VCE via VA-API for encoding tasks. enables hardware-accelerated streaming and recording through VA-API, reducing CPU load during live production. utilizes VCE for batch video conversion, with support integrated into its Linux builds for faster on GPUs. offers VA-API-based encoding and playback, allowing users to export videos directly using VCE acceleration. This functionality is upstreamed within the Mesa graphics library, particularly through its Gallium3D drivers, ensuring broad compatibility across distributions. VCE compatibility on has evolved with versions: H.264 encoding became available starting with 4.7, coinciding with enhanced AMDGPU support for Polaris-era . HEVC encoding followed in 4.15, extending to GPUs with improved handling. Advanced HEVC profiles in VCE 3.x were stabilized by 2019 through Mesa updates and patches, while community efforts and recent 2025 updates continue to maintain support for legacy GCN-based .

Successor

Video Core Next (VCN)

Video Core Next (VCN) was announced in 2017 as part of AMD's Raven Ridge APUs and first released with their desktop variants in January 2018. This hardware block unifies the previously separate Video Coding Engine (VCE) for video encoding and Unified Video Decoder (UVD) for video decoding into a single, integrated unit, streamlining video acceleration within AMD's graphics processors. By merging these functions, VCN enables more efficient resource allocation and improved power efficiency for multimedia tasks in both GPUs and APUs. At its core, VCN provides symmetric encoding and decoding capabilities for key video codecs such as H.264/AVC and HEVC/H.265, with decoding support for VP9, ensuring balanced performance without the asymmetric bottlenecks seen in prior designs separating encoding and decoding. Support for AV1 decoding was introduced starting with VCN 3.0 in 2020 (RDNA 2 architecture), while VCN 4.0 in 2022 (RDNA 3, RX 7000 series) added AV1 encoding up to 8K resolutions, and VCN 5.0 in 2024 (RDNA 4) brought further efficiency improvements for high-resolution workflows as of 2025. This design emphasizes hardware-accelerated processing for mainstream video workflows, with features like HEVC Main10 (10-bit) decoding available from the outset to handle HDR content effectively. The initial VCN 1.0 iteration debuted in the 2018 Raven Ridge , offering HEVC Main10 decoding up to at 60 alongside encoding at 30 for 8-bit HEVC. VCN followed in 2019 with the 10-based Radeon RX 5000 series GPUs, retaining the primary support of VCN 1.0 but with refinements in encoding quality and overall performance efficiency. These early versions laid the foundation for VCN's evolution, focusing on reliable support for video standards. Since its debut, VCN has been adopted as the standard video engine across all AMD GPUs and APUs produced after 2017, including those utilizing the RDNA graphics architectures in subsequent Radeon and Ryzen product lines. This widespread integration has made VCN a cornerstone for AMD's multimedia ecosystem, powering applications from video streaming to content encoding in consumer and professional environments.

Transition from VCE

The transition from the Video Coding Engine (VCE) to (VCN) was primarily motivated by the need to unify AMD's previously separate hardware blocks for video decoding (, or UVD) and encoding (VCE) into a single, more integrated core. This unification streamlined hardware design, reducing overall die area and power consumption while enabling more efficient symmetric support for modern codecs such as HEVC and later , where encoding and decoding operations benefit from shared architecture. Additionally, VCN provided better future-proofing for demanding applications like 8K video processing and AI-enhanced encoding workflows, which require optimized for both directions of codec handling. VCN's rollout commenced with pre-announcements in October 2017 alongside the Raven Ridge , with the first products shipping in January 2018 and achieving full replacement of VCE in consumer by that year. Discrete GPUs followed suit later, adopting VCN starting with in the Navi-based released in July 2019. Post-transition, legacy VCE hardware in older GPUs—such as those based on and architectures—continued to receive firmware maintenance through the open-source AMDGPU driver stack, with driver support extending until approximately 2023 to ensure compatibility for existing systems. Key improvements in VCN included higher encoding efficiency and reduced power consumption for HEVC compared to VCE in equivalent workloads, alongside continued hardware decode support for formats like VP9. Backward compatibility for VCE-dependent applications was preserved via layers in drivers, allowing software to leverage VCN hardware transparently where feasible. In open-source ecosystems, while development efforts have shifted toward VCN-exclusive features, legacy VCE modes remain available for older hardware in tools like FFmpeg.

References

  1. [1]
    AMD Video and Streaming
    Is AMD Video Coding Engine (VCE) support required on my graphics product to use Record & Stream features? Yes, at minimum Video Coding Engine 1.0 support is ...Related Products · Amd Noise Suppression · Is Amd Video Coding Engine...
  2. [2]
    AMD Hardware Encoding in 2021 (VCE / VCN) - Code Calamity
    Sep 9, 2021 · VCE – Video Coding Engine – AMD's early name for its built in encoding hardware; VCN – Video Core Next – AMD's new name for GPU hardware ...Missing: definition | Show results with:definition
  3. [3]
    Video Codec Engine (VCE) - CPU-World
    May 6, 2025 · The VCE block was initially introduced in HD 7000 series of graphics cards, and consequentially it is available only in Accelerated Processing ...Missing: history | Show results with:history
  4. [4]
    AMD VCE - HandBrake Documentation
    HandBrake supports the AMD VCE encoder but does not support the VCN decoder. The CPU will still be used for: Video decoding; All video filters; Audio encoding ...
  5. [5]
    AMD Advanced Media Framework SDK - GPUOpen
    The AMD Advanced Media Framework SDK provides developers with optimal access to AMD GPUs for multimedia processing.
  6. [6]
    [PDF] Family 15h Models 10h-1Fh AMD A-Series Accelerated Processor ...
    Dec 2, 2012 · • Video compression engine: • Dedicated hardware (VCE 1.0) assisted encoding of HD video streams to H.264 (baseline + CABAC) compressed ...
  7. [7]
    https://www.anandtech.com/show/5261/amd-radeon-hd-7970-review/25
  8. [8]
    Libav Adds H.264 & MPEG4 Encoders Using OpenMAX IL - Phoronix
    Apr 13, 2016 · ... AMD VCE encoding engine using the Gallium3D OpenMAX state tracker, among other OpenMAX-supported drivers. These OpenMAX IL encoders were ...
  9. [9]
    AMD Publishes New Code For Open-Source VCE Video Encode
    Feb 11, 2014 · AMD has published a second version of their open-source Linux driver code for exposing the "VCE" video engine on modern Radeon GPUs under Linux ...
  10. [10]
    AMD Open-Sources VCE Video Encode Engine Code - Phoronix
    Feb 4, 2014 · AMD is doing another large and important open-source graphics driver code drop this morning.<|control11|><|separator|>
  11. [11]
    AMD Takes Embedded Applications to the Next Level With New GPUs
    Sep 27, 2016 · Features include next-generation UVD and VCE support; HEVC/H.265 decode and encode, and up to five display outputs using HDMI® 2.0 and/or ...
  12. [12]
    AMD Posts Initial Patches For Raven APU Support: 117 Patches ...
    The patches do confirm there is a new ACP audio with Raven Ridge as well as a new media block (VCN) that appears to replace UVD and VCE. At least initially ...
  13. [13]
    A look at the AMD Radeon HD 7970, the new single-GPU king - Digit
    Dec 22, 2011 · Another new feature, developed as direct competition to Intel's Quick Sync feature, is AMD's Video Codec Engine (VCE). This feature will also be ...
  14. [14]
    Radeon VCE Enabled For Trinity & Richland APUs - Phoronix
    Oct 13, 2015 · The Piledriver-based Trinity and Richland APUs have the VCE 1.0 video coding engine that supports accelerated encoding of H.264. VCE 1.0 was ...Missing: specifications Southern Islands
  15. [15]
    AMD Releases Open-Source VCE 1.0 Support - Phoronix
    May 12, 2015 · Christian König at AMD has worked out VCE support for the 1.0 hardware, including Trinity and Richland APUs. Tahiti, Pitcairn, Verde, Oland, and ...Missing: specifications Southern
  16. [16]
    OBS branch with AMD VCE support. | Page 72
    May 2, 2014 · Even if you manually enable them, the h264 encoder with VCE 1.0 cannot produce b frames. Lucil said: i noticed putting it to balanced and ...Missing: specifications IP DEM
  17. [17]
    Why You Need Hardware Acceleration to Fast Rip DVD Disc to Digital
    VCE 1.0 supports H.264 YUV420 (I & P frames), H.264 SVC Temporal Encode VCE, and Display Encode Mode (DEM). VCE 2.0 adds H.264 YUV444 (I-Frames), B-frames ...
  18. [18]
    AMD Radeon HD 7790 Review - TechSpot
    Rating 75% · Review by Steven WaltonMar 22, 2013 · The Radeon HD 7790 will be available in volume beginning April 2nd for as little as $150, which prices it smack bang between the 7770 and 7850.
  19. [19]
    https://hothardware.com/reviews/amd-kaveri-arrives-a87600-apu-review
  20. [20]
    AMD A10-7850K And A8-7600: Kaveri Gives Us A Taste Of HSA
    Jan 16, 2014 · AMD also claims to have improved its Video Codec Engine, adding I, P, and B frame support to the common H.264 YUV420 video format and I frames ...<|separator|>
  21. [21]
    AMD Kaveri APU Architecture Overview
    Jan 14, 2014 · VCE 2 in Kaveri includes all of those, but also adds B frames to the YUV420 and H.264 YUV444 (I Frames) for 60Hz Wireless Display.
  22. [22]
    [PDF] energy efficient graphics and multimedia in 28nm carrizo apu
    Aug 27, 2015 · 4 ENERGY EFFICIENT GRAPHICS AND MULTIMEDIA IN 28NM “CARRIZO” APU | HOT CHIPS 27 – AUGUST 2015. Die size: 250.04mm1. Transistor count: 3.1 ...
  23. [23]
    Question - Polaris vs Vega HEVC encoding | AnandTech Forums
    Jun 20, 2024 · I have been using hardware encoding (AMD VCE x265) on handbrake lately to quickly size down large 1080p VODs saved from Twitch to put on a 720p ...
  24. [24]
    SOS! AMD VCE 10 bit encoding, Vegas Pro 16? Need help.
    Nov 29, 2018 · When I set up AMD VCE in the options (see screenshot), then there is no possibility of saving in 10 bits and the final video is 8 bits only.Missing: documentation | Show results with:documentation
  25. [25]
    AMD Radeon RX Vega will arrive in 7 different models - TweakTown
    Mar 21, 2017 · ... (VCE 4.0), support for 3D via RadeonSI, power management, full display support using DC, and support for SR-IOV virtualization". The new ...
  26. [26]
    AMD Redefines the Enthusiast Gaming Experience with Radeon ...
    Jul 30, 2017 · The groundbreaking new features in the 'Vega' architecture, including the High Bandwith Cache Controller, Rapid Packed Math, Next-Generation ...
  27. [27]
    Accelerator Specifications - AMD
    Compare up to 4 products ; Instinct™ MI50 (32GB), Instinct, Instinct MI Series, Servers, 11/18/2018 ; Instinct™ MI50 (16GB), Instinct, Instinct MI Series, Servers ...Missing: VCE 4.1
  28. [28]
    PreProcessing and PreAnalysis · GPUOpen-LibrariesAndSDKs/AMF ...
    Feb 13, 2023 · AMF Video Encoder provides video pre-processing component (PP) and video pre-analysis component (PA) that are designed to improve video compression efficiency.Missing: VCE | Show results with:VCE
  29. [29]
    AMD Posts Linux Driver Patches For Video Core Next 5 "VCN 5.0"
    Feb 8, 2024 · It looks like next-generation RDNA4 graphics will feature a new iteration of the Video Core Next (VCN) for accelerated video encode/decode.Missing: key | Show results with:key
  30. [30]
    New Code Allows VCE 1.0 Video Acceleration To Work ... - Phoronix
    Oct 24, 2025 · New Code Allows VCE 1.0 Video Acceleration To Work On AMDGPU Driver For GCN 1.0 GPUs. Written by Michael Larabel in Radeon on 24 October 2025 ...
  31. [31]
    [PDF] The Polaris Architecture | - TechPowerUp
    As streaming platforms and services transition over to HEVC/H.265 to improve quality and data rates, the Polaris architecture has also been updated to include H ...
  32. [32]
    AMD 硬件加速编解码支持表 - 诺德美地流媒体系统 - NodeMedia
    AMD's hardware acceleration includes UVD for decoding, offloading video processing, and VCE for encoding, with VCN 1.0 adding VP9 decoding.Missing: complements | Show results with:complements
  33. [33]
    [PDF] AMD GRAPHICS CORES NEXT (GCN) ARCHITECTURE
    Using these new instructions, a Compute Unit can execute 64 SADs/cycle which translates into 256 operations per clock. These instructions are very powerful and ...
  34. [34]
    AMD Radeon RX 470 Specs - GPU Database - TechPowerUp
    The Radeon RX 470 is a mid-range graphics card by AMD, launched on August 4th, 2016. Built on the 14 nm process, and based on the Ellesmere graphics processor.ASUS RX 470 Mining · Asus rog strix rx 470 gaming · Msi rx 470 gaming xMissing: 7000, 7790,
  35. [35]
    Video Encoding Tested: AMD GPUs Still Lag Behind Nvidia, Intel ...
    Mar 9, 2023 · Here we're going to focus specifically on the video encoding performance and quality that you can expect from various generations of GPU.
  36. [36]
    A's Video Converter 7.0.0 - now supports VCE HEVC encoding on ...
    Dec 23, 2016 · This program is a video converter using AMD, Intel, NVIDIA and Microsoft Encoder, and it has the following features. Hardware H.264 encode using ...
  37. [37]
    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.Missing: VCE | Show results with:VCE
  38. [38]
    Socket FM2+ - CPU-World
    Socket FM2+ is a socket for the latest generation of AMD Accelerated Processing Units for desktop and All-in-One systems.
  39. [39]
    AMD refreshes 'Kaveri' lineup, touts great overclockability, up to ...
    May 29, 2015 · AMD “Kaveri” features second-generation video coding engine (VCE) and fourth-generation unified video decoder (VCE) units that ensure high ...
  40. [40]
    Sixth time lucky: AMD details the Carrizo APU - Ars Technica
    Jun 3, 2015 · All Carrizo chips are made up of 3.1 billion transistors (that's around 29 percent more transistors than Kaveri in approximately the same die ...
  41. [41]
    Can AMD RX570 into 1080p60fps hardware video encoding?
    Apr 24, 2019 · Using VAAPI hardware encoding in OBS with a RX 570 works just fine at 1080p 30 fps. Going above that to 1080p 60 fps results in 40-50% frames dropped by the ...<|separator|>
  42. [42]
    https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-22-6-1-WIN7.html
  43. [43]
    AMD Software: Adrenalin Edition 22.6.1 for Windows 7 Release Notes
    AMD Software: Adrenalin Edition 22.6.1 for Windows 7 is compatible with the following AMD Radeon products. AMD Radeon™ RX 5000, RX 6000 Series.
  44. [44]
    Supporting DXVA 2.0 in Media Foundation - Win32 apps
    Mar 3, 2021 · This topic describes how to support DirectX Video Acceleration (DXVA) 2.0 in a Media Foundation transform (MFT) using Microsoft Direct3D 9.Opening A Direct3d Device... · Finding A Decoder... · DecodingMissing: Engine VCE Catalyst Adrenalin
  45. [45]
    [PDF] The OpenMAX Integration Layer Specification - Khronos Registry
    Nov 7, 2011 · 1.1. Introduction. This document details the Application Programming Interface (API) for the OpenMAX. Integration Layer (IL).Missing: VCE | Show results with:VCE
  46. [46]
    OBS Studio 0.16.2 released with updated built in AMD AMF (VCE ...
    Sep 30, 2016 · Added an AMD H.264 encoder for AMD video cards on windows (also pre-configured settings available in simple output mode).Missing: XSplit Radeon Espresso<|separator|>
  47. [47]
    Release Notes (February 2025 Release) - XSplit Support
    AMD VCE Enhancements. XSplit can now detect and use multiple VCE-capable AMD GPUs. This update allows you to choose which GPU handles encoding in multi-GPU ...
  48. [48]
    CyberLink Optimizes Flagship Products for the New Second ...
    May 22, 2012 · In conjunction with AMD's VCE, MediaEspresso 6.5 provides quick output of video content for playback on new iPad, iPhone 4S, iPod and PSP ...
  49. [49]
    Radeon™ Software Adrenalin 2020 Edition 20.11.2 Release Notes
    Radeon Software Adrenalin 2020 Edition 20.11.2 is a notebook reference graphics driver with limited support for system vendor specific features.
  50. [50]
    The AMDGPU Additions For Linux 4.7 Are Enormous - Phoronix
    The AMDGPU Additions For Linux 4.7 Are Enormous. Written by Michael Larabel in Radeon on 11 May 2016 at 03:06 PM EDT. 32 Comments. RADEON. More AMDGPU DRM ...
  51. [51]
    Hardware/VAAPI - FFmpeg Wiki
    Jan 28, 2024 · The Mesa VAAPI driver uses the UVD (Unified Video Decoder) and VCE (Video Coding Engine) hardware found in all recent AMD graphics cards and APUs.Missing: kernel 4.7
  52. [52]
    [Studio][LINUX] AMD VCE Support on Linux via va-api + libx264
    Dec 13, 2016 · AMD VCE is working under linux using va-api and libx264. I can successfully encode videos using the command line like that:
  53. [53]
    [PDF] AMD Raven Ridge APU - Hot Chips
    Video Codec (VCN). ▫ Unified encode and decode engine. - Up to 4kp60 HEVC 10b decode. - Up to 4kp30 HEVC 8b encode. ▫ Low power video playback – 4kp30 @Vmin.Missing: introduction | Show results with:introduction
  54. [54]
    GPU and APU HW Features and Support - GitHub
    Mar 26, 2025 · AMD GPU multimedia hardware features. Codecs. All codecs are 4:2:0 AV1 encoder supported in one VCN instance only.
  55. [55]
    HWAccelIntro - FFmpeg Wiki
    Oct 28, 2024 · AMD UVD/VCE. AMD UVD is usable for decode via VDPAU and VAAPI in Mesa on Linux. VCE also has some initial support for encode via VAAPI, but ...