N100 HW Transcoding QSV not working

[technut8]

Hi, I have Jellyfin running Docker on OMV7 using Intel N100 CPU. I have recently amended my Docker Compose file to allow for hardware transcoding using the guides provided. When selecting VA-API as the transcoder and reducing the mbps stream on the client I can see that hardware transcoding is working as the CPU utilisation is around 30%

When switching to QSV the CPU is at 100%. I also tried to enable tone mapping using VA-API and the CPU goes to 100%. Please could someone assist as there must be some additional configuration needed that isn’t included in the guide.

Thanks

[TheDreadPirate]

What kernel is the system running? On the command line "sudo uname -a".

[technut8]

Hi thanks for getting back to me. Here is the kernel version:

Linux NAS 6.1.0-23-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) x86_64 GNU/Linux

I did read somewhere about having to use Promox kernel on OMV, or a newer kernel but am not 100% sure if it is relevant.

[TheDreadPirate]

You should be using Quick Sync instead of VAAPI. Can you share your docker compose file and also screenshots of Dashboard > Playback?

[technut8]

Hi here is what I have added to Docker Compose:

group_add:
- "105"
devices:
- /dev/dri/renderD128dev/dri/renderD128

I have ran some other commands which I can show outputs, it looks like the driver is installed:

docker exec -it d125fab04887 /usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose -init_hw_device vaapi=va -init_hw_device opencl@va

[AVHWDeviceContext ] Trying to use DRM render node for device 0.
[AVHWDeviceContext ] libva: VA-API version 1.22.0
[AVHWDeviceContext @ ] libva: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
[AVHWDeviceContext @ ] libva: Found init function __vaDriverInit_1_22
[AVHWDeviceContext @ ] libva: va_openDriver() returns 0
[AVHWDeviceContext @ ] Initialised VAAPI connection: version 1.22
[AVHWDeviceContext @ ] VAAPI driver: Intel iHD driver for Intel® Gen Graphics - 24.2.5 (12561f6).
[AVHWDeviceContext @ ] Driver not found in known nonstandard list, using standard behaviour.
[AVHWDeviceContext @ ] 0.0: Intel® OpenCL Graphics / Intel® UHD Graphics
[AVHWDeviceContext @ ] Intel QSV to OpenCL mapping function found (clCreateFromVA_APIMediaSurfaceINTEL).
[AVHWDeviceContext @ ] Intel QSV in OpenCL acquire function found (clEnqueueAcquireVA_APIMediaSurfacesINTEL).
[AVHWDeviceContext @ ] Intel QSV in OpenCL release function found (clEnqueueReleaseVA_APIMediaSurfacesINTEL).
Hyper fast Audio and Video encoder

Sometimes VAAPI seems to work other times it does not. QSV never works. I’ll also post outputs from UI.

[technut8]

For VAAPI I choose this in the playback UI and select /dev/dri/renderD128 as the device.

For QSV there are no other options to select the device.

I couldn’t see any option to post pictures unless there is a place to upload.

[TheDreadPirate]

With QSV the Intel driver will automatically select the device.

You have to use the full reply editor to attach pictures. Click "New Reply" at the top or bottom or "Preview Post".

[technut8]

Here are the settings in the Playback UI.

---

Thanks, here are the outputs. The only changes I’ve made are to add the render ID and iGPU device to the compose file.

I haven’t made any other changes.

[technut8]

Am wondering if it’s a permissions issue. The Jellyfin compose is not using root it has a specific user and group assigned to it which has limited privileges.

I did also disable a setting ‘Prefer OS native’ and the CPU load has come down to between 30-60% when transcoding a large 4k file.

[TheDreadPirate]

Can you share one of the ffmpeg logs associated with this issue.  I'm betting it is trying to transcode TO AV1, which your device does not support encoding to.  It can DECODE AV1, but not encode.

For the list of codecs, check ALL the boxes except VP8.  UNcheck "Allow encoding in AV1 format" since your N100 does not support encoding to that.  Check VPP tone mapping and tone mapping.  UNcheck both low power encoding boxes, unless you followed the documentation to set that up.  It isn't necessary, but may be worth the effort to get setup, if you have not done so already.  Documentation below.

https://jellyfin.org/docs/general/admini...e-on-linux