• 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 hardware acceleration on jelly fin

     
    • 0 Vote(s) - 0 Average

    hardware acceleration on jelly fin

    hardware acceleration on jelly fin
    Prince3739
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2024 Jan
    Reputation: 0
    Country:Germany
    #1
    2024-01-22, 10:28 AM (This post was last modified: 2024-01-22, 10:30 AM by Prince3739. Edited 2 times in total.)
    Hello all,
    I'm trying to figure out hardware acceleration on jelly fin. I have jell fin installed on a docker container.

    My setup
    Device : Intel NUC
    CPU : Intel® Core™ i5-5250U processor Architecture: X64
    OS : Linux Mint
    Jellyfin Version : Version: 10.8.13

    Graphics: Driver: i915 Model: HD Graphics 6000

    Below is the stack I'm running on docker container.

    services:
      jellyfin:
        image: lscr.io/linuxserver/jellyfin:latest
        container_name: jellyfin
        environment:
          - PUID=1000
          - PGID=100
          - TZ=Europe/Berlin
        volumes:
          - /xxxxx/xxxx/Documents/docker/dockerconfigs/jellyfin: /config
          - /media/datadrive/media/tv: /data/tvshows
          - /media/datadrive/media/movies: /data/movies
        ports:
          - 8096:8096
          - 8920:8920 #optional
          - 7359:7359/udp #optional
          - 1900:1900/udp #optional
        devices:
          - /dev/dri: /dev/dir
        restart: unless-stopped


    Whenever trying to play HEVC format for chrome browser on my PC, getting this error: Playback Error
    This client isn't compatible with the media and the server isn't sending a compatible media format.

    Also tried both Intel quick sync and video acceleration API but nothing works
    I have checked off the HEVC decoding but still wont work.

    Any suggestion would be help full, thanks


    Attached Files Thumbnail(s)
           
    mikesulsenti
    Offline

    Loonix Expert & Mod

    Posts: 28
    Threads: 0
    Joined: 2023 Nov
    Reputation: 3
    Country:United States
    #2
    2024-01-22, 11:41 AM
    You should be using QSV instead of VA-API when using Intel graphics

    See if your docker container can actually utilize it:
    Code:
    docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/vainfo
    and
    Code:
    docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose -init_hw_device vaapi=va -init_hw_device opencl@va

    JellyFin: 10.10.0
    OS: Proxmox 8 + Ubuntu 24.04
    CPU: 2xIntel Xeon E5-2690 v4 (28c/56t)
    RAM: 256GB DDR4
    GPU: Intel Arc A380
    Rack: HPE DL380 Gen9
    Storage: 260TB
      100TB ZFS RAIDZ3 HDD
      150TB ZFS RAIDZ3 HDD
      5TB ZFS RAIDZ1 NVMe
      5TB ZFS RAIDZ3 SSD
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #3
    2024-01-22, 02:50 PM
    You also have too many of those codec boxes checked.

    https://en.wikipedia.org/wiki/Intel_Quic...d_encoding

    MPEG2
    H264
    VC-1
    VP8
    VP9?
    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]
    Prince3739
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2024 Jan
    Reputation: 0
    Country:Germany
    #4
    2024-01-22, 04:25 PM (This post was last modified: 2024-01-22, 04:28 PM by Prince3739.)
    (2024-01-22, 11:41 AM)mikesulsenti Wrote: You should be using QSV instead of VA-API when using Intel graphics

    See if your docker container can actually utilize it:
    Code:
    docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/vainfo
    and
    Code:
    docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose -init_hw_device vaapi=va -init_hw_device opencl@va

    (2024-01-22, 04:25 PM)Prince3739 Wrote:
    (2024-01-22, 11:41 AM)mikesulsenti Wrote: You should be using QSV instead of VA-API when using Intel graphics

    See if your docker container can actually utilize it:
    Code:
    docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/vainfo
    and
    Code:
    docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose -init_hw_device vaapi=va -init_hw_device opencl@va

    (2024-01-22, 10:28 AM)Prince3739 Wrote: Hello all,
    I'm trying to figure out hardware acceleration on jelly fin. I have jell fin installed on a docker container.

    My setup
    Device : Intel NUC
    CPU : Intel® Core™ i5-5250U processor Architecture: X64
    OS : Linux Mint
    Jellyfin Version : Version: 10.8.13

    Graphics: Driver: i915 Model: HD Graphics 6000

    Below is the stack I'm running on docker container.

    services:
      jellyfin:
        image: lscr.io/linuxserver/jellyfin:latest
        container_name: jellyfin
        environment:
          - PUID=1000
          - PGID=100
          - TZ=Europe/Berlin
        volumes:
          - /xxxxx/xxxx/Documents/docker/dockerconfigs/jellyfin: /config
          - /media/datadrive/media/tv: /data/tvshows
          - /media/datadrive/media/movies: /data/movies
        ports:
          - 8096:8096
          - 8920:8920 #optional
          - 7359:7359/udp #optional
          - 1900:1900/udp #optional
        devices:
          - /dev/dri: /dev/dir
        restart: unless-stopped


    Whenever trying to play HEVC format for chrome browser on my PC, getting this error: Playback Error
    This client isn't compatible with the media and the server isn't sending a compatible media format.

    Also tried both Intel quick sync and video acceleration API but nothing works
    I have checked off the HEVC decoding but still wont work.

    Any suggestion would be help full, thanks
    Prince3739
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2024 Jan
    Reputation: 0
    Country:Germany
    #5
    2024-01-22, 04:31 PM
    @mikesulsenti thank you for suggestion, refer below, i run the commands and below is the result, what does this mean ?



    sysadmin@LinuxMint:~$ sudo docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/vainfo
    Trying display: drm
    error: failed to initialize display
    sysadmin@LinuxMint:~$ sudo docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose -init_hw_device vaapi=va -init_hw_device opencl@va~
    ffmpeg version 5.1.4-Jellyfin Copyright © 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-libs=-lfftw3f --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-libdrm --enable-libass --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libdav1d --enable-libwebp --enable-libvpx --enable-libx264 --enable-libx265 --enable-libzvbi --enable-libzimg --enable-libfdk-aac --arch=amd64 --enable-libsvtav1 --enable-libshaderc --enable-libplacebo --enable-vulkan --enable-opencl --enable-vaapi --enable-amf --enable-libmfx --enable-ffnvcodec --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvdec --enable-nvenc
    libavutil 57. 28.100 / 57. 28.100
    libavcodec 59. 37.100 / 59. 37.100
    libavformat 59. 27.100 / 59. 27.100
    libavdevice 59. 7.100 / 59. 7.100
    libavfilter 8. 44.100 / 8. 44.100
    libswscale 6. 7.100 / 6. 7.100
    libswresample 4. 7.100 / 4. 7.100
    libpostproc 56. 6.100 / 56. 6.100
    [AVHWDeviceContext @ 0x560b122254c0] Cannot open DRM render node for device 0.
    [AVHWDeviceContext @ 0x560b122254c0] Cannot open DRM render node for device 1.
    [AVHWDeviceContext @ 0x560b122254c0] Cannot open DRM render node for device 2.
    [AVHWDeviceContext @ 0x560b122254c0] Cannot open DRM render node for device 3.
    [AVHWDeviceContext @ 0x560b122254c0] Cannot open DRM render node for device 4.
    [AVHWDeviceContext @ 0x560b122254c0] Cannot open DRM render node for device 5.
    [AVHWDeviceContext @ 0x560b122254c0] Cannot open DRM render node for device 6.
    [AVHWDeviceContext @ 0x560b122254c0] Cannot open DRM render node for device 7.
    [AVHWDeviceContext @ 0x560b122254c0] No VA display found for any default device.
    Device creation failed: -22.
    Failed to set value 'vaapi=va' for option 'init_hw_device': Invalid argument
    Error parsing global options: Invalid argument
    sysadmin@LinuxMint:~$
    tmsrxzar
    Offline

    Senior Member

    Posts: 755
    Threads: 6
    Joined: 2023 Nov
    Reputation: 20
    #6
    2024-01-22, 04:31 PM (This post was last modified: 2024-01-22, 04:33 PM by tmsrxzar. Edited 2 times in total.)
    i see you have worked out how to quote posts on the forum; any chance you plan on following up to the responses you've received?

    nvm



    you have a typo

    devices:
    - /dev/dri: /dev/dir

    should be /dev/dri on the second one, not dir
    Prince3739
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2024 Jan
    Reputation: 0
    Country:Germany
    #7
    2024-01-22, 04:53 PM (This post was last modified: 2024-01-22, 04:57 PM by Prince3739.)
    (2024-01-22, 11:41 AM)mikesulsenti Wrote: You should be using QSV instead of VA-API when using Intel graphics

    See if your docker container can actually utilize it:
    Code:
    docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/vainfo
    and
    Code:
    docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose -init_hw_device vaapi=va -init_hw_device opencl@va

    (2024-01-22, 11:41 AM)mikesulsenti Wrote: You should be using QSV instead of VA-API when using Intel graphics

    See if your docker container can actually utilize it:
    Code:
    docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/vainfo
    and
    Code:
    docker exec -it jellyfin /usr/lib/jellyfin-ffmpeg/ffmpeg -v verbose -init_hw_device vaapi=va -init_hw_device opencl@va

    @TheDreadPirate thanks for sharing the wiki my cpu falls under broadwell family and HEVC is NO on the table what dos that mean ?
    tmsrxzar
    Offline

    Senior Member

    Posts: 755
    Threads: 6
    Joined: 2023 Nov
    Reputation: 20
    #8
    2024-01-22, 05:15 PM (This post was last modified: 2024-01-22, 05:20 PM by tmsrxzar. Edited 1 time in total.)
    "thanks for sharing the wiki my cpu falls under broadwell family and HEVC is NO on the table what dos that mean ? "

    unselect everything under hardware decoding, only select things that your gpu supports, the wiki link does not show capabilities for broadwell so you will have to source your own information

    unselect hevc encoding, broadwell is unlikely to be capable but when you find your gpu specs you can verify

    lastly fix the typo, nothing is going to work when you passed it as /dev/dir; it needs to be /dev/dri



    here i found your specs

    https://www.cpu-monkey.com/en/igpu-intel...phics_6000

    under the table hardware codec support, your gpu only supports h264 encoding
    supports h264, vp8, vc-1 and jpeg decoding
    Efficient_Good_5784
    Offline

    Community Moderator

    Posts: 1,167
    Threads: 3
    Joined: 2023 Jun
    Reputation: 50
    #9
    2024-01-22, 05:22 PM (This post was last modified: 2024-01-22, 05:28 PM by Efficient_Good_5784. Edited 2 times in total.)
    (2024-01-22, 10:28 AM)Prince3739 Wrote:     devices:
          - /dev/dri: /dev/dir
    Is the "/dev/dir" at the end a typo?

    (2024-01-22, 04:53 PM)Prince3739 Wrote: my cpu falls under broadwell family and HEVC is NO on the table what dos that mean ?
    This means that the iGPU doesn't support HEVC.

    I looked at the codec support table for your iGPU (with Quick Sync, hopefully these also apply for VAAPI).

    Enable these:
    1. H.264
    2. MPEG-2
    3. VC1
    4. VP8
    5. VP9 (depends on linux, disable this too if unsure)

    Disable these (don't work with your iGPU):
    1. HEVC
    2. AV1
    3. HEVC 10-bit
    4. VP9 10-bit

    The ones that you will have disabled will fall back onto the CPU.
    That is, when you attempt to stream a HEVC video on a client that wont support it, your Jellyfin server will use the CPU instead of the iGPU to transcode it.
    « 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