Video Core Next
AMD hardware video codec, built into AMD GPUs and APUs
Video Core Next is AMD's brand for its dedicated video encoding and decoding hardware core. It is a family of hardware accelerator designs for encoding and decoding video, and is built into AMD's GPUs and APUs since AMD Raven Ridge, released January 2018.
01Background
Video Core Next is AMD's successor to both the Unified Video Decoder and Video Coding Engine designs, which are hardware accelerators for video decoding and encoding, respectively. It can be used to decode, encode and transcode ("sync") video streams, for example, a DVD or Blu-ray Disc to a format appropriate to, for example, a smartphone. Unlike video encoding on a CPU or a general-purpose GPU, Video Core Next is a dedicated hardware core on the processor die. This application-specific integrated circuit (ASIC) allows for more power-efficient video processing.
02Feature set
All versions of VCN support H.264/MPEG-4 AVC Encode/Decode, HEVC (H.265) Encode/Decode, and VP9 Decode. 10-bit color depth in the P010 format is supported. VCN 1.0 supports up to 4K resolution. VCN 2.0 and beyond supports up to 8K. Support for H.264 and H.265 Encode methods differ among generations (see below). VC-1 Decode is not supported since VCN 3.0.33.
VCN 2.0 was introduced with RDNA 1 and the Renoir APU. The feature set remains the same as VCN 1.0.
VCN 3.0 was introduced with RDNA 2 and is implemented in the Playstation 5 and Xbox Series S/X. VCN 3.0 implements H.264 B-frames, which was present in Video Coding Engine 2.0 but taken out with VCE 3.0, and AV1 Decoding.
VCN 4.0 was introduced with RDNA 3 and adds AV1 encode. H.264 quality is higher with VCN 4.0 (as part of RDNA 3) compared to previous generations, but still somewhat lags behind Intel and Nvidia hardware codecs - though many critics believed it was already good enough to be utilized more often.
VCN 5.0 was introduced with RDNA 4 and enhances overall encoding further, finally closing the gap between AMD and Intel/Nvidia hardware encoding. Higher end RDNA 4 GPUs also have 2 VCN units instead of 1, like equivalent Ada Lovelace/Blackwell GPUs, to improve video encoding/decoding latency and performance.
There is no support for encoding or decoding in YUV422 and YUV444 in H.264 and H.265.
| VCN Generation |
GPU code name | JPEG | VC-1 / WMV 9 |
H.262 (MPEG-2) |
H.264 (MPEG-4 AVC) |
H.265 (HEVC) |
VP9 | AV1 | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Decode | Decode | Decode | Decode | Encode | Decode | Encode | Decode | Decode | Encode | |||||
| B-frame | Pre-analysis | Resolution, color depth |
Chroma | Resolution, color depth | ||||||||||
| VCN 1.0 | Raven, Picasso | ? | 4K @ 10b | 4:2:0 | 4K @ 10b | |||||||||
| VCN 2.0 | Navi 1x | 4K @ 8b | 4K @ 10b | |||||||||||
| VCN 2.2 | Renoir, Lucienne, Cezanne, Barcelo | |||||||||||||
| VCN 2.5 | Arcturus | |||||||||||||
| VCN 2.6 | Aldebaran | |||||||||||||
| VCN 3.0 | Navi 21, Navi 22, Navi 23 | 8K @ 10b | ||||||||||||
| VCN 3.0.33 | Navi 24 | |||||||||||||
| VCN 3.1.0 | Van Gogh | 4K @ 8b | 4:2:0 | 8K @ 10b | ||||||||||
| VCN 3.1.1 | Rembrandt, Mendocino | |||||||||||||
| VCN 3.1.2 | Raphael, Dragon Range | |||||||||||||
| VCN 4.0 | Navi 3x, Phoenix | 8K @ 10b | ||||||||||||
| VCN 5.0 | Navi 4x | |||||||||||||
03Quality
Early versions of AMD VCN had lower overall quality (VMAF) compared to offerings from Intel and Nvidia. B-frame support narrowed the gap, but did not eliminate it; further improvements, including pre-analysis, resulted in nearly equivalent performance to competitors at the release of VCN 4.0.
Despite a lack of B-frame support, H.265 provides better quality (VMAF) and near-identical speed for the same bitrate compared to H.264 on VCN 2.0, 3.0, and 4.0.
Sources and credits
This article is adapted from the Wikipedia article “Video Core Next”, written by its contributors and licensed under CC BY-SA 4.0. Fathomly has changed the layout, removed citation markers, navigation and maintenance notices, and adjusted punctuation. This adapted version is shared under the same license. For references, see the original article.
Fathomly is not affiliated with or endorsed by the Wikimedia Foundation. Spotted a problem? Tell us.