Locast issues in LA market

quite often for the past few months (although i'm just now getting around to posting about it), KTLA-DT 2 and 3 locast streams won't play through channels. they load and just freeze immediately, with the spinning wheel in the playback buffer status area. the streams are not down, they work in the locast app...and there are no apparent errors in the logs...and i have not noticed any other locast streams having issues.

any ideas?

What error is shown for the stream in the dvr logs?

FYI... I have been using LOCAST in LA for some time now. I have had a couple issues but for the most part (and for some time now) it has worked very well. In particular KTLA has been working very well. My wife and I do not watch it often but my daughter-in-law loves that channel and they have it on for hours every day (morning) remotely because Hulu Live and others do not carry it. Channels Developers were kind enough to add LA-KTLA TVE 6974 prior to supporting LOCAST which we were using until LOCAST. It is 24/7 news where the normal KTLA is about 80% news (all morning news). You may want to try it when you have a problem with the LOCAST KTLA.

Right now here:
Activity
Watching ch5903 KTLADT from 192.168.11.39 <==== local
Watching ch5903 KTLADT from 192.168.11.239 <==== remote

none, that's the weird part. it shows the opening and closing of the stream, but it just doesn't play...it freezes immediately and the spinning circle comes up.

thanks, but none of that information is at all relevant to this issue. i agree that locast has worked well for the most part, but that does not mean there haven't been any issues and also does not mean that issues that do exist (like this one) shouldn't be looked into.

Please post the logs that do appear.

Had device are you watching from?

2020/01/02 12:54:02 [TNR] Opened connection to LOCAST-803 for ch5913 KCALDT [transcode=none]
2020/01/02 12:55:11 [TNR] Closed connection to LOCAST-803 for ch5913 KCALDT
2020/01/02 12:55:22 [TNR] Opened connection to LOCAST-803 for ch5904 KTLADT2 [transcode=none]
2020/01/02 12:55:37 [TNR] Closed connection to LOCAST-803 for ch5904 KTLADT2
2020/01/02 12:55:40 [TNR] Opened connection to LOCAST-803 for ch5903 KTLADT [transcode=none]
2020/01/02 12:55:46 [TNR] Opened connection to LOCAST-803 for ch5904 KTLADT2 [transcode=none]
2020/01/02 12:55:47 [TNR] Closed connection to LOCAST-803 for ch5903 KTLADT
2020/01/02 12:55:53 [TNR] Opened connection to LOCAST-803 for ch5905 KTLADT3 [transcode=none]
2020/01/02 12:55:56 [TNR] Closed connection to LOCAST-803 for ch5904 KTLADT2
2020/01/02 12:56:01 [TNR] Opened connection to LOCAST-803 for ch5909 KABCDT3 [transcode=none]
2020/01/02 12:56:03 [TNR] Closed connection to LOCAST-803 for ch5905 KTLADT3
2020/01/02 12:56:31 [TNR] Opened connection to LOCAST-803 for ch5913 KCALDT [transcode=none]
2020/01/02 12:56:36 [TNR] Closed connection to LOCAST-803 for ch5909 KABCDT3
2020/01/02 12:56:45 [TNR] Opened connection to LOCAST-803 for ch5915 KTTVDT [transcode=none]

this particular instance was from a fire stick 4k, but it also happens often on our android tv box.

What about if you try playing from the web UI?

next time i see it happen i'll try that. right now it seems to be working (that's the other frustrating part, it's not an all-the-time occurrence). i've edited my previous comment to reflect that it happens often but not all the time.

Okay thanks. Next time you can also try recording from the channel which will cause more log messages about the underlying issue

even more frustration...web UI works, fire tv is frozen. i set up a recording and tried to watch the recording, when doing that both web UI and fire tv are frozen.

still nothing in the log that looks out of the ordinary...

2020/01/06 21:41:15 [TNR] Opened connection to LOCAST-803 for ch5905 KTLADT3 [transcode=none]
2020/01/06 21:41:49 [TNR] Sharing existing connection to LOCAST-803 for ch5905 KTLADT3 (clients=2, len=0)
2020/01/06 21:41:51 [HLS] Probed live stream in 1.8416681s: h264 704x480  5242880bps
2020/01/06 21:41:51 [HLS] Starting transcoder for channel 5905 from 192.168.88.70 (encoder=h264_mf, resolution=, deinterlacer=blend, bitrate=10000)
[h264_mf @ 00000000006fe880] stream format change
[mpegts @ 000000000061bd40] DTS 66000 < 72000 out of order
2020/01/06 21:41:58 [HLS] Stopping transcoder session ch5905-dANY-ip192.168.88.70 (out: 6.281311s, finished: false)
2020/01/06 21:42:38 [DVR] Starting job 1578373020-ch5905 Court TV Trial Coverage on ch=[5905]
2020/01/06 21:42:38 [DVR] Waiting 4h44m21.4268556s until next job 1578392820-35 Mork & Mindy
2020/01/06 21:42:38 [TNR] Sharing existing connection to LOCAST-803 for ch5905 KTLADT3 (clients=2, len=0)
2020/01/06 21:42:38 [DVR] Recording for job 1578373020-ch5905 from LOCAST-803 ch5905 into "TV\Court TV Trial Coverage\Court TV Trial Coverage 2019-09-23 2020-01-06-2142.mpg" for 2h20m21.4268556s
2020/01/06 21:42:38 [DVR] Refreshing metadata for Court TV Trial Coverage (17423365)
2020/01/06 21:42:39 [IDX] Generating video index for job 1578373020-ch5905
2020/01/06 21:45:56 [TNR] Sharing existing connection to LOCAST-803 for ch5905 KTLADT3 (clients=2, len=0)
2020/01/06 21:45:59 [HLS] Probe failed for live stream after 3.4049313s and 0 bytes
2020/01/06 21:45:59 [HLS] Starting transcoder for channel 5905 from 192.168.88.70 (encoder=h264_mf, resolution=, deinterlacer=blend, bitrate=10000)
[h264_mf @ 0000000002b32700] stream format change
[mpegts @ 000000000061bd40] DTS 8590003592 < 8590018592 out of order
2020/01/06 21:46:04 [HLS] Stopping transcoder session ch5905-dANY-ip192.168.88.70 (out: 5.333311s, finished: false)

Can you email us that recording to [email protected]

that might be tough, the recording is almost a gig. i can put it on my cloud storage and send a link, if that'll work...

Sure, or use send.firefox.com

didn't even know that was a thing...uploading it now. trying to, anyway...it seems to be stuck at 0%.

edit: nvm, it's moving. didn't realize it was just that slow.

sent!

1 Like

Wow. This file was very corrupted. Can you look in your logs for a line that starts with:

[MTS] Statistics for Court TV Trial Coverage 2019-09-23 2020-01-06-2142.mpg: 

and send what it says?

which logs am i looking at? the one i think it is, the file is almost half a gig (just the logs). i can't get any apps to open it...

I've had pretty good luck with vi/vim for large log files. You may also want to try looking at only the first or last XXXX lines by using head/tail, and then piping it into the editor.

(For example:

tail -n 5000 channels-dvr.log | vi -

will send only the last/latest 5,000 lines to the editor, and

head -n 5000 channels-dvr.log | vi -

will send the first 5,000 lines to the editor.)

yeah, even vim wouldn't load it (i thought the same thing and already tried it). i'll try tailing it and see if that works...