• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting [SOLVED] HW tone mapping failure (QSV)

     
    • 0 Vote(s) - 0 Average

    [SOLVED] HW tone mapping failure (QSV)

    HDR content fails to transcode using Intel QSV with tone mapping enabled
    cosmicvoyager
    Offline

    Junior Member

    Posts: 6
    Threads: 2
    Joined: 2024 Jul
    Reputation: 0
    Country:Netherlands
    #1
    2024-07-10, 10:20 AM (This post was last modified: 2024-07-10, 01:38 PM by cosmicvoyager. Edited 6 times in total.)
    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
      built with gcc 11 (Ubuntu 11.4.0-1ubuntu1~22.04)
      configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --extra-version=Jellyfin --disable-doc --disable-ffplay --disable-ptx-compression --disable-static --disable-libxcb --disable-sdl2 --disable-xlib --enable-lto --enable-gpl --enable-version3 --enable-shared --enable-gmp --enable-gnutls --enable-chromaprint --enable-opencl --enable-libdrm --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libsvtav1 --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=amd64 --enable-libshaderc --enable-libplacebo --enable-vulkan --enable-vaapi --enable-amf --enable-libvpl --enable-ffnvcodec --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvdec --enable-nvenc
      libavutil      58.  2.100 / 58.  2.100
      libavcodec    60.  3.100 / 60.  3.100
      libavformat    60.  3.100 / 60.  3.100
      libavdevice    60.  1.100 / 60.  1.100
      libavfilter    9.  3.100 /  9.  3.100
      libswscale      7.  1.100 /  7.  1.100
      libswresample  4. 10.100 /  4. 10.100
      libpostproc    57.  1.100 / 57.  1.100
    libva info: VA-API version 1.21.0
    libva info: Trying to open /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so
    libva info: Found init function __vaDriverInit_1_21
    libva info: va_openDriver() returns 0
    [AVHWDeviceContext @ 0x55f17ec74500] 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

    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.
    fract
    Offline

    Junior Member

    Posts: 21
    Threads: 3
    Joined: 2024 Jul
    Reputation: 0
    Country:Croatia
    #2
    2024-07-10, 10:53 AM
    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).
    cosmicvoyager
    Offline

    Junior Member

    Posts: 6
    Threads: 2
    Joined: 2024 Jul
    Reputation: 0
    Country:Netherlands
    #3
    2024-07-10, 11:22 AM
    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 ?
    fract
    Offline

    Junior Member

    Posts: 21
    Threads: 3
    Joined: 2024 Jul
    Reputation: 0
    Country:Croatia
    #4
    2024-07-10, 01:11 PM
    nope. looks perfectly fine...
    cosmicvoyager
    Offline

    Junior Member

    Posts: 6
    Threads: 2
    Joined: 2024 Jul
    Reputation: 0
    Country:Netherlands
    #5
    2024-07-10, 01:26 PM
    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:
      - ...
      - DOCKER_MODS=linuxserver/mods:jellyfin-opencl-intel

    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.
    fract
    Offline

    Junior Member

    Posts: 21
    Threads: 3
    Joined: 2024 Jul
    Reputation: 0
    Country:Croatia
    #6
    2024-07-10, 01:29 PM
    np. enjoy!
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode