Jellyfin Forum
Transcoding issue on Windows with MKV using QSV - 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: Transcoding issue on Windows with MKV using QSV (/t-transcoding-issue-on-windows-with-mkv-using-qsv)



Transcoding issue on Windows with MKV using QSV - MadOx75 - 2024-02-29

Good afternoon.  I'm still pretty new to the Jellyfin game, and I know the default answer is "Use Linux", but I was having all kinds of fits with getting the permissions right. I will likely go back and try it again at some point, but for now, Windows is doing a fine job - for the most part.  

I have a movie file that is HDR H265 MKV.  When I try to play it on another Windows PC on the LAN, both through the browser and the Jellyfin Media Player, I get the " This client isn't compatible with the media and the server isn't sending a compatible media format" error.  I had ToneMapping enabled, and someone mentioned that didn't work in Windows, so I turned it off.  Still the same error.  

I'm using Beelink with an N100. It seems to transcode other movies I have without issue - They appear to be MKV with HEVC/H264.  

This isn't really an issue, as it plays just fine on my TV, which doesn't require transcoding, and is primarily what I watch on.  I'm just curious what could cause this issue, and if its resolvable, until such time I go back and get it working on Linux again.


RE: Transcoding issue on Windows with MKV using QSV - TheDreadPirate - 2024-02-29

If you are using Intel's latest drivers, you will need to revert. There is a bug in their latest drivers that breaks transcoding. Revert to one of their November or December 2023 drivers. I forget the exact version number that isn't broken.


RE: Transcoding issue on Windows with MKV using QSV - MadOx75 - 2024-02-29

(2024-02-29, 05:57 PM)TheDreadPirate Wrote: If you are using Intel's latest drivers, you will need to revert.  There is a bug in their latest drivers that breaks transcoding.  Revert to one of their November or December 2023 drivers.  I forget the exact version number that isn't broken.

I did do an update last night and I think it upgraded the video driver, but I reverted it before posting as well. The driver is from October 2023.  

Below is the message in the log.  With that last "invalid data found when processing" maybe its just a bad rip?

Code:
/videos/aaa7b84f-4839-0d01-49a4-3ab820c5d7f3/live.m3u8

{"Protocol":0,"Id":"aaa7b84f48390d0149a43ab820c5d7f3","Path":"E:\\Movies\\Wonder.Woman.1984.2020.2160p.MAX.WEB-DL.DDPA.5.1.DV.HDR.H.265\\Wonder.Woman.1984.2020.2160p.MAX.WEB-DL.DDPA.5.1.DV.HDR.H.265.mkv","EncoderPath":null,"EncoderProtocol":null,"Type":0,"Container":"mkv","Size":null,"Name":"Wonder.Woman.1984.2020.2160p.MAX.WEB-DL.DDPA.5.1.DV.HDR.H.265","IsRemote":false,"ETag":"157f5e9306b8661fdeb0c9efa80e4edf","RunTimeTicks":null,"ReadAtNativeFramerate":false,"IgnoreDts":false,"IgnoreIndex":false,"GenPtsInput":false,"SupportsTranscoding":true,"SupportsDirectStream":true,"SupportsDirectPlay":true,"IsInfiniteStream":false,"RequiresOpening":false,"OpenToken":null,"RequiresClosing":false,"LiveStreamId":null,"BufferMs":null,"RequiresLooping":false,"SupportsProbing":true,"VideoType":0,"IsoType":null,"Video3DFormat":null,"MediaStreams":[],"MediaAttachments":[],"Formats":[],"Bitrate":null,"Timestamp":null,"RequiredHttpHeaders":{},"TranscodingUrl":null,"TranscodingSubProtocol":null,"TranscodingContainer":null,"AnalyzeDurationMs":null,"DefaultAudioStreamIndex":null,"DefaultSubtitleStreamIndex":null}

ffmpeg -analyzeduration 200M -init_hw_device d3d11va=dx11:,vendor=0x8086 -init_hw_device qsv=qs@dx11 -filter_hw_device qs -autorotate 0 -i file:"E:\Movies\Wonder.Woman.1984.2020.2160p.MAX.WEB-DL.DDPA.5.1.DV.HDR.H.265\Wonder.Woman.1984.2020.2160p.MAX.WEB-DL.DDPA.5.1.DV.HDR.H.265.mkv" -map_metadata -1 -map_chapters -1 -threads 0 -sn  -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_delay 5000000 -hls_time 3 -hls_segment_type mpegts -start_number 0 -hls_base_url "hls/5c86659f79eca573cf92f8194fca72e6/" -hls_segment_filename "C:\ProgramData\Jellyfin\Server\transcodes\5c86659f79eca573cf92f8194fca72e6%d.ts" -hls_playlist_type event -hls_list_size 0 -y "C:\ProgramData\Jellyfin\Server\transcodes\5c86659f79eca573cf92f8194fca72e6.m3u8"


ffmpeg version 5.1.4-Jellyfin Copyright (c) 2000-2023 the FFmpeg developers
  built with gcc 12-win32 (GCC)
  configuration: --prefix=/opt/ffmpeg --arch=x86_64 --target-os=mingw32 --cross-prefix=x86_64-w64-mingw32- --pkg-config=pkg-config --pkg-config-flags=--static --extra-libs='-lfftw3f -lstdc++' --extra-cflags=-DCHROMAPRINT_NODLL --extra-version=Jellyfin --disable-ffplay --disable-debug --disable-doc --disable-sdl2 --disable-ptx-compression --disable-w32threads --enable-pthreads --enable-shared --enable-lto --enable-gpl --enable-version3 --enable-schannel --enable-iconv --enable-libxml2 --enable-zlib --enable-lzma --enable-gmp --enable-chromaprint --enable-libfreetype --enable-libfribidi --enable-libfontconfig --enable-libass --enable-libbluray --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libopenmpt --enable-libwebp --enable-libvpx --enable-libzimg --enable-libx264 --enable-libx265 --enable-libsvtav1 --enable-libdav1d --enable-libfdk-aac --enable-opencl --enable-dxva2 --enable-d3d11va --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 @ 0000017a5219c900] Using device 8086:46d1 (Intel(R) UHD Graphics).
[matroska,webm @ 0000017a509a9240] Format matroska,webm detected only with low score of 1, misdetection possible!
[matroska,webm @ 0000017a509a9240] 0x00 at pos 0 (0x0) invalid as first byte of an EBML number
[matroska,webm @ 0000017a509a9240] EBML header parsing failed
file:E:\Movies\Wonder.Woman.1984.2020.2160p.MAX.WEB-DL.DDPA.5.1.DV.HDR.H.265\Wonder.Woman.1984.2020.2160p.MAX.WEB-DL.DDPA.5.1.DV.HDR.H.265: Invalid data found when processing input



RE: Transcoding issue on Windows with MKV using QSV - TheDreadPirate - 2024-02-29

Run DDU, reboot, reinstall the older driver. Someone else had to do this to truly remove the broken driver.


RE: Transcoding issue on Windows with MKV using QSV - nyanmisaka - 2024-03-01


[matroska,webm @ 0000017a509a9240] 0x00 at pos 0 (0x0) invalid as first byte of an EBML number

[matroska,webm @ 0000017a509a9240] EBML header parsing failed


This error usually hints at a corrupted video file where the checksum has been changed.