Hardware Encoding error causes firefox to say "Video can't be played because the file is corrupt."

[snake98 10]

I"m seeing a lot of failed hardware encoding, here is an expert of the log file attached

Stream mapping:
  Stream #0:0 (hevc_qsv) -> scale_qsv
  scale_qsv -> Stream #0:0 (h264_qsv)
  Stream #0:1 -> #0:1 (copy)
  Stream #0:2 -> #1:0 (subrip (srt) -> webvtt (native))
  Stream #0:3 -> #2:0 (subrip (srt) -> webvtt (native))
T=0.125s
Press [q] to stop, [?] for help
[h264_qsv @ 0000027c57518ac0] Current pixel format is unsupported
[h264_qsv @ 0000027c57518ac0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
Conversion failed!

Interesting on the Firefox note, if I pause is right when it starts, wait 30 seconds, then it play just fine.  If I don't catch it in time, I have to reload and relaunch,as it stuck on that screen with the circling dots and circling line that changes color.

 

Found this on the form, may be related

 

https://emby.media/community/index.php?/topic/63766-help-getting-started-with-quicksync/

 

ffmpeg-transcode.txt

[snake98 10]

Found out hte probem is on the decoding side.  If I disabled hvec decoding, it works but with the following error

Stream mapping:
  Stream #0:0 (hevc) -> scale
  scale -> Stream #0:0 (h264_qsv)
  Stream #0:1 -> #0:1 (copy)
  Stream #0:2 -> #1:0 (subrip (srt) -> webvtt (native))
  Stream #0:3 -> #2:0 (subrip (srt) -> webvtt (native))
T=0.109s
Press [q] to stop, [?] for help
Incompatible pixel format 'yuv420p' for codec 'h264_qsv', auto-selecting format 'nv12'
[segment @ 000002472bef9d00] Opening 'D:\Transcoding\transcoding-temp\ccd69ba4438155ce96e71eeb12e6018c0.ts.tmp' for writing
Output #0, segment, to 'D:\Transcoding\transcoding-temp\ccd69ba4438155ce96e71eeb12e6018c%d.ts':
  Metadata:
    encoder         : Lavf58.12.100
    Stream #0:0: Video: h264 (h264_qsv), nv12, 720x302 [SAR 302:303 DAR 240:101], q=-1--1, 1180 kb/s, Level 4, 23.98 fps, 90k tbn, 23.98 tbc (default)
    Metadata:
      encoder         : Lavc58.18.100 h264_qsv
    Side data:

[Luke 42087]

Hi, did you follow the steps in our hardware acceleration setup guide?

https://github.com/MediaBrowser/Wiki/wiki/Hardware-Acceleration-Overview

[snake98 10]

Yes, I have a dummy plug in, running windows 10 with the Latest drivers, not as a service. I"m thinking it's a that intel can't decode it, as I tried with vlc and it used the cpu to decode.  Is there an easy way to test if the hardware decode will work outside of emby?

[Luke 42087]

Yes, I have a dummy plug in, running windows 10 with the Latest drivers, not as a service. I"m thinking it's a that intel can't decode it, as I tried with vlc and it used the cpu to decode.  Is there an easy way to test if the hardware decode will work outside of emby?

 

Perhaps using some other application such as handbrake.