Content deleted Content added
No edit summary |
Rescuing 2 sources and tagging 1 as dead.) #IABot (v2.0.9.5 |
||
(37 intermediate revisions by 26 users not shown) | |||
Line 1:
{{Short description|AMD hardware accelerator for encoding MP4 H.264 videos, built into AMD GPU's}}
'''Video Code Engine''' ('''VCE''', was earlier referred to as '''Video Coding Engine''',<ref name="amd-introducing"/> '''Video Compression Engine'''<ref>{{cite web|url=https://www.amd.com/en/media/43876/download|title=Product brief|website=amd.com}}</ref> or '''Video Codec Engine'''<ref>{{cite web|url=https://subscriptions.amd.com/newsletters/channelnews/pdf_guides/51884i_update_to_the_qrg_october2014.pdf |title=Updates|website=amd.com}}</ref> in official AMD documentation) is [[Advanced Micro Devices|AMD's]] [[video encoding]] [[
As of [[AMD
==Overview==
Line 11:
[[File:AMD VCE hybrid mode.svg|thumb|The entropy encoding block of the VCE ASIC is also separately accessible, enabling ''"hybrid mode"''. In ''"hybrid mode"'' most of the computation is done by the 3D engine of the GPU. Using [[AMD APP SDK|AMD's Accelerated Parallel Programming SDK]] and [[OpenCL]] developers can create hybrid encoders that pair custom motion estimation, inverse discrete cosine transform and motion compensation with the hardware entropy encoding to achieve faster than real-time encoding.]]
The handling of video data involves computation of [[data compression]] algorithms and possibly of [[video processing]] algorithms. As the template [[Template:Compression methods|
AMD Video Code Engine (VCE) is a full hardware implementation of the video codec H.264/MPEG-4 AVC.
By employing [[AMD APP SDK]], available for Linux and Microsoft Windows, developers can create hybrid encoders that pair custom motion estimation, inverse discrete cosine transform and motion compensation with the hardware entropy encoding to achieve faster than real-time encoding. In hybrid mode, only the entropy encoding block of the VCE unit is used, while the remaining computation is offloaded to the 3D engine
==={{Anchor|1.0|DEM}}VCE 1.0===
It can be found on:
Line 56:
** Mobile Radeon R9 M385, M385X
** Mobile Radeon R9 M470, M470X
** FirePro
** Mobile FirePro M6100, W6150M, W6170M
==={{Anchor|3.0}}VCE 3.0===
Video Code Engine 3.0 (VCE 3.0) technology features a new high-quality video scaling and - since version 3.4 - [[High Efficiency Video Coding]] (HEVC/H.265).<ref>{{cite web | title=Mailing Lists | website=lists.freedesktop.org | date=4 June 2015 | url=https://lists.freedesktop.org/archives/dri-devel/2015-June/084083.html
It, together with [[Unified Video Decoder|UVD]] 6.0, can be found on 3rd generation of Graphics Core Next (GCN3) with "Tonga"
* Tonga: Radeon R9 285, 380, 380X; Mobile Radeon R9 M390X, M395, M395X, M485X
* Tonga XT: FirePro W7100, S7100X, S7150, S7150 X2
* Fiji: Radeon R9 Fury, Fury X, Nano; Radeon Pro Duo (2016); FirePro S9300, W7170M; Instinct MI8
* Polaris: RX 460, 470, 480; RX 550, 560, 570, 580; Radeon Pro Duo (2017)
AMD's [[List_of_AMD_accelerated_processing_units#"Carrizo"_(2016)|Carrizo]] platform features VCE 3.1, retaining the same capabilities as the VCE found in "Fiji" and "Tonga".<ref>{{cite web | title=AMDGPU (vi.c) | url=https://github.com/ROCm/ROCK-Kernel-Driver/blob/master/drivers/gpu/drm/amd/amdgpu/vi.c#L282-L289|website=GitHub}}</ref>
[[List_of_AMD_accelerated_processing_unit_microprocessors#"Stoney_Ridge"_(2016)|Stoney Ridge]] features a cut down version of VCE 3.4 without HEVC/H.265 encoding and is accompanied by a UVD 6.2 engine.<ref>{{cite web | title=AMDGPU (vi.c) | url=https://github.com/ROCm/ROCK-Kernel-Driver/blob/55cf32d54948f98f1cc6d6b3fdc05b32fab9b3f0/drivers/gpu/drm/amd/amdgpu/vi.c#L2153-L2169|website=GitHub}}</ref>
VCE 3.0 removes support for H.264 B-frames.<ref>{{cite web |title=Video Encode API: BFrames not supported on RX 4xx? · Issue #8 · GPUOpen-LibrariesAndSDKs/AMF |url=https://github.com/GPUOpen-LibrariesAndSDKs/AMF/issues/8 |website=GitHub |language=en}}</ref>
==={{Anchor|4.0}}VCE 4.0===
The Video Code Engine 4.0 encoder and UVD 7.0 decoder are included in the Vega-based GPUs.<ref name=
====VCE 4.1====
AMD's Vega20 GPU, present in the Instinct Mi50, Instinct Mi60 and Radeon VII cards, include VCE 4.1 and two UVD 7.2 instances.<ref>{{cite web|url=https://lists.freedesktop.org/archives/amd-gfx/2018-May/022291.html|title=[PATCH 50/57] drm/amdgpu/vg20:Enable the 2nd instance IRQ for uvd 7.2|last=Deucher|first=Alex|date=15 May 2018|
===Feature overview===
Line 83 ⟶ 90:
==Operating system support==
The VCE SIP core needs to be supported by the [[device driver]]. The device driver provides one or multiple [[Application programming interface|interfaces]], e. g. [[OpenMAX IL]]. One of these interfaces is then used by end-user software, like [[GStreamer]] or [[HandBrake]] (HandBrake rejected VCE support in December 2016,<ref>{{cite web |url=https://github.com/HandBrake/HandBrake/pull/88 |title=HandBrake rejected VCE pull request |website=[[GitHub]] |date=2016-12-08 |
AMD's [[proprietary software|proprietary]] device driver [[AMD Catalyst]] is available for multiple operating systems and support for VCE
===Linux===
Line 92 ⟶ 99:
{{Main|AMD Catalyst|Free and open-source graphics device driver#ATI/AMD|l1=AMD Catalyst for Linux|l2=Free Radeon driver}}
* Initial VCE support
* [[Gallium3D|Gallium3D state tracker]] for [[OpenMAX]] was added
* The [[free and open-source graphics device driver#ATI/AMD|free and open-source Radeon driver]]
* AMD employee Leo Liu implemented [[H.264/MPEG-4 AVC#Levels|h264 level support]] into the Mesa 3D state tracker.<ref>{{cite web |url=https://cgit.freedesktop.org/mesa/mesa/commit/?id=e2db7c10d63399b6a34ba5fa56ce9e1eac402416 |title=st/omx/enc: implement h264 level support |date=2014-06-12 |
===Windows===
The software "MediaShow Espresso Video Transcoding" seems to utilize VCE and UVD to the fullest extent possible.<ref>{{cite web |url=https://www.guru3d.com/articles_pages/amd_a8_7600_apu_review,13.html |title=MediaShow Espresso Video Transcoding Benchmark |date=2014-01-14 |
[[XSplit Broadcaster]] supports VCE from version 1.3.<ref>{{cite web |url=http://www.splitmedialabs.com/news/109-splitmedialabs-releases-xsplit-gamecaster-and-updates-xsplit-broadcaster-13 |archive-url=https://archive.
[[Open Broadcaster Software]] (OBS Studio) supports VCE for recording and streaming. The original Open Broadcaster Software (OBS) requires a fork build in order to enable VCE.<ref>{{cite web |url=https://obsproject.com/forum/threads/obs-branch-with-amd-vce-support.13996/ |title=OBS branch with AMD VCE support |date=May 2, 2014 |
[[AMD Radeon Software Crimson|AMD Radeon Software]] supports VCE with built in game capture ("Radeon ReLive") and use AMD AMF/VCE on APU or Radeon Graphics card to reduce FPS drop when capturing game or video content.<ref>{{cite web |url=http://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-16.12.1-Release-Notes.aspx |title=Radeon Software Crimson ReLive Edition 16.12.1 Release Notes |
[[HandBrake]] added Video Coding Engine support in version 1.2.0 in December 2018.<ref name="Handbrake"/>
Line 111 ⟶ 118:
{{Main|Video Core Next}}
The VCE was succeeded by AMD Video Core Next in the Raven Ridge series of APUs released in October 2017. The VCN combines both encode (VCE) and decode (UVD).<ref>{{cite news|last1=Larabel|first1=Michael|title=Radeon VCN Encode Support Lands In Mesa 17.4 Git|url=https://www.phoronix.com/scan.php?page=news_item&px=Radeon-VCN-Encode-Lands|
==See also==
=== Video hardware technologies ===
==== AMD ====
* [[Video Core Next]] - [[Advanced Micro Devices|AMD]]
* Video Coding Engine - [[Advanced Micro Devices|AMD]]
* [[Unified Video Decoder]] - [[Advanced Micro Devices|AMD]]
* [[Video Shader]] - [[ATI Technologies|ATI]]
==== Others ====
* [[Intel Quick Sync Video]] – Intel's equivalent SIP core
* [[Nvidia NVENC]] – Nvidia's equivalent SIP core
*[[Qualcomm Hexagon]] - Qualcomm's equivalent SIP core
==References==
Line 123 ⟶ 143:
[[Category:Video acceleration]]
[[Category:
[[Category:Video compression and decompression ASIC]]
|