SOLVED: Hardware acceleration on Unraid issues

[bitmap]

You can also find the transcode logs in the UI via Dashboard > Logs.

Just FYI, group add doesn't work the way you'd expect (or at all, depending on the version of compose you're using) with docker compose. What you need to do is ensure that the UID you're using is added to the video/render groups that own the devices (renderD128 and card0). I come at this from Ubuntu/Debian world and I don't know what the underlying flavor of Linux is with Unraid, nor what kind of abstraction is done to isolate the user from the host, so my info might be a little different.

If you can exec into the container, you can easily test if access to the device is an issue without going through the motions of playing a video, checking the logs, repeat ad nauseam...

Code:

docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -init_hw_device qsv=qs:/dev/dri/renderD128

And you should see an output similar to this (plus all the other crap ffmpeg spits out if you don't put the muzzle on):

Code:

libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0

Or you'll see an error. Errors mean it's not configured properly.