Anyone having a problem playing MSNBC? I tried an update and rescan with no luck. Log says rescan was successful, and I can stream MSNBC using both web and NBC app.
Channel 6050-MSNBC is working for me on DVR version 2021.06.17.1801.
What error does it show when trying to play?
Any errors in the DVR log when you try to play the channel?
1 Like
MSNBC is working for me as well.
when I try to watch MSNBC, after many seconds it just says "Timeout:. This log entry is related to me selecting MSNBC: 2021/06/25 06:18:25.527504 [TNR] Sharing existing connection to TVE-Cablevision for ch6050 MSNBC (clients=8, len=67108864)
If I tune to CNBC, it woks fine. Here is the CNBC Channel Selection log entry:
2021/06/25 06:19:20.879784 [TNR] Opened connection to TVE-Cablevision for ch6051 CNBC
2021/06/25 06:20:03.419459 [TVE] stream timestamps: cnn: start_at=2021-06-25T06:09:50-04:00 current_at=2021-06-25T06:19:32-04:00 end_at=2021-06-25T06:19:44-04:00
if I tune to CNN it works fine. Here is the log entry for CNN channel selection:
2021/06/25 06:20:03.419510 [TNR] Opened connection to TVE-Cablevision for ch6030 CNN
As you can see, when I select MSNBC, the log says "sharing existing connection..." and the CNBC anc CNN examples both just say "Opened Connection". So there is something different about MSNBC. Any ideas?
I should add that during my previous post, there was a scheduled recording on MSNBC. That playback didnt work, so I deleted it. I then tried to tune to MSNBC unsuccessfully, and here is the log:
2021/06/25 06:45:00.002498 [TNR] Sharing existing connection to TVE-Cablevision for ch6050 MSNBC (clients=9, len=67108864)
2021/06/25 06:45:00.003506 [HLS] Starting transcoder for channel 6050 from 192.168.0.180 (encoder=remux, resolution=, deinterlacer=, bitrate=4200)
2021/06/25 06:45:00.504142 [HLS] Probed live stream in 500.483106ms: h264 1920x1080 progressive 3939623bps
2021/06/25 06:45:16.102637 [HLS] Couldn't generate stream playlist for ch6050-dANY-ip192.168.0.180: Timeout waiting for session to start after 8s
2021/06/25 06:45:16.102741 [HLS] Stopping transcoder session ch6050-dANY-ip192.168.0.180 (out: 0s, finished: false)
2021/06/25 06:45:17.115855 [TNR] Sharing existing connection to TVE-Cablevision for ch6050 MSNBC (clients=9, len=67108864)
2021/06/25 06:45:17.116862 [HLS] Starting transcoder for channel 6050 from 192.168.0.180 (encoder=remux, resolution=, deinterlacer=, bitrate=4200)
2021/06/25 06:45:17.418885 [HLS] Probed live stream in 301.481666ms: h264 1920x1080 progressive 3939623bps
2021/06/25 06:45:25.160523 [HLS] Couldn't generate stream playlist for ch6050-dANY-ip192.168.0.180: Timeout waiting for session to start after 8s
2021/06/25 06:45:25.160629 [HLS] Stopping transcoder session ch6050-dANY-ip192.168.0.180 (out: 0s, finished: false)
Try restarting the DVR on your Synology
sorry for the dumb question, but how do I do that? I just looked at installed packages on the Synology and could find nothing called "Channels:. How do I find the app on the Synology to stop ad restart?
Disregard. Figured out how to restart DVR on Synology and MSNBC working now.
check this log out. I tuned to MSNBC. It came on fine, Then I checked the logs. See the note below about "Timestamps being unset" and a warning that this will break again. Should we be concerned? In all honesty, MSNBC is the only channel my wife cares about. If I can't keep MSNBC reliably working, its goodbye Channels DVR for me.
2021/06/25 17:28:53.396821 [TNR] Opened connection to TVE-Cablevision for ch6050 MSNBC
2021/06/25 17:28:53.644119 [HLS] Starting transcoder for channel 6050 from 192.168.0.180 (encoder=remux, resolution=, deinterlacer=, bitrate=4200)
2021/06/25 17:28:54.591129 [HLS] Probed live stream in 945.24544ms: h264 1920x1080 progressive 3862645bps
2021/06/25 17:28:54.805567 [HLS] ffmpeg: ch6050-dANY-ip192.168.0.180-remux: [hls @ 0x6ba4ac0] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2021/06/25 17:28:54.874421 [HLS] Session ch6050-dANY-ip192.168.0.180 started in 4.12821746s
No. It is the DVR saying that the incoming stream from MSNBC has errors. It does what it can to correct the feed before sending it on to clients, but there is only so much it can do. Garbage in, garbage out. (NBCUniversal streams seem to regularly have issues with timestamps, either not being present, or differing when commercials are inserted, that this is just something you'll have to suffer through.)
racameron is correct.
Channels DVR TVE captures a streaming TV channel from a networks website to allow you to view or record it.
Streaming isn't 100% reliable, but Channels does a great job trying to fix errors the networks send.
The Channels DVR log captures a lot of info, but not everything is an error or something to be concerned about.You could either learn what everything in the log means, or only refer to it when you have issues.
In the example you gave, Channels DVR (which uses ffmpeg) was remuxing the Live feed, probably because you were playing it in a web browser, and the error just meant that one packet didn't have a timestamp. Nothing you would ever notice when viewing. That type of in-depth logging is there for the developers to view if you report an issue with viewing the Live or recorded stream.
My DVR log...
2021/06/25 16:05:56.720297 [HLS] Starting transcoder for channel 6050 from 192.168.1.8 (encoder=remux, resolution=, deinterlacer=, bitrate=4200)
2021/06/25 16:05:58.381797 [HLS] ffmpeg: ch6050-dANY-ip192.168.1.8-remux: [hls @ 0x71fa4c0] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2021/06/25 16:05:58.536529 [HLS] Probed live stream in 1.815854772s: h264 1920x1080 progressive 3862645bps
2021/06/25 16:05:58.580651 [HLS] Session ch6050-dANY-ip192.168.1.8 started in 4.085861098s
2021/06/25 16:06:10.138468 [HLS] Stopping transcoder session ch6050-dANY-ip192.168.1.8 (out: 28.261011s, finished: false)
2021/06/25 16:06:10.138996 [HLS] ffmpeg: ch6050-dANY-ip192.168.1.8-remux: [mpegts @ 0x71c4ac0] Dropped corrupted packet (stream = 1)
2021/06/25 16:06:10.148291 [TNR] Closed connection to TVE-Comcast_SSO for ch6050 MSNBC```Thank you
I have been having similar problems with MSNBC for weeks now.
1 Like
Meaning?
I just realized this thread was already here. I opened a different one a few days later. I'm having the same issue: MSNBC works on and off. I'm hoping the Channels team will be able to find a solution.
Having problems over the last 2 days on nvidia shield TV. Troubleshooting tab reports:
"Chrome version is out of date: HeadlessChrome/81.0.4044.113"
Force update doesn't appear to work.
Not sure what to do about it. I also just tried viewing content via the NBC News app, which doesn't appear to work either (hangs).
If you go to Support>Troubleshooting on your DVR web UI, is there a FIX CHROME button you can press?
No, it won't force an upgrade that way. I'm guessing nvidia may have the chrome version pegged to the OS?
Are you running the latest DVR prerelease version 2021.08.10.2129?
1 Like
I normally shy away from prereleases--does it contain a known fix for this issue?