M3u failing sharing connection

M3u using cookie token and ts from one channels server to another channels server. This was all working prior and I’m not sure when it started failing. All the channels in the m3u work except for when the host server is tuned and recording. Mlb docker and the host server can tune to 777 but the client server can’t tune to 777 when host is recording, client server can tune to 789 or any other except 777 with no issue. It also seems like it’s not releasing the channel when I canceled the recording as it still shows sharing connection when the host is no longer tuned to the stream.

2022/09/16 21:57:53.205929 [TNR] Sharing existing connection to M3U-Rim3u for ch777 Kansas City Royals (clients=0, len=0)
2022/09/16 21:57:53.207939 [HLS] Starting live stream for channel 777 from 10.66.66.3 (bitrate=0)
2022/09/16 21:57:53.250183 [HLS] ffmpeg: ch777-dANY-ip10.66.66.3-remux:  pipe:: could not find codec parameters
2022/09/16 21:58:03.248542 [HLS] Probe failed for live stream after 10.04035857s and 0 bytes
2022/09/16 21:58:07.325772 [HLS] Stopping transcoder session ch777-dANY-ip10.66.66.3

Client server diagnostics 4ec31ec4-7372-4391-bed2-590c4a314be5

Host server diagnostics. 0da6d8ae-824f-4071-bc1a-1d143c5bca8c

One note: are your Client and Host DVRs on the same local network (less than 5ms apart)? If not, you'll have a better time using HLS instead of TS for your sharing.

It looks like you've run into a bug that we've seen a couple other reports of so far but haven't gotten a handle on yet. To resolve your immediate issue with watching channel 777, you'll have to restart the "Client server".

Thank you for reporting this. Your diagnostics will be helpful in us figuring out what's going on here.

1 Like

They are not on the same lan but geographicly close. Host has symmetrical gig fiber and the client has 500 down. I don’t really have a way to ping from client to host but I was aware to change to HLS if I had issues but client side has been solid and very fast so I’ve left it Mpeg ts.

This seems to have resolved it for the time. Thanks

Dont know if this helps but here is a screenshot from iPad app when it was failing

I believe that error is unrelated to the underlying issue, but I've made a change to try to suppress that error to help us figure out what is really going on. Thanks for the screenshot.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.