Transcoding issue in v10.8.12

[Kevin1109]

Hi, I'm having issues as well with a Docker setup, and at this point I'm at a complete loss of what's exactly going on.

Any time Jellyfin has to transcode, the entire NAS hangs and the only way to solve that is by stopping the jellyfin container. Streaming works perfectly fine without the transcode, but it just seems like it doesn't want to use hardware acceleration no matter what I try.

Here is the ffmpeg log: https://privatebin.net/?eb1210cc55220544...m3haM1gr6R

Judging from the Jellyfin log it seems to correctly identify everything it has to use:
[2025-08-23 22:38:41.953 +02:00] [INF] [1] MediaBrowser.MediaEncoding.Encoder.MediaEncoder: VAAPI device "/dev/dri/renderD128" is Intel GPU (iHD)
[2025-08-23 22:38:41.954 +02:00] [INF] [1] MediaBrowser.MediaEncoding.Encoder.MediaEncoder: VAAPI device "/dev/dri/renderD128" supports Vulkan DRM modifier
[2025-08-23 22:38:41.954 +02:00] [INF] [1] MediaBrowser.MediaEncoding.Encoder.MediaEncoder: VAAPI device "/dev/dri/renderD128" supports Vulkan DRM interop

Is there anything I'm missing? I'm running 10.10.6.

[bitmap]

I would always recommend making your own topic -- not resurrecting old topics. From your ffmpeg log, your hardware is not powerful enough to transcode. It's running at fractions of a frame per second, which is not sufficient to keep up with the running rate of 24+ FPS of most media.

[Kevin1109]

I would always recommend making your own topic -- not resurrecting old topics. From your ffmpeg log, your hardware is not powerful enough to transcode. It's running at fractions of a frame per second, which is not sufficient to keep up with the running rate of 24+ FPS of most media.

Yea, apologies. I saw posts from last week and thought it was a good idea to hang on. Turns out it was an ancient topic.

Is this actually the iGPU itself throwing those awful framerates? I know it's awful and never had the illusion that 4k to 4k was ever going to work, but this just feels way too low to be hardware encoding.

[bitmap]

Code:

/usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 200M -probesize 1G -f matroska -init_hw_device vaapi=va:/dev/dri/renderD128,driver=iHD -hwaccel vaapi -hwaccel_output_format vaapi -noautorotate -i file:"/media/films/TEST/TEST.mkv"

Yes, it's using VA-API hardware acceleration. I would agree with you that this is unacceptable. What is the processor in your NAS? Most of the time they're underpowered and although you may be able to use VA-API, it's not cutting it. If new enough, you may be able to upgrade to QSV for better results, but it seems a bit off that your performance is so piss poor.

[Kevin1109]

Code:

/usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 200M -probesize 1G -f matroska -init_hw_device vaapi=va:/dev/dri/renderD128,driver=iHD -hwaccel vaapi -hwaccel_output_format vaapi -noautorotate -i file:"/media/films/TEST/TEST.mkv"

Yes, it's using VA-API hardware acceleration. I would agree with you that this is unacceptable. What is the processor in your NAS? Most of the time they're underpowered and although you may be able to use VA-API, it's not cutting it. If new enough, you may be able to upgrade to QSV for better results, but it seems a bit off that your performance is so piss poor.

It's an Intel Celeron J4125. QSV wasn't much better, I switched to VA-API to test that one. Judging from this thread it should at the very least work at all. I don't care that much about performance, for that I have to buy something much better, but it just has to be better than what it is right now.