• 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: H265 qsv linux not working

     
    • 0 Vote(s) - 0 Average

    SOLVED: H265 qsv linux not working

    K4YN5
    Offline

    Junior Member

    Posts: 5
    Threads: 1
    Joined: 2024 Oct
    Reputation: 0
    #1
    2024-10-07, 11:42 AM
    I have a problem when trying to transcode h265 content with QSV. It doesn't show up as an option. I have the n100 cpu, and it should be capable of doing so. When QSV is deactivated, it runs, but it throttles. The files are on a good state so it's not their fault either. On the logs of the ffmpeg this show up

    [AVHWDeviceContext @ 0x59eaeb70acc0] No VA display found for any default device.
    Device creation failed: -22.
    Failed to set value 'vaapi=va:,kernel_driver=i915,driver=iHD' for option 'init_hw_device': Invalid argument
    Error parsing global options: Invalid argument

    Does anyone know how to solve it?
    Go to solution
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2024-10-07, 12:31 PM
    What OS? And do you using any virtualization (docker, VM, LXC)?

    Can you the full ffmpeg log via pastebin?
    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]
    K4YN5
    Offline

    Junior Member

    Posts: 5
    Threads: 1
    Joined: 2024 Oct
    Reputation: 0
    #3
    2024-10-07, 01:38 PM
    https://pastebin.com/Za5xQ5ef

    I am using arch Linux on bare metal and I have Jellyfin on a docker container.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2024-10-07, 02:29 PM
    You enabled AV1 encoding. The N100 does not support encoding AV1. Only decoding AV1.
    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]
    K4YN5
    Offline

    Junior Member

    Posts: 5
    Threads: 1
    Joined: 2024 Oct
    Reputation: 0
    #5
    2024-10-07, 02:45 PM
    I disabled it, however it still complains and doesn't work. The new log.

    https://pastebin.com/ZkmYR0Xp
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #6
    2024-10-07, 03:43 PM
    You still have AV1 encoding enabled.

    Code:
    -codec:v:0 av1_qsv

    What did you disable?  There are two AV1 settings.  One for decoding and one for encoding.  See my screenshot below.  The box at the top is for DECODING, which the N100 supports, and the bottom box, labeled "Allow encoding in AV1 format", is for encoding, which the N100 does not support.

       
    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]
    K4YN5
    Offline

    Junior Member

    Posts: 5
    Threads: 1
    Joined: 2024 Oct
    Reputation: 0
    #7
    2024-10-07, 07:07 PM (This post was last modified: 2024-10-07, 07:09 PM by K4YN5. Edited 1 time in total.)
    Thanks! I have been disabling the decoding and leaving the encoding enabled, however it still doesn't work.

    https://pastebin.com/An1P2hAn

    On the docker compose I haven't added any special group, render video etc., I've been seeing people adding them on some Reddit posts, could that be the cause from the error?
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #8
    2024-10-07, 07:20 PM
    Almost certainly. You have to both pass in the device and pass in the render group ID.

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

    My docker compose for reference.

    Code:
    jellyfin-prod:
        image: jellyfin/jellyfin:10.9.11
        container_name: jellyfin-prod
        user: 1002:1002
        group_add:
          - "993" # Intel render group
        networks:
          blackmoon:
            ipv4_address: 172.16.100.10
        expose:
          - 8096
        volumes:
          - ./jellyfin-prod-data/config:/config
          - ./jellyfin-prod-data/cache:/cache
          - /media/library:/media/library
          - /media/ramdisk:/media/ramdisk
        devices:
          - /dev/dri/renderD128:/dev/dri/renderD128
        environment:
          - TZ=America/New_York
        restart: unless-stopped
    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]
    K4YN5
    Offline

    Junior Member

    Posts: 5
    Threads: 1
    Joined: 2024 Oct
    Reputation: 0
    #9
    2024-10-07, 07:58 PM
    Now it's finally working!! Thank you very much!
    « 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