hardware:en-decoder

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
hardware:en-decoder [2020/03/29 12:10] – [Radeon] derpeterhardware:en-decoder [2021/10/15 10:43] (current) – derpeter
Line 1: Line 1:
 = Video Acceleration = Video Acceleration
- 
   * https://en.wikipedia.org/wiki/Category:Video_acceleration   * https://en.wikipedia.org/wiki/Category:Video_acceleration
 +  * https://en.wikipedia.org/wiki/Category:Video_compression_and_decompression_ASIC
 +  * https://wiki.archlinux.org/index.php/Hardware_video_acceleration
  
 = APIs = APIs
Line 11: Line 12:
   * https://freedesktop.org/wiki/Software/vaapi/   * https://freedesktop.org/wiki/Software/vaapi/
  
-The tool ''vainfo'' from the libva-utils repository ( https://github.com/intel/libva-utils/tree/master/vainfo ) can give you an overview what is supported on you system. The results differ depending on lib, cpu and driver version. vainfo is also packaged in many linux distributions. Output on a kabylake microarchitecture based CPU will e.g. look like this:+The tool ''vainfo'' from the libva-utils repository ( https://github.com/intel/libva-utils/tree/master/vainfo ) can give you an overview what is supported on you system. The results differ depending on lib, cpu and driver version. vainfo is also packaged in many linux. distributions.  
 + 
 +Vainfo can be forced to use a specific render device  
 +<code> 
 +vainfo --display drm --device /dev/dri/renderD129 
 +</code> 
 + 
 +Also the driver to use can be choosen 
 +<code> 
 +LIBVA_DRIVER_NAME=iHD 
 +</code> 
 + 
 +Output on a kabylake microarchitecture based CPU will e.g. look like this:
  
 <code> <code>
Line 73: Line 86:
   * https://en.wikichip.org/wiki/intel/microarchitectures/gen9#Hardware_Accelerated_Video   * https://en.wikichip.org/wiki/intel/microarchitectures/gen9#Hardware_Accelerated_Video
   * https://en.wikichip.org/wiki/intel/microarchitectures/gen9.5#Hardware_Accelerated_Video   * https://en.wikichip.org/wiki/intel/microarchitectures/gen9.5#Hardware_Accelerated_Video
 +  * https://wiki.gentoo.org/wiki/Intel#Feature_support
 +  * https://wiki.archlinux.org/index.php/intel_graphics
 +
 +There are two userspace drivers availiable to enable usage of the igpu with vaapi. 
 +
 +* intel-media-driver (Gen8+ / Broadwell+)
 +* i965-va-driver (up to Gen7)
 +
 +Gen9+ / Skylake to Gen11 need GuC/HuC firmware to be loaded to enable all features (https://github.com/intel/media-driver#known-issues-and-limitations)
 +
  
 The ffmpeg wiki has a clear list of the capabilities each Intel GPU generation offers: The ffmpeg wiki has a clear list of the capabilities each Intel GPU generation offers:
Line 106: Line 129:
 == AMD / ATI == AMD / ATI
 === Radeon === Radeon
-The AMD stand alone GPUs provide also video en/ decoder capabilties. With recent Linux Kernels e.g. the NAVI Gpus (Radeon GT 5xxx) can be used without binary drivers. +The AMD stand alone GPUs provide also video en/ decoder capabilities. With recent Linux Kernels e.g. the NAVI Gpus (Radeon GT 5xxx) can be used without binary drivers. 
-The first AMD/ATI GPU with video accellerator was R600 architecture from 2007. AMD developed different accelerator suites over time. +The first AMD/ATI GPU with video accelerator was R600 architecture from 2007. AMD developed different accelerator suites over time:
  
-E.g. a Radion gt 5500 XT provides the following encoders through libva+* https://en.wikipedia.org/wiki/Unified_Video_Decoder 
 +* https://en.wikipedia.org/wiki/Video_Coding_Engine 
 +* https://en.wikipedia.org/wiki/Video_Core_Next 
 +  
 +which provide different encoding and decoding capabilities as well as different offloading features. 
 + 
 +E.g. a Radeon gt 5500 XT provides the following encoders through libva with opensource drivers on 5.4.0 Kernel
  
 <code> <code>
Line 138: Line 167:
       VAProfileNone                   : VAEntrypointVideoProc       VAProfileNone                   : VAEntrypointVideoProc
 </code> </code>
 +
 +while gstreamer seems not support the usage jet.
 == Broadcom == Broadcom
 === Christal HD === Christal HD
Line 172: Line 203:
 <code>sudo gst-inspect-1.0 vaapi </code> <code>sudo gst-inspect-1.0 vaapi </code>
 gstreamer1.0-vaapi needs to be installed for this to work. Replace vaapi with the API you want to use e.g. omx. gstreamer1.0-vaapi needs to be installed for this to work. Replace vaapi with the API you want to use e.g. omx.
 +There are some envirement variables that can be set to change gstreamers behavior / driver usage
 +
 +<code>
 +LIBVA_DRIVER_NAME=iHD DRI_PRIME=/dev/dri/renderD128 GST_VAAPI_ALL_DRIVERS=1
 +</code>
 +where the first one is in most cases enough.
 +
 +
 The output will look like: The output will look like:
  
Line 203: Line 242:
 </code> </code>
  
 +  * https://blogs.igalia.com/vjaquez/2018/03/28/gstreamer-va-api-troubleshooting/ <= trouble shooting guide
   * https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer-vaapi-plugins/html/ch01.html   * https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gstreamer-vaapi-plugins/html/ch01.html
   * https://gstreamer.freedesktop.org/documentation/tutorials/playback/hardware-accelerated-video-decoding.html   * https://gstreamer.freedesktop.org/documentation/tutorials/playback/hardware-accelerated-video-decoding.html
  • hardware/en-decoder.1585476626.txt.gz
  • Last modified: 2020/03/29 12:10
  • by derpeter