9to5crypto

Got it. Thanks anyways for your help!

I've just tried that and I always get the same ffmpeg crash. By the way I was already using VA-API when I got that error message about "QSV to OpenCL mapping not usable", while I don't get it in the default container, so that's why I think that might be the issue.

The official image seems to be working fine... I've found this line: [AVHWDeviceContext @ 0x55e374aee140] QSV to OpenCL mapping not usable. in the log of ffmpeg with your container, which could be the problem. I have no idea what causes that though.

I've tried many files and I always get the same error but I haven't tried the official Jellyfin container yet. I'm going to try that and let you know if it works. Thanks a lot!

Yes I've upgraded Unraid to 6.10.3 without issues. Here's the pastebin of the log with VA-API.

It gives the same error as with QSV in the Jellyfin log file unfortunately. (ffmpeg exited with code 139)

Thanks for the suggestions! I've removed the line from the go file and upgraded Unraid but that did not affect my problem, which is still there. Here are the screenshots of the playback section (I've already tried changing the tone mapping algorithm and disabling encoding to HEVC).

You're right, sorry about that. Here's the diagnotics zip file and a pastebin of Jellyfin's log file. diagnostics-20220622-2020.zip

Hello! After the update to Jellyfin version 10.8.0 I was hoping I could finally use OpenCL tone mapping but I cannot make it work. I'm currently using Intel QSV with a UHD 630 iGPU and transcoding with tone mapping makes ffmpeg crash with code 139. Does anyone have the same problem?