Transcoding issue in v10.8.12

[vitalessandro]

Hi all,

I'm running Jellyfin on a Synology in docker. Getting hardware transcoding to work with Synology's proprietary Linux distro is a bit tricky, but had worked fine up until now. After upgrading to version 10.8.12 however, I get errors trying to play most files that need transcoding (using the web player e.g). The error message is along the lines of 'Cannot play back file, no compatible format found / server isn't sending one'.

The transcoding logs show the following (right at the end after the ffmpeg configuration):
[AVHWDeviceContext @ 0x558ef899c440] Failed to get number of OpenCL platforms: -1001.
Device creation failed: -19.
Failed to set value 'opencl=ocl@va' for option 'init_hw_device': No such device
Error parsing global options: No such device

Downgrading the docker container to use Jellyfin v10.8.11 works just fine, and every file is transcoded as exptected.

On a sidenote, how can I verify that transcodes are indeed using hardware transcoding? What expressions do I need to look for in the logs?

For now, I'll just use the previous version, but I wanted to know if anybody else experienced this. If not, I might open a thread on Github. Anybody know what I should look for to try to find the fault?

[TheDreadPirate]

When 10.8.12 was released there was an OpenCL driver upgrade from Intel that was included in the official image. In this Open CL update, apparently Intel dropped support for the 4.4.X Linux kernel that is still being used by a lot of older Synology NASes.

[vitalessandro]

4.4.X Linux kernel that is still being used by a lot of older Synology NASes.

Oh, not just oder NASes. Synology's entire OS, including their latest version, still use some version of the 4.4.x kernel. Needless to say, I wouldn't buy any of their hardware again...  

Is there any (easy-ish) way to use a previous version of OpenCL for the docker container going forward?

[TheDreadPirate]

Negative. Its bundled with the image. The devs are discussing how to handle this in future releases but, for now, 10.8.11 is the latest official image you should use.

You could also give the lsio image of 10.8.12 a whirl. I know they handle drivers a bit different. Backup your server config and data before hand.

[vitalessandro]

Thanks for the info! Seems weird no one else seems to have this issue. Afaik a lot of people are running Jellyfin on Synology... or maybe I just didn't search for the right things.

I generally prefer to use official images whenever possible instead of ones maintained by 3rd parties, but I might look into it if this remains an issue. Do you know if I can use the existing config and just point the linuxserver.io image at the existing volume without issues (including 'backwards compatibility' to return to the official image)?

Also, what are the chances this is going to get resolved in future releases? I planned on continuing to use Synology in the near future for now.

[TheDreadPirate]

It only happens when you are tone mapping HDR to SDR. Regular transcoding should work fine. If you turn off tone mapping and can tolerate the off-colors it will also work. And you are not the first, btw. There were a couple other posts here and in the Matrix chat regarding this issue.

[sb19]

Hi I'm having a similar issue with a Docker install of Jellyfin 10.10.7 on my DS224+

https://privatebin.net/?89c0db91cd58c9e9...gWyqQ7ZH11

In this file is my Docker compose file, as well as a recent Jellyfin log and FFmpeg log when I try to play a video.  The video content I am trying to play is

   

and here are my transcoding settings in Jellyfin

       

I have read in other threads on the forum with this device about disabling tone mapping or setting the device to /dev/dridev/dri instead of declaring it explicitly.  However, these options do not seem to work either.  Any help is appreciated.

[pxr5]

You should disable AV1 encoding for a start. Your NAS CPU doesn't support it.

https://kb.synology.com/en-uk/DSM/tutori...y_NAS_have

https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video

[sb19]

Resolved!

All I had to do was change the user declaration in my Docker Compose file to be 1026 (user) and 937 (video group). You can check to see what your video group is by running this command as root user:

cat /etc/group | grep video

[bitmap]

Resolved!

All I had to do was change the user declaration in my Docker Compose file to be 1026 (user) and 937 (video group).  You can check to see what your video group is by running this command as root user:

cat /etc/group | grep video

I'd be careful with the user declaration. You might try group_add instead.