Jellyfin Forum
SOLVED: QSV suddenly stopped working, cant transcode - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: QSV suddenly stopped working, cant transcode (/t-solved-qsv-suddenly-stopped-working-cant-transcode)

QSV suddenly stopped working, cant transcode - Ilajelly - 2024-05-20

* 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

RE: QSV suddenly stopped working, cant transcode - TheDreadPirate - 2024-05-20

Was there a recent Intel driver update? Or did this problem start when you upgraded to 10.9?

RE: QSV suddenly stopped working, cant transcode - Ilajelly - 2024-05-20

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.

RE: QSV suddenly stopped working, cant transcode - TheMaFa - 2024-05-22

Had the same problem. Take a look at my thread:
https://forum.jellyfin.org/t-10-9-broke-qsv-vpp-encoding

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

RE: QSV suddenly stopped working, cant transcode - Operator - 2024-05-23

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/download/762755/intel-6th-10th-gen-processor-graphics-windows.html

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

RE: QSV suddenly stopped working, cant transcode - TheDreadPirate - 2024-05-24

Can you share the full ffmpeg log?

RE: QSV suddenly stopped working, cant transcode - Operator - 2024-05-24

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

RE: QSV suddenly stopped working, cant transcode - Ilajelly - 2024-05-24

(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/download/762755/intel-6th-10th-gen-processor-graphics-windows.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!