Content deleted Content added
mNo edit summary |
mNo edit summary |
||
Line 1:
'''Video Code Engine''' ('''VCE''', was earlier referred to as '''Video Coding Engine''',<ref name="amd-introducing"/> '''Video Compression Engine'''<ref>https://www.amd.com/en/media/43876/download</ref> or '''Video Codec Engine'''<ref>https://subscriptions.amd.com/newsletters/channelnews/pdf_guides/51884i_update_to_the_qrg_october2014.pdf</ref> in official AMD documentation) is [[Advanced Micro Devices|AMD's]] [[video encoding]] [[Application-specific integrated circuit|ASIC]] implementing the [[video codec]] [[H.264/MPEG-4 AVC]]. Since 2012 it is integrated into all of their [[List of AMD graphics processing units|GPUs]] and [[AMD Accelerated Processing Unit|APUs]] except Oland.
Video Coding Engine was introduced with the [[Radeon HD 7000 Series|Radeon HD 7900]] on {{date|2011-12-22}}.<ref>{{cite web |url=https://www.amd.com/Documents/UVD3_whitepaper.pdf |title=White Paper AMD UnifiedVideoDecoder (UVD) |date=2012-06-15 |accessdate=2017-05-20}}</ref><ref>{{cite web |url=
As of [[Ryzen#APUs: Raven Ridge|Raven Ridge]] VCE has been succeeded by [[Video Core Next|VCN]].
Line 11:
The handling of video data involves computation of [[data compression]] algorithms and possibly of [[video processing]] algorithms. As the template [[Template:Compression methods|Compression methods]] shows, lossy video compression algorithms involve the steps: [[Motion compensation|Motion estimation]] (ME), [[Discrete cosine transform]] (DCT), and [[entropy encoding]] (EC).
AMD Video Code Engine (VCE) is a full hardware implementation of the video codec H.264/MPEG-4 AVC. The ASIC is capable of delivering 1080p at 60 frames/sec. Because its entropy encoding block is also a separately accessible Video Codec Engine, it can be operated in two modes: full-fixed mode and hybrid mode.<ref name="AnandTech">{{cite web |url=
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 ([[Graphics Core Next|GCN]]) of the GPU, so the computing scales with the number of available compute units (CUs).
Line 57:
==={{Anchor|3.0}}VCE 3.0===
Video Code Engine 3.0 (VCE 3.0) technology features a new high-quality video scaling and [[High Efficiency Video Coding]] (HEVC/H.265).<ref>
It, together with [[Unified Video Decoder|UVD]] 6.0, can be found on 3rd generation of Graphics Core Next (GCN3) with "Tonga", "Fiji", "Iceland", and "Carrizo" (VCE 3.1) based graphics controller hardware, which is now used [[AMD Radeon Rx 300 Series]] (Pirate Islands GPU family) and VCE 3.4 by actual [[AMD Radeon Rx 400 Series]] and [[AMD Radeon 500 Series]] (both Polaris GPU family).
Line 70:
====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>{{
===Feature overview===
Line 81:
==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 |date=2016-12-08 |accessdate=2017-08-15}}</ref> but added it in December 2018
AMD's [[proprietary software|proprietary]] device driver [[AMD Catalyst]] is available for multiple operating systems and support for VCE has been added to it{{citation needed|date=June 2014}}. Additionally, a [[free and open-source graphics device driver#ATI/AMD|free device driver]] is available. This driver also supports the VCE hardware.
Line 90:
{{Main|AMD Catalyst|Free and open-source graphics device driver#ATI/AMD|l1=AMD Catalyst for Linux|l2=Free Radeon driver}}
* Initial VCE support has been added on {{date|2014-02-04}} by Christian König of AMD to the free radeon driver.<ref>{{cite mailing list |url=
* [[Gallium3D|Gallium3D state tracker]] for [[OpenMAX]] was added {{date|2013-10-24}} to [[Mesa 3D]].<ref>{{cite mailing list |url=
* The [[free and open-source graphics device driver#ATI/AMD|free and open-source Radeon driver]] has been adapted to using OpenMAX with the [[GStreamer]] OpenMAX (gst-omx) support for exposing the VCE video encode engine.<ref>{{cite web |url=https://www.phoronix.com/scan.php?page=news_item&px=MTU5MTc |title=AMD Open-Sources VCE Video Encode Engine Code |date=2014-02-04 |work=[[Phoronix]] |accessdate=2017-05-20}}</ref>
* AMD employee Leo Liu implemented [[H.264/MPEG-4 AVC#Levels|h264 level support]] into the Mesa 3D state tracker.<ref>{{cite web |url=
===Windows===
The software "MediaShow Espresso Video Transcoding" seems to utilize VCE and UVD to the fullest extent possible.<ref>{{cite web |url=
[[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.is/20140722041719/http://www.splitmedialabs.com/news/109-splitmedialabs-releases-xsplit-gamecaster-and-updates-xsplit-broadcaster-13 |url-status=dead |archive-date=2014-07-22 |title=XSplit Broadcaster 1.3 maintenance update includes mainly performance enhancements and maintenance fixes including such noteworthy features such as support for AMD's VCE H.264 hardware encoder}}</ref>
| |||