Web Player Stream format change and stops playing

Channels DVR Server Troubleshooting
#1

Problem seen on Version 2018.11.06.2356 (and all 3 later pre-release versions)

It's been a many days since I have used the web player on another machine in the home to view a recording.
Using Chrome, everything is hardwired to a gigabit switch

Recording starts to play, and then playback ends after I hit my buffer (5min).

Here is the log from a restart. once the message [h264_mf @ 0000000001493dc0] stream format change
the web player stops and goes back to the title screen.

I've rolled back one by one to the 11/6 version and still have the error. Playback is Hardware, Blend, 1080p 10mbs

2018/11/16 15:21:20 [SYS] Starting Channels DVR v2018.11.06.2356 (windows-x86_64 pid:2624) in C:\ProgramData\ChannelsDVR\data
2018/11/16 15:21:20 [SYS] Running as a Windows system service.
2018/11/16 15:21:22 [HDR] Found 2 devices
2018/11/16 15:21:23 [SYS] Started HTTP Server
2018/11/16 15:21:24 [DVR] Recording engine started in X:\DVR
2018/11/16 15:21:24 [DVR] Waiting 38m35.9332768s until next job 1542405600-1 Judge Judy
2018/11/16 15:21:24 [SYS] Bonjour service running for dvr-mediapc.local. [192.168.10.45]
2018/11/16 15:21:24 [NAT] Successfully mapped port 8089 using natpmp
2018/11/16 15:21:24 [SYS] Created database snapshot: backup-20181116.152124
2018/11/16 15:21:24 [SYS] Removing old backup backup-20181028.163425
2018/11/16 15:21:34 [IDX] Pruned 0 expired airings from HDHR-PREMIUM in 74.9567ms.
2018/11/16 15:21:34 [IDX] Pruned 0 expired airings from USA-OTA60014 in 45.9736ms.
2018/11/16 15:21:41 [HLS] Starting transcoder for file72-ip192.168.10.199 at 3m26s from 192.168.10.199 (encoder=h264_mf, resolution=1080, deinterlacer=blend, bitrate=10000)
[mpegts @ 000000000118c180] Dropped corrupted packet (stream = 2)
[mpegts @ 000000000118c180] Dropped corrupted packet (stream = 3)
Last message repeated 1 times
[mpegts @ 000000000118c180] Dropped corrupted packet (stream = 2)
[mpegts @ 000000000118c180] Dropped corrupted packet (stream = 3)
[mpegts @ 000000000118c180] Dropped corrupted packet (stream = 2)
[mpegts @ 000000000118c180] Dropped corrupted packet (stream = 3)
[mpegts @ 000000000118c180] Dropped corrupted packet (stream = 2)
[mpegts @ 000000000118c180] Dropped corrupted packet (stream = 3)
[h264_mf @ 0000000001493dc0] stream format change

#2

Does it work with software transcoding?

#3

Unfortunately, no. Same issue, but no stream format change message.

2018/11/16 15:37:22 [HLS] Starting transcoder for file72-ip192.168.10.199 at 5m20s from 192.168.10.199 (encoder=libx264, resolution=1080, deinterlacer=blend, bitrate=10000)
[mpegts @ 000000000114c140] Dropped corrupted packet (stream = 2)
[mpegts @ 000000000114c140] Dropped corrupted packet (stream = 3)
Last message repeated 1 times
[mpegts @ 000000000114c140] Dropped corrupted packet (stream = 2)
[mpegts @ 000000000114c140] Dropped corrupted packet (stream = 3)
[mpegts @ 000000000114c140] Dropped corrupted packet (stream = 2)
[mpegts @ 000000000114c140] Dropped corrupted packet (stream = 3)
[mpegts @ 000000000114c140] Dropped corrupted packet (stream = 2)
[mpegts @ 000000000114c140] Dropped corrupted packet (stream = 3)

#4

Might be it got corrupted during recording. Are you able to open the file in VLC and play it there?

#5

Yes, VLC plays it on the local machine no problem. Channels DVR on the ipad and Fire Stick 4K is good too

#6

Machine is running Windows 10 v 1809 (has always run this version)

This week both MS Patches were installed KB4469342 and KB4467708, in case those could have a compatibility issue
Edit -- I just looked those up and one is the insider build. Let me drop this machine out of Windows Insider and roll back

#7

Same error on web player after rollback. Have also gone down to 1080p / 8mbs
Thx

#8

Sounds like the transcoder is choking on something happening in that file. It's just the one recording that's not working?

#9

Unfortunately not. I’ll check a bunch more later tonight, but it’s more than one file (I’ve tried at least 3)

#10

Followup to this thread, will continue to try to figure this out, but it's less of a hot topic. One computer works fine in Edge, but not Chrome and the machine running the DVR works fine in Chrome.