Unable to get tone mapping working

[kickingknowledge]

Running version 10.10.3 in a Docker container on Linux (OMV on Debian)

Here's my docker-compose: https://pastebin.com/9VeUZKz8

Current tone mapping settings: https://imgur.com/a/YbZhyDC

Most recent ffmpeg logs via JF: https://pastebin.com/1mMQNXcz

Most recent JF logs: https://pastebin.com/K5ZxKGvz

I'm working with an Intel i3-10100, no discrete GPU. VPP tone mapping works on its own terms, but the colurs are way too dark, so I want to get regular tone mapping working.

Output of

Code:

docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -v debug -init_hw_device opencl

: https://pastebin.com/5K2bd0cA

What should be my next step here?

[theguymadmax]

You need to pass the render group into the container. Here's my compose file.

Code:

services:
  jellyfin:
    image: jellyfin/jellyfin:latest
    container_name: jellyfin
    user: 1000:1000  #[color=#c7c2ba]uid:gid[/color]
    group_add:
      - "992" #render
    network_mode: 'host' 
    volumes:
      - /home/max/Dockers/Jellyfin/Config:/config
      - /home/max/Dockers/Jellyfin/Cache:/cache
      - /media/Media1:/Movies
      - /media/Media2:/Show
    restart: 'unless-stopped'
    devices:
      - /dev/dri/renderD128:/dev/dri/renderD128

[kickingknowledge]

This hasn't fixed it, unfortunately. I checked the render group:

Code:

$getent group render

Which returned:

Code:

render:x:106:

I updated the docker-compose (as a Portainer stack) accordingly:

 

Code:

jellyfin:
      image: lscr.io/linuxserver/jellyfin
      container_name: jellyfin
      group_add:
        - 106 #render
      environment:
        - PUID=1000
        - PGID=100
        - TZ=Europe/Berlin
      devices:
        - /dev/dri/renderD128:/dev/dri/renderD128
        - /dev/dri/card0:/dev/dri/card0
      volumes:
        - /srv/dev-disk-by-uuid-xxx/config0/jellyfin:/config
        - /srv/dev-disk-by-uuid-yyy/config0/jellyfin/cache:/cache
        - /srv/dev-disk-by-uuid-zzz/media:/media
      ports:
        - 8096:8096
        - 8920:8920
        - 7359:7359/udp
        - 1900:1900/udp
      restart: unless-stopped

I do notice the linuxserver image, not the official jellyfin image. Could this be a problem?

Here's the most recent logs and ffmpeg logs:
https://pastebin.com/pMqkLF7K
https://pastebin.com/7GvUwNPC

[theguymadmax]

Add the Intel OpenCLDocker mod for Jellyfin into the environment variables of your compose file.

Code:

DOCKER_MODS=linuxserver/mods:jellyfin-opencl-intel

[kickingknowledge]

This got it. Thank you! Is this mod also necessary for the official JF image, or just the linuxserver one?

[bitmap]

The official container already comes with OpenCL.

https://jellyfin.org/docs/general/admini...ualization

[kickingknowledge]

Is the official image generally recommended over the linuxserver one/are there other advantages to using the official one? I've had this JF instance running for 2.5 years already; I don't recall why I chose the linuxserver one.

[TheDreadPirate]

For most users, there is no practical difference. Though some users have encountered weird bugs in the linuxserver image that don't exist in the official image. If the linuxserver image works for you, don't bother switching. The linuxserver image has their configs organized a bit differently which makes it difficult to interchange your existing Jellyfin data with the official image.