Transcoding failing on Windows (device failed -17)

message has been sent

Chrome Remote Desktop ok?

I was able to reproduce the issue on @Foz86ā€™s machine, so Iā€™m good on remote access for now. Itā€™s definitely a weird bugā€¦ happens randomly.

Iā€™m glad it helped you.

Howā€™s your French? :stuck_out_tongue_winking_eye:

For me it didnā€™t seem random, at least not judging by channel, seemed like it was always the same channels that threw the error.

Interesting. Chrome Desktop is fine if you want to send me the details, I can try to see if your computer acts the same way as the other one.

Did you learn anything from mine?

My windows computer has an older J1800 CPU, and the driver version is only v10.18.10.4425. I couldnā€™t find any updates to it. My computer doesnā€™t have this problem.

Both @Foz86 and @JMcGuire are using driver v22.20.16.4771, and both of them are seeing the same problem.

@uspino and @Ryboflavins Can you check and post the version of the Intel Graphics driver installed on your system?

Oh no! I switched box to Ubuntu (I use the transcoder a fair bit). Iā€™ve got some other intel based hardware I can throw Windows on though, Iā€™ll get back to ya ASAP!

Iā€™ve got a Nuc i3 4010u with a 2016 driver I can test if needed

is there an easy way to go back to an older driver?

Here you go (i7-5557U NUC):

Driver Date: 9/29/2016
Version: 20.19.15.4531

Updated to 3/8/2017, latest 20.19.15.4624 drivers, same behavior.

Also, I used to get almost instant streaming when accessing remotely, selecting ā€œOriginalā€ on Internet Streaming Quality. Now it fails pretty much all the time, I think itā€™s actually trying to encode instead of remux (ffmpeg process goes up to 50% CPU on an i7). This is what I get (again, trying to stream on full, original MPEG2 quality on iOS):

017/10/04 02:24:45 [TNR] Opened connection to 132286F4 for ch665
2017/10/04 02:24:45 [HLS] Starting transcoder for channel 665 (encoder=h264_qsv, resolution=0, deinterlacer=blend, bitrate=10000)
[ac3 @ 0000000000622240] frame sync error
Error while decoding stream #0:1: Invalid data found when processing input
[aac @ 000000000068ec00] Queue input is backward in time
[hls @ 0000000002d2e620] Non-monotonous DTS in output stream 0:1; previous: 4800, current: 3840; changing to 4801. This may result in incorrect timestamps in the output file.
[h264_qsv @ 0000000002db8a60] Error during encoding: device failed (-17)
Video encoding failed
[aac @ 000000000068ec00] 2 frames left in the queue on closing
2017/10/04 02:24:55 [HLS] Stopping transcoder session ANY-ch665 @ 0s
2017/10/04 02:24:55 [TNR] Closed connection to 132286F4 for ch665

Hi there - I have a similar device failed -17 issue when trying to watch a recording through the web UI (I have an HDHR Prime). Note that some recordings it works fine, others I get the error. For the ones I get an error, I can view them just fine in VLC, etc, so something seems to be an issue with the transcoding. I can consistently replicate the failure on several recordings.

I have an Intel i3-4130 with driver version 20.19.15.4531 (dated 9/29/2016).

Please post your windows version too.

Exact same behavior as mine

Windows 10 Pro 64-bit

Also, I just updated the intel drivers to the latest using the intel driver update utility, and still the same issue (the latest drivers I have are 20.19.15.4703 dated 6/9/2017)

Good news everyone! This issue is finally fixed.

Run this command in powershell to upgrade, and let me know how the new version works for you.

Invoke-WebRequest -UseBasicParsing -Method PUT http://127.0.0.1:8089/updater/check/2017.10.11.2148

2 Likes

The fixed updated version works great for meā€¦ my transcoding issues are fixed! Curiousā€¦ what was the issue? Great work!

1 Like