+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: FFMPEG ERROR 237 (/t-ffmpeg-error-237)
FFMPEG ERROR 237 - citruspickles - 2025-08-17
I am getting an error 237 in logs and a source error when trying to play certain files. This is on a 1220p on Debian 12 and 13 with transcoding enabled on v10.10.7. The physical files play fine, just not through jellyfin.
Here is the recent logs that show the error:
https://pastebin.com/2Z1Jp9PY
Most transcode settings are default except the first section which I took a screenshot. I am streaming locally and expected this to direct play being that my NAS transfers range from 50-150MB/s on a U7 Pro.
RE: FFMPEG ERROR 237 - citruspickles - 2025-08-17
I think this is a package/driver issue. Looking through the docs, I am wondering if intel-opencl is supposed to be installed for my CPU/iGPU. There is no package for Debian 13, though, so not sure how to proceed. I came to this conclusion when I was working on fixing a remote bitrate issue not working properly, and finally got it going. Source errors were popping up on all videos watched remotely (I set the bitrate really low to test it and saw that transcoding was finally happening). Turning tone mapping off let the videos play, so everything is pointing towards transcoding not functioning at all, and I see I do not have this package.
RE: FFMPEG ERROR 237 - theguymadmax - 2025-08-17
Are you using the linuxserver.io Docker image?
RE: FFMPEG ERROR 237 - citruspickles - 2025-08-17
(Yesterday, 10:01 PM)theguymadmax Wrote: Are you using the linuxserver.io Docker image?
No, but it seems to have been the intel-opencl package missing after all. The jellyfin doc page with that reference has steps listed that the auto installer already does and I must have assumed that package was installed along with everything else. Manually installing the Intel *.deb files from the repository on GitHub seems to have fixed the issue on my devices. There is a mesa opencl package I tried that did not, so not sure what the difference is.
Thank you for your help, it's on me for not checking that everything needed and listed in the detailed docs was installed.