Got my Intel Arc A380 (DG2) to work with Booshs qsv on Tdarr (bare metal Ubuntu 22.04)!

This page summarizes the projects mentioned and recommended in the original post on /r/Tdarr

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • Have Ubuntu 22.04 and an Arc (Other Distributions may work too idk, also 12th, 13th gen Intel) Orient yourself by following this tutorial. Do not use the Mainline Kernel use this one. For Firmware install this one additionally. Mind the altered firmware update path because of this and put the Intel Firmware here /opt/drivers-linux-firmware/i915.

  • Have Ubuntu 22.04 and an Arc (Other Distributions may work too idk, also 12th, 13th gen Intel) Orient yourself by following this tutorial. Do not use the Mainline Kernel use this one. For Firmware install this one additionally. Mind the altered firmware update path because of this and put the Intel Firmware here /opt/drivers-linux-firmware/i915.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
  • media-driver

    Intel Graphics Media Driver to support hardware decode, encode and video processing.

  • Do all the compiling. You will need to install a lot of dependency, compilers and probably even have to build compilers if you've never done this before. Follow the respective readmes. Do Media Driver first with cmake ../media-driver -DENABLE\_PRODUCTION\_KMD=ON because of this. Then do oneVPL and oneVPL-GPU. Then FFmpeg, which has to be configured with:

  • libvpl

    IntelĀ® Video Processing Library (IntelĀ® VPL) dispatcher, tools, and examples

  • Do all the compiling. You will need to install a lot of dependency, compilers and probably even have to build compilers if you've never done this before. Follow the respective readmes. Do Media Driver first with cmake ../media-driver -DENABLE\_PRODUCTION\_KMD=ON because of this. Then do oneVPL and oneVPL-GPU. Then FFmpeg, which has to be configured with:

  • vpl-gpu-rt

  • Do all the compiling. You will need to install a lot of dependency, compilers and probably even have to build compilers if you've never done this before. Follow the respective readmes. Do Media Driver first with cmake ../media-driver -DENABLE\_PRODUCTION\_KMD=ON because of this. Then do oneVPL and oneVPL-GPU. Then FFmpeg, which has to be configured with:

  • FFmpeg

    Mirror of https://git.ffmpeg.org/ffmpeg.git

  • Do all the compiling. You will need to install a lot of dependency, compilers and probably even have to build compilers if you've never done this before. Follow the respective readmes. Do Media Driver first with cmake ../media-driver -DENABLE\_PRODUCTION\_KMD=ON because of this. Then do oneVPL and oneVPL-GPU. Then FFmpeg, which has to be configured with:

  • HandBrake

    HandBrake's main development repository

  • If it doesn't check if you exported the right path to the driver. Also check if it's showing the correct gpu, if you have a multi-gpu scenario. With two Intel gpus is isn't obvious as they use the same driver. You'll have to find out the how yourself, because it may even depend if you're using ssh or sitting i nfront of the monitor. 2. Then do a FFmpeg test run (if multigpu situation look at initial post) with a h264 to h265 conversion. Provide the files yourself, use this command: ffmpeg -hwaccel qsv -qsv_device /dev/dri/renderD129 -c:v h264_qsv -i input.mkv -map 0 -b:v 2500k -minrate 500k -maxrate 5000k -c:v hevc_qsv -c:a copy -c:s copy output.mkv should clock in at a nice 630 fps. If not you probably got reBAR (see here) deactivated. If it doesn't do anything/errors out and vainfo is good: check your pathing, could be that it's D128 and not D129. Could also be that it's not using your compiled FFmpeg as standard. You'll have to explore/modify things yourself in that case. 3. If Step 2 works, modify your baremetal Tdarr Node and Server config to use your compiled FFmpeg like this (Mind the path on your specific system). I also build Handbrake from source and added the path to the cli in the config (depends probably on if it's already installed on your system. I also needed this sudo apt install tesseract-ocr libtesseract-dev because Tdarr didn't seem to be to happy that I was missing libtesseract4. 4. If you only have one GPU and use Boosh-Transcode using QSV GPU & FFMPEG do everything as usual, but make sure you set enable_10bit: false. If it's true the transcode will throw errors. Read initial post for the what. I'll update when I know the why. (If you should have a multi-gpu situation (another IGPU perhaps: read initial post.)

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts