I'm trying to play a recording on my apple tv and getting this every time. Any idea?
I have my server on a Synology 920+.
The connection to the Channels DVR server had a problem. Press play to try again. (Timeout)
Check the dvr log
1 Like
2023/06/08 21:21:08.499469 [TNR] Cancelling stream M3U-MLB ch781.1 after no data was received for 2m0s
2023/06/08 21:21:13.820314 [SNR] Buffer statistics for "TV/LIVE New York Mets @ Atlanta Braves/LIVE New York Mets @ Atlanta Braves 2023-06-08-1820.mpg": buf=0% drop=0%
2023/06/08 21:21:15.570244 [SNR] Buffer statistics for "TV/LIVE New York Mets @ Atlanta Braves/LIVE New York Mets @ Atlanta Braves 2023-06-08-1820-1697.mpg": buf=0% drop=0%
2023/06/08 21:21:17.786872 [MTS] Statistics for "TV/LIVE New York Mets @ Atlanta Braves/LIVE New York Mets @ Atlanta Braves 2023-06-08-1820.mpg": skipped=0 unhandled_packets=0 discontinuity_detected=0 transport_errors=0 invalid_pts=0 invalid_dts=0 saw_pcr=true saw_pmt=true highest_pts=10753.583600
2023/06/08 21:21:19.311662 [MTS] Statistics for "TV/LIVE New York Mets @ Atlanta Braves/LIVE New York Mets @ Atlanta Braves 2023-06-08-1820-1697.mpg": skipped=0 unhandled_packets=0 discontinuity_detected=0 transport_errors=0 invalid_pts=0 invalid_dts=0 saw_pcr=true saw_pmt=true highest_pts=10756.753433
2023/06/08 21:21:36.358832 [TNR] Closed connection to M3U-MLB for ch777.1 New York Mets
2023/06/08 21:21:36.358874 [DVR] Error running job 1686266400-78 LIVE: New York Mets @ Atlanta Braves: Could not fetch playlist: http://192.168.50.143:8080/playlist/NYM: Get "http://192.168.50.143:8080/playlist/NYM": net/http: timeout awaiting response headers
2023/06/08 21:21:36.360484 [TNR] Closed connection to M3U-MLB for ch781.1 Atlanta Braves
2023/06/08 21:21:36.360518 [DVR] Error running job 1686266400-70 LIVE: New York Mets @ Atlanta Braves: Could not fetch playlist: http://192.168.50.143:8080/playlist/ATL: Get "http://192.168.50.143:8080/playlist/ATL": net/http: timeout awaiting response headers
2023/06/08 21:21:42.120347 [DVR] Starting job 1686266400-78 LIVE: New York Mets @ Atlanta Braves on ch=[777.1]
2023/06/08 21:21:44.461439 [M3U] stream timestamps: mlb-nym: start_at=2023-06-08T16:49:56-05:00 end_at=2023-06-08T21:21:29-05:00 live_delay=9.555397213s
2023/06/08 21:21:44.461794 [TNR] Opened connection to M3U-MLB for ch777.1 New York Mets
Seems like your docker is not running or unresponsive
Thanks, I tried restarting docker and each of the containers that I have. None of this helped as the issue continues tonight on today's active recording of the MLB game. I submitted diagnostics if this helps:
b725d09b-5659-4bf7-bcf2-445841b2bd73
Here is an odd observation, usually the way I stop a recording in progress is to go to DVR / Schedule and select the show's drop down and click Stop Recording. But today,I couldn't do that. According to this screen (see screenshot) it seems like the game didn't record at all. But it did... It appears in my library and under recordings, etc.
I then tried Trashing the active recording in order to stop the recording, and then went to Settings /Trash and clicked Restore. The game reappeared in my library, and voila, it's playing now! I just don't get what is going on, any advice?
I'm trying to post some of my log, but it doesn't seem like it updated as all since yesterday, and not sure how to refresh it.
Thanks
Seth
It appears that it was still recording, but encountered interruptions.
Search for 502 bad gateway using your favorite search provider to learn more
Thanks for this suggestion. I've read a bit about it and it may be a bit over my head. Is the potential bad connection between my Apple tv and my Synology server on the same network?
Why do you think it would happen only while the recording is in progress?
I was able to watch the recording from last night, this morning, at the same TV and it played just fine.
Sorry for all the questions, just trying to post about my experience, maybe it'll help someone else one day.
I have seen this occasionally. It’s always with the mlb docker. It seems like if it has to many interruptions the dvr goes into a sort of loop and forgets when it’s supposed to stop recording. I’ve seen recordings as long as 16hours on a game. When it gets on this loop the only way to watch the recording is to cancel the recording and then it will play just fine. It is not tvOS specific as it happens on the shield. This is a problem at the server level.
The recording in your screenshot tells the story, it has a duration of 8 hours. I’ve never reported it because it doesn’t happen regularly. I don’t have to trash and restore the recording, simply using my iOS app to stop the recording and waiting 30sec or so will allow it to play on shield or iOS. My server runs on Linux and the docker container runs on a separate machine that also runs Linux.
1 Like
What happened when you clicked on the dropdown arrow?
I usually see either Stop Recording or Delete scheduled job
Sorry I don't remember as the game is deleted now, but it didn't have Stop Recording as that's where I usually go to do that, and was looking for it. The Trash/Restore idea was just an alternate way of stopping the recording that I thought of.
@tmm1 Does this make any sense? It's happening again right now for today's recording. The game started at 1pm and the recording is over, but I can't view the recording, in getting the same error. I basically gave up trying until I tried the other Channels app on my Apple TV and the recording played right away! It continues to not play in the Beta version (currently 6.10.1549)
Hope this helps!
Try experimental mpegts rewriting
Tried it with yesterday's recording, it made no difference. It still says
The Channels DVR Server had a problem. Press play to try again.