[SOLVED] HW tone mapping failure (QSV) - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: [SOLVED] HW tone mapping failure (QSV) (/t-solved-hw-tone-mapping-failure-qsv) |
[SOLVED] HW tone mapping failure (QSV) - cosmicvoyager - 2024-07-10 Hi, I am running Jellyfin in Docker using the Linuxserver image on a Debian machine. My server runs a 10th gen Intel i5 and I have enabled hardware transcoding with Intel QSV. in JF parameters. Transcoding SDR media works flawlessly, so does HDR media but only with tone mapping disabled. As soon as I enable tone mapping the the file does not start and I get 'Playback failed due to a fatal player error.'. The transcode logs shows the following : Code: ffmpeg version 6.0.1-Jellyfin Copyright (c) 2000-2023 the FFmpeg developers I tried enabling/disabling the VPP option but no changes. I left all Tone Mapping parameters to their default value. Any input appreciated ! Edit: I installed the intel-opencl-icd package which was not installed. By running the clinfo command on the host machine, I can see an openCL device listed. However, when running the same command insde the jellyfin docker container, no openCL devices are found. I made sure to add the jellyfin user to the render group but that did not help.
RE: HW tone mapping failure (QSV) - fract - 2024-07-10 try other way around...leave vpp checked but disble lower tonemaping option. works for me that way. also, try setting tonemapping algorithm to "none". works for me that way on gemini lake Celeron J4125 (synology). RE: HW tone mapping failure (QSV) - cosmicvoyager - 2024-07-10 Not sure why I did not think of this ... It works, however with DV content the image has the characteristic purple tint. IS this also the case for you ? RE: HW tone mapping failure (QSV) - fract - 2024-07-10 nope. looks perfectly fine... RE: HW tone mapping failure (QSV) - cosmicvoyager - 2024-07-10 I found the solution (somewhere in the depth of a forum, as you would expect). The key for me was to add the following line to my docker compose configuration: Code: environment: I was then able to use the not-VPP tone mapping and DV content worked fine. Running the clinfo command line in the jellyfin container showed the presence of an openCL device.@fract : Thank you for your answer and putting me on the right track. RE: HW tone mapping failure (QSV) - fract - 2024-07-10 np. enjoy! |