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...
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...
You should be able to use:
grep channels-dvr.log "Statistics for Court TV Trial"
to find it.
I've had some problems with grep and the Channels log in the past, as sometimes it reports that the log is a binary file and it won't operate on it. It's for that specific reason that I mentioned vi/vim.
no results when grepping channels-dvr.log for that phrase
Did you have this issue with other recordings as well?
no, it's just those two channels that i've noticed. i only did the recording based on the suggestion above to try a recording to see if that would generate further logs. those two subchannels on locast are the only ones i've noticed this happening on...
Do those play just fine from the locast website or app?
Could you go to the recording you sent me and select View Recording Log and zip that and send it to support? It will definitely be big.
yup, fine from both. also will play fine from the channels web UI, they only freeze in the android/fire stick app occasionally (not all the time, which makes it even more frustrating). recording is the one that freezes in both the app and the web UI.
i'll zip the log and send it over ASAP.
i can just grab the recording log file from the actual DVR directory and send it that way, right? i don't have to wait for the web to render it...
interestingly enough, right now it's playing fine on the locast website but not the locast app on my roku. on roku, that particular channel is pixelated...on the locast web UI, it plays but there's another audio track laid over top of it. i can hear the words that are going with the guys talking on screen, but very faintly.
that being said, there have been times over the past few weeks where the stream did in fact play perfectly in both locast app and web UI, and channels was still having issues with it. last night being one such time.
edit: it's happening right now, but with KTLA-DT2. locast web and roku app both play it fine, channels hangs...but the reverse of what was happening last night. channels hangs on the web app, but the fire tv app plays the stream fine.
this is incredibly frustrating. the seeming randomness of it makes it very tough to run this down (i'm a programmer by day, so i feel the pain here)...
Yes. It's under Logs/recording/ in your DVR directory.