Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| hardware:en-decoder [2020/03/29 12:07] – derpeter | hardware:en-decoder [2021/10/15 10:43] (current) – derpeter | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| = Video Acceleration | = Video Acceleration | ||
| - | |||
|   * https:// |   * https:// | ||
| + |   * https:// | ||
| + |   * https:// | ||
| = APIs | = APIs | ||
| Line 11: | Line 12: | ||
|   * https:// |   * https:// | ||
| - | The tool '' | + | The tool '' | 
| + | |||
| + | Vainfo can be forced to use a specific render device | ||
| + | < | ||
| + | vainfo --display drm --device / | ||
| + | </ | ||
| + | |||
| + | Also the driver to use can be choosen | ||
| + | < | ||
| + | LIBVA_DRIVER_NAME=iHD | ||
| + | </ | ||
| + | |||
| + | Output on a kabylake microarchitecture based CPU will e.g. look like this: | ||
| < | < | ||
| Line 73: | Line 86: | ||
|   * https:// |   * https:// | ||
|   * https:// |   * https:// | ||
| + |   * https:// | ||
| + |   * https:// | ||
| + | |||
| + | 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:// | ||
| + | |||
| 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 104: | Line 127: | ||
| To see the load of your GPU use nvidia' | To see the load of your GPU use nvidia' | ||
| < | < | ||
| - | == AMD | + | == AMD / ATI | 
| === Radeon | === Radeon | ||
| - | The AMD stand alone GPUs provide also video en/ decoder  | + | The AMD stand alone GPUs provide also video en/ decoder  | 
| + | The first AMD/ATI GPU with video accelerator was R600 architecture from 2007. AMD developed different accelerator suites over time: | ||
| - | E.g. a Radion  | + | * https:// | 
| + | * https:// | ||
| + | * https:// | ||
| + | |||
| + | which provide different encoding and decoding capabilities as well as different offloading features. | ||
| + | |||
| + | E.g. a Radeon  | ||
| < | < | ||
| Line 137: | Line 167: | ||
|       VAProfileNone  |       VAProfileNone  | ||
| </ | </ | ||
| + | |||
| + | while gstreamer seems not support the usage jet. | ||
| == Broadcom | == Broadcom | ||
| === Christal HD | === Christal HD | ||
| Line 171: | Line 203: | ||
| < | < | ||
| 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 | ||
| + | |||
| + | < | ||
| + | LIBVA_DRIVER_NAME=iHD DRI_PRIME=/ | ||
| + | </ | ||
| + | where the first one is in most cases enough. | ||
| + | |||
| + | |||
| The output will look like: | The output will look like: | ||
| Line 202: | Line 242: | ||
| </ | </ | ||
| + |   * https:// | ||
|   * https:// |   * https:// | ||
|   * https:// |   * https:// | ||