• 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 Transcoding not working on docker with QSV

     
    • 0 Vote(s) - 0 Average

    Transcoding not working on docker with QSV

    kaeru
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    Country:Italy
    #1
    2025-02-27, 12:50 AM
    Hello, I am having troubles with transcoding.
    I have an old QNAP NAS (TS451A) with an Intel Celeron N3060 CPU. This CPU should support Intel QSV. I use docker to run jellyfin and I imported the device for the GPU
    Transcoding never worked great, but I noticed that I was using VAAPI, so I tried to switch to QVS but i get the error:

    [AVHWDeviceContext @ 0x5592e061bdc0] libva: /usr/lib/jellyfin-ffmpeg/lib/dri/iHD_drv_video.so init failed
    [AVHWDeviceContext @ 0x5592e061bdc0] Failed to initialise VAAPI connection: 1 (operation failed).
    Device creation failed: -5.
    Failed to set value 'vaapi=va: /dev/dri/renderD128,driver=iHD' for option 'init_hw_device': Input/output error
    Error parsing global options: Input/output error

    full ffmpeg log
    .txt   ffmpeg.txt (Size: 11.52 KB / Downloads: 34)

    I don't really know what I'm doing wrong here.
    Thank you in advance for your help
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2025-02-27, 01:33 PM
    You are trying to encode to HEVC, which your Braswell CPU does not support. Uncheck "Allow encoding in HEVC format".

    Use this table to ensure you only check the boxes your CPU/iGPU supports decoding or encoding.

    https://en.wikipedia.org/wiki/Intel_Quic...d_encoding
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    kaeru
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    Country:Italy
    #3
    2025-03-04, 05:37 PM
    I'm sorry for the delay. I probably didn't set the notifications settings right.
    The option you mentioned was already unchecked. The link you sent made me realize that I was trying to transcode HEVC with a depth of 10 bits, that is unsupported by my iGPU.
    Transcoding of HEVC 8bit lead to the same error though
    34626
    Offline

    Member

    Posts: 172
    Threads: 36
    Joined: 2023 Jul
    Reputation: 0
    Country:Denmark
    #4
    2025-03-04, 06:19 PM
    Could you also please share your docker-compose fle?
    Serv: N5105 - 32GB RAM, 1 WD Red SA500 2TB, 2 8TB, 2 4TB WD Red Plus, LC-35U3-C-HUB
    OS: Debian
    Clients: Pi4 with LibreELEC + JellyCon and Jellyfin Media Player
    Network: 2 TP-Link AX23, OpenWRT mesh 802.11s and 1 Gbit
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #5
    2025-03-04, 06:32 PM
    (2025-03-04, 05:37 PM)kaeru Wrote: I'm sorry for the delay. I probably didn't set the notifications settings right.
    The option you mentioned was already unchecked. The link you sent made me realize that I was trying to transcode HEVC with a depth of 10 bits, that is unsupported by my iGPU.
    Transcoding of HEVC 8bit lead to the same error though

    In my post I stated that your CPU/iGPU doesn't support HEVC ENcoding.  There is a separate check box farther down labeled "Allow encoding in HEVC format" and that you need to uncheck that one.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    kaeru
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    Country:Italy
    #6
    2025-03-05, 12:45 PM (This post was last modified: 2025-03-05, 12:47 PM by kaeru. Edited 1 time in total.)
    I'm sorry I didn't explain myself. I probably unckecked the check box for HEVC ENCODING a while back and so I found it unchecked when I switched to QVS. Anyway it is unchecked and I get the same error.
    For transcoding I have checked h264, HEVC, MPEG2, VC1, VP8
    For encoding I have nothing checked as it sais that h264 is always on


    Here is the docker compose:

    services:
    jellyfin:
    image: jellyfin/jellyfin
    container_name: jellyfin
    network_mode: 'host'
    volumes:
    - /share/Container/jellyfin/config: /config
    - /share/Container/jellyfin/cache: /cache
    - /share/Multimedia: /media
    devices:
    - /dev/dri/: /dev/dri/
    restart: 'unless-stopped'

    I am using portainer, don't know if it helps
    [edit]I adderd a space between the ":" and the "/" as it were interpret as the Confused-face emoji. On my docker compose there is no space
    34626
    Offline

    Member

    Posts: 172
    Threads: 36
    Joined: 2023 Jul
    Reputation: 0
    Country:Denmark
    #7
    2025-03-05, 04:00 PM (This post was last modified: 2025-03-05, 04:01 PM by 34626. Edited 1 time in total.)
    Please try this, do backup your current docker-compose.ymlfile

    One error you may occur with the text below is missing spave in the beginning, but else it should work, i use the added functions with Debian 12.9 with QSV which works. Be also aware that i have edited in the path to config and cache, should also work

    services:
    jellyfin:
    image: jellyfin/jellyfin:latest # 10.10.6 (current)
    container_name: jellyfin
    network_mode: 'host'
    group_add:
      - "105" # Run in terminal to verify the number: "getent group render | cut -d: -f3"
    volumes:
    - ./config: /config
    - ./cache: /cache
    - /share/Multimedia: /media
        devices:
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/dri/card0:/dev/dri/card0
    restart: 'unless-stopped'
    Serv: N5105 - 32GB RAM, 1 WD Red SA500 2TB, 2 8TB, 2 4TB WD Red Plus, LC-35U3-C-HUB
    OS: Debian
    Clients: Pi4 with LibreELEC + JellyCon and Jellyfin Media Player
    Network: 2 TP-Link AX23, OpenWRT mesh 802.11s and 1 Gbit
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #8
    2025-03-05, 05:01 PM
    If I'm reading your initial log correctly, you do NOT have the following box checked.

    "Prefer OS native DXVA or VA-API hardware decoders"

    Try checking that box. It is slightly slower than using QSV for decoding, but it is more flexible and reliable.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    pxr5
    Offline

    Member

    Posts: 51
    Threads: 3
    Joined: 2024 Jan
    Reputation: 3
    Country:United Kingdom
    #9
    2025-03-07, 07:21 PM
    I can't help with this I'm afraid as I have exactly the same problem with an Intel Braswell CPU in a Synology NAS. It works fine with VAAPI, but any configuration with QSV will cause a fatal playback error with the same log info as in the OP's post. I've tried pretty much every configuration of the transcoding settings in Jellyfin. This is my compose file - I've tried it as root too with no joy. I've tried this as well ("Prefer OS native DXVA or VA-API hardware decoders") and paired back everything to h.264, low power settings on/off etc.

    services:
    jellyfin:
    image: jellyfin/jellyfin:latest
    container_name: Jellyfin
    environment:
    - PUID=1027
    - PGID=65536
    - TZ=Europe/London
    group_add:
    - "937" \ # Change this to match your "render/video/input" host group id and remove this comment
    volumes:
    - /volume1/docker/jellyfin/cacheConfused-facecache:rw
    - /volume1/docker/jellyfin/configConfused-faceconfig:rw
    - /volume1/video3/TVConfused-faceTV:ro
    - /volume1/video3/MovieConfused-faceMovie:ro
    devices:
    - /dev/dri/renderD128Confused-facedev/dri/renderD128
    - /dev/dri/card0Confused-facedev/dri/card0
    ports:
    - 8096:8096/tcp
    network_mode: host
    restart: unless-stopped
    Jellyfin1 - 10.10.3 (Docker) Synology NAS (transcoding off)
    Jellyfin2 - 10.10.3 Minix ZX100-0db MiniPC, Intel N100 (transcoding on)
    Storage - x3 Synology NAS (22TB)
    Reverse Proxy - Caddy v2 running on a Pi3b+
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #10
    2025-03-07, 07:29 PM
    It is quite possible that the Intel packages we include in our container no longer support Braswell. As Intel has a habit of dropping support. So you may just need to use VAAPI, which works with both AMD and Intel.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    « 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