2023-11-21, 07:57 PM
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):
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?
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 deviceDowngrading 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?