• 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: QSV suddenly stopped working, cant transcode

     
    • 0 Vote(s) - 0 Average

    SOLVED: QSV suddenly stopped working, cant transcode

    Ilajelly
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2024 Apr
    Reputation: 0
    #1
    2024-05-20, 05:58 PM (This post was last modified: 2024-05-20, 06:50 PM by Ilajelly. Edited 2 times in total.)
    * Jellyfin 10.9.2 (updated from 10.9.1 and from older 10.8.x version)

    * Windows installer on Windows 10

    *Intel i7-8550U


    I used QSV transcoding for a couple of months now with no issues. Suddenly a couple of days ago I couldnt transcode on any client (phone/pc ect.)
    Changing transcoding method to VAAPI works for now, but I can't seem to understand what changed, no driver changes basically the server PC was not touched.

    On pc client when trying to transcode with QSV no player appears, on Android phone client Fatal Playback error or Source Error message appears depending on player selection.

    Issue appears on any video file regardless of type.

    FFMPEG:
    https://pastebin.com/aB90CNRY

    Jellyfin logs (Direct played then trying to transcode right after):
    https://pastebin.com/zmHWc7iw


    Thank you for trying to help, if any additional information is needed just say so <3
    Go to solution
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2024-05-20, 08:08 PM
    Was there a recent Intel driver update? Or did this problem start when you upgraded to 10.9?
    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]
    Ilajelly
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2024 Apr
    Reputation: 0
    #3
    2024-05-20, 08:14 PM
    No driver updated as far as I'm aware, just the upgrade. All clients are updated to recent stable version as well but there was no updates to android version and the problem was there as well so I don't think it's a client problem.
    TheMaFa
    Offline

    Junior Member

    Posts: 10
    Threads: 1
    Joined: 2024 May
    Reputation: 0
    Country:Germany
    #4
    2024-05-22, 11:30 AM
    Had the same problem. Take a look at my thread:
    https://forum.jellyfin.org/t-10-9-broke-...p-encoding

    For me it was specifically VPP that broke QSV so I just used BT.2390 for tone mapping instead.
    Operator
    Offline

    Junior Member

    Posts: 2
    Threads: 0
    Joined: 2024 May
    Reputation: 0
    Country:Denmark
    #5
    2024-05-23, 02:33 PM (This post was last modified: 2024-05-23, 02:35 PM by Operator. Edited 1 time in total.)
    I had the exact same error when transcoding using QSV after updating from Jellyfin server 1.8.13 to 1.9.1.

    Code:
    [AVHWDeviceContext @ 000001d3bfdac200] Using device 8086:5917 (Intel(R) UHD Graphics 620).
    [AVHWDeviceContext @ 000001d3bfe69840] Error creating a MFX session: -9.
    Device creation failed: -1313558101.
    Failed to set value 'qsv=qs@dx11' for option 'init_hw_device': Unknown error occurred
    Error parsing global options: Unknown error occurred

    I am also running Jellyfin Server on a Windows box with an old Intel Pentium G4400 CPU.

    The solution for me was to update to the newest Intel HD driver for my system. For me, it is version 31.0.101.2115 for 6th-10th Gen Intel® Core™ Processor Graphics. I found it here on Intel's homepage: https://www.intel.com/content/www/us/en/...ndows.html

    It is my guess that Jellyfin might use some functions in the Intel Media SDK that needs a newer driver.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #6
    2024-05-24, 01:04 AM
    Can you share the full ffmpeg log?
    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]
    Operator
    Offline

    Junior Member

    Posts: 2
    Threads: 0
    Joined: 2024 May
    Reputation: 0
    Country:Denmark
    #7
    2024-05-24, 06:09 AM
    This is an example of the FFMPEG log before i updated the Graphics driver:
    https://pastebin.com/2VWvuaR8

    This is after the update:
    https://pastebin.com/dndgmaFh
    Ilajelly
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2024 Apr
    Reputation: 0
    #8
    2024-05-24, 11:47 AM (This post was last modified: 2024-05-24, 11:48 AM by Ilajelly. Edited 1 time in total.)
    (2024-05-23, 02:33 PM)Operator Wrote: I had the exact same error when transcoding using QSV after updating from Jellyfin server 1.8.13 to 1.9.1.

    Code:
    [AVHWDeviceContext @ 000001d3bfdac200] Using device 8086:5917 (Intel(R) UHD Graphics 620).
    [AVHWDeviceContext @ 000001d3bfe69840] Error creating a MFX session: -9.
    Device creation failed: -1313558101.
    Failed to set value 'qsv=qs@dx11' for option 'init_hw_device': Unknown error occurred
    Error parsing global options: Unknown error occurred

    I am also running Jellyfin Server on a Windows box with an old Intel Pentium G4400 CPU.

    The solution for me was to update to the newest Intel HD driver for my system. For me, it is version 31.0.101.2115 for 6th-10th Gen Intel® Core™ Processor Graphics. I found it here on Intel's homepage: https://www.intel.com/content/www/us/en/...ndows.html

    It is my guess that Jellyfin might use some functions in the Intel Media SDK that needs a newer driver.

    Nice going!

    I updated intel driver to 31.0.101.2127 (most recent on intel site) and QSV started working again.
    Thanks for the tip!
    « 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