Transcoding failing on Windows (device failed -17)

Foz86 · August 29, 2017, 5:17pm

I’m opening a new thread regarding an issue I brought up elsewhere.

I have bought a dedicated mini PC to run my DVR server. It has these specs :

OSBeelink AP34
Windows Microsoft Windows 10 Home
10.0.14393 Build 14393
CPU
4 cores / Intel(R) Celeron(R) CPU N3450 @ 1.10GHz
RAM 4.14 GB

I have a HDHR Extend.

I’m having issues with live transcoding. When trying to watch a live channel trough the web UI, transcoder will try to start but will fail after a few seconds and prompt me with an error message saying :

The media could not be loaded, either because the server or network failed or because the format is not supported

I then get this in the logs :

2017/08/29 07:36:38 [TNR] Opened connection to 1053BB4B for ch2.1 [transcode=none]
2017/08/29 07:36:38 [HLS] Starting transcoder for channel 2.1 (encoder=h264_qsv, resolution=720, deinterlacer=blend, bitrate=6000)
[h264_qsv @ 00000000001aaee0] Error during encoding: device failed (-17)
Video encoding failed
[aac @ 00000000001abd20] 2 frames left in the queue on closing
2017/08/29 07:36:47 [WRN] Buffer for 1053BB4B ch2.1 is more than 50% full (clients=1, len=16779000)
2017/08/29 07:36:51 [WRN] Buffer for 1053BB4B ch2.1 is more than 75% full (clients=1, len=25176396)
2017/08/29 07:36:54 [WRN] Buffer for 1053BB4B ch2.1 is more than 95% full (clients=1, len=31877468)
2017/08/29 07:36:55 [WRN] Buffer for 1053BB4B ch2.1 is more than 99% full (clients=1, len=33222420)
2017/08/29 07:38:44 [HLS] Stopping transcoder session ANY-ch2.1 @ 0s
2017/08/29 07:38:44 [TNR] Closed connection to 1053BB4B for ch2.1

The odd thing is that transcoding works usually fine for recordings, but it sometimes fails as well. I then get this out of the logs :

2017/08/29 07:41:25 [HLS] Starting transcoder for file-444 at 0s (encoder=h264_qsv, resolution=720, deinterlacer=blend, bitrate=6000)
[mpegts @ 00000000024dbaa0] Dropped corrupted packet (stream = 1)
[h264_qsv @ 00000000025bb680] Error during encoding: device failed (-17)
Video encoding failed
[aac @ 00000000025bcd60] 2 frames left in the queue on closing
2017/08/29 07:41:32 [HLS] Stopping transcoder session file-444 @ 981.333ms

When It happens, I just have to stop the transcoder and start it again and it will then work fine at 1.9x at 1080p 6mbp/s. This is still when playing a recorded show.

It’s a weird behavior.

Any thoughts?

I did updated the Intel drivers with their automated utility. Nothing changed.

Thanks for the help

Foz86 · August 31, 2017, 1:12pm

Oh, I forgot this bit of the puzzle :

I did managed to get the transcoder working with a live feed. But I had to set the DVR to Heavy mode.

If I leave it to none, it fails every time.

Foz86 · September 5, 2017, 12:28am

Is this being look into?

tmm1 · September 5, 2017, 1:56am

I will take a look when I return home next week

Foz86 · September 5, 2017, 2:04am

Thanks a lot!

Foz86 · September 13, 2017, 10:41pm

it’s weird how it works really great with the ATV app and iOS app but it doesn’t work at all with the web app. Can’t get it to transcode at all from the web UI now. Nor a live stream nor a recording. I trying every transcoder options and it always fails when starting.

Ryboflavins · September 21, 2017, 8:20pm

Having recently reinstalled and now running Windows I too ran into this error, on a second try it worked fine (oddly enough on the same 2.1 channel # ), but a third try on another channel resulted in the error again:

  2017/09/21 14:06:45 [TNR] Opened connection to 10401921 for ch2.1
2017/09/21 14:06:46 [HLS] Starting transcoder for channel 2.1 (encoder=h264_qsv, resolution=1080, deinterlacer=blend, bitrate=8000)
[h264_qsv @ 000000000072b0a0] Error during encoding: device failed (-17)
Video encoding failed
[aac @ 000000000072bee0] 2 frames left in the queue on closing
2017/09/21 14:06:54 [WRN] Buffer for 10401921 ch2.1 is more than 50% full (clients=1, len=16777684)
2017/09/21 14:06:57 [WRN] Buffer for 10401921 ch2.1 is more than 75% full (clients=1, len=25165868)
2017/09/21 14:07:00 [WRN] Buffer for 10401921 ch2.1 is more than 95% full (clients=1, len=31877468)
2017/09/21 14:07:01 [WRN] Buffer for 10401921 ch2.1 is more than 99% full (clients=1, len=33219788)
2017/09/21 14:07:15 [HLS] Stopping transcoder session ANY-ch2.1 @ 0s
2017/09/21 14:07:15 [TNR] Closed connection to 10401921 for ch2.1
2017/09/21 14:09:08 [TNR] Opened connection to 10401921 for ch2.1
2017/09/21 14:09:08 [HLS] Starting transcoder for channel 2.1 (encoder=h264_qsv, resolution=1080, deinterlacer=blend, bitrate=8000)
2017/09/21 14:11:29 [HLS] Stopping transcoder session ANY-ch2.1 @ 2m19.84s
2017/09/21 14:11:29 [TNR] Closed connection to 10401921 for ch2.1
[mpegts @ 000000000265b500] Dropped corrupted packet (stream = 1)
[mpeg2video @ 00000000032cfce0] ac-tex damaged at 64 8
[mpeg2video @ 00000000032cfce0] Warning MVs not available
2017/09/21 14:18:10 [TNR] Opened connection to 10401921 for ch9.1
2017/09/21 14:18:10 [HLS] Starting transcoder for channel 9.1 (encoder=h264_qsv, resolution=1080, deinterlacer=blend, bitrate=8000)
[h264_qsv @ 0000000003041680] Error during encoding: device failed (-17)
Video encoding failed
[aac @ 0000000002dd2940] 2 frames left in the queue on closing
2017/09/21 14:18:21 [WRN] Buffer for 10401921 ch9.1 is more than 50% full (clients=1, len=16777684)
2017/09/21 14:18:25 [WRN] Buffer for 10401921 ch9.1 is more than 75% full (clients=1, len=25165868)
2017/09/21 14:18:28 [WRN] Buffer for 10401921 ch9.1 is more than 95% full (clients=1, len=31877468)
2017/09/21 14:18:29 [WRN] Buffer for 10401921 ch9.1 is more than 99% full (clients=1, len=33219788)
2017/09/21 14:18:33 [HLS] Stopping transcoder session ANY-ch9.1 @ 0s
2017/09/21 14:18:33 [TNR] Closed connection to 10401921 for ch9.1

I’m using HDHR Connects though with:

OS ASUS All Series
Windows Microsoft Windows 10 Pro
10.0.15063 Build 15063
CPU
4 cores / Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz

Ryboflavins · September 22, 2017, 6:06pm

Just to add an extra wrinkle, it seems to work pretty reliably with the transcoder set to 720p 4Mb. Only failed once on that setting, whereas it has failed all but once on any of the 1080p settings.

Foz86 · October 3, 2017, 2:41am

Any developpement on this?

an we provide you with any more info?

tmm1 · October 3, 2017, 2:45am

On my windows machine I can’t get it to error out… I tried both my PRIME and CONNECT and lots of different channels.

Maybe I need to buy another windows test machine.

Foz86 · October 3, 2017, 4:48am

Try those 99$ mini PC’s from Amazon.

This it what I got and it does crash!

JMcGuire · October 3, 2017, 4:50am

It’s not just low end hardware having the issue though

Foz86 · October 3, 2017, 5:01am

Your having the same problem? what are you using?

JMcGuire · October 3, 2017, 5:23am

Windows i5 6600k

Foz86 · October 3, 2017, 2:36pm

Getting the same errors while transcoding from the web UI?

tmm1 · October 3, 2017, 7:19pm

Please open the Device Manager and check what version of the Intel HD driver is installed:

Foz86 · October 3, 2017, 7:30pm

Here is mine

tmm1 · October 3, 2017, 7:40pm

If someone is able to give me remote access to their windows machine, that would help.

If you’re able, install a VNC server (https://www.tightvnc.com/), setup port forwarding for port 5900 and then send me a private message with your IP (from ipchicken.com) and the login.

Otherwise, please try running this command in PowerShell a few times and see if it shows the same error:

C:\ProgramData\ChannelsDVR\latest\ffmpeg.exe -hide_banner -loglevel warning -f lavfi -i color=black:640x480 -t 30 -profile:v high -level 42 -g 60 -b:v 400k -c:v h264_qsv -y -f mpegts nul -stats

Foz86 · October 3, 2017, 7:46pm

I already have a VNC setup installed on mine. I don’t mind having you look around. My machine is in running a French version on Windows 10 though. Do you still wanna try? Where do I send you the credentials?

tmm1 · October 3, 2017, 7:47pm

Sure. You can email [email protected] or click on my photo to send a private message on this site.