Sounds like a nice vacation.
I have seen on occasion when using multiple clients with tuner sharing ... the buffer sometimes fills up and abruptly ends the stream.
Can you give me an approximate time of when you submitted diagnostics from the client right after this happened?
I have 4 clients running the same show at the moment to see if I can recreate it... I will look at some of the old logs.
2022/01/23 15:11:11.569837 [TNR] Sharing existing connection to 107829D3/0 for ch8.1 KGW (clients=3, len=0)
2022/01/23 15:15:28.413332 [WRN] Buffer for 107829D3 ch8.1 is more than 50% full (clients=3, len=33554888)
2022/01/23 15:15:45.071186 [WRN] Buffer for 107829D3 ch8.1 is more than 75% full (clients=3, len=50331760)
2022/01/23 15:15:46.554404 [SNR] Statistics for ch8.1 KGW: ss=100% snq=100% seq=100% bps=9127609,1598752-14803872 pps=781,150-1268
This is when it picked it up again ....
2022/01/23 15:17:18.768221 [TNR] Sharing existing connection to 107829D3/0 for ch8.1 KGW (clients=3, len=0)
more recent ....
2022/05/23 05:04:31.891905 [WRN] Buffer for 13147C7B ch723 is more than 50% full (clients=3, len=33555064)
2022/05/23 05:05:03.822916 [WRN] Buffer for 13147C7B ch723 is more than 75% full (clients=3, len=50332596)
2022/05/23 05:05:29.395063 [WRN] Buffer for 13147C7B ch723 is more than 95% full (clients=3, len=63754672)
2022/05/23 05:05:34.763524 [WRN] Buffer for 13147C7B ch723 is more than 99% full (clients=3, len=66437964)
2022/05/23 05:07:07.961826 [SNR] Statistics for ch723 FS1HD: ss=86%,0%-88% snq=98%,0%-100% seq=98%,0%-100% bps=4072420,0-7318464 pps=350,0-633 err=3% sigerr=1% neterr=2%
2022/05/23 05:07:07.962473 [SNR] Statistics for ch723 FS1HD: ss=86%,0%-88% snq=98%,0%-100% seq=98%,0%-100% bps=4072420,0-7318464 pps=350,0-633 err=3% sigerr=1% neterr=2%
2022/05/23 05:07:07.974293 [SNR] Statistics for "TV/First Things First/First Things First 2022-05-23-0429.mpg": ss=86%,0%-88% snq=98%,0%-100% seq=98%,0%-100% bps=4072420,0-7318464 pps=350,0-633 err=3% sigerr=1% neterr=2%
2022/05/23 05:07:07.982836 [TNR] Closed connection to 13147C7B/0 for ch723 FS1HD
@Edwin_Perez I've checked and I don't see any diagnostics submissions from your client devices. There's nothing we can do without seeing those.
1 Like
IIRC, buffer warning errors ([WRN]) are caused by two situations:
- either your server's disk cannot keep up with the incoming data, or
- your network cannot consistently deliver the data to your clients within an acceptable timeframe.
1 Like
Next time if it happens again, I will submit ... I usually watch my morning sports shows in 3 locations... all live.
I thought the tuner sharing buffer is in memory? so why would it be disk... so lets eliminate that.
Because for recording or transcoding the buffer is written to disk; if the disk cannot keep up with data filling the buffer, the buffer gets full. The buffer is in memory, recordings and the streaming cache are not.
That is not my problem as it is livetv ... but thanks for the input.
Eric thank you for taking time to respond to our desires and explain (VIOLENTLY MURDER) why my dreams are unlikely to happen. Lol.
I also really like the two topic titles i quoted. But i assure you my solution is easy . . . For me.
So @eric here is my plan. I tell you I want the worlds most bad ass DVR. Thats my whole plan. Its easy for me. I don't have to do any of the work. Ummm. . . Eric shouldn't you be working right now?
One thing is for sure ... if it were 'easy' someone else would already be doing it. Right?!?!?
No, definitely not true. The basis of your understanding is wrong. Other DVRs can do this because they were built that way from the start (server-focused). Channels doesn't work that way because it prioritized the client above the server to give users a great viewing experience. It was viewing-focused, not DVR-focused. (Channels' DVR features only came after it was established as a first-class TV client.)
If you really want server-based functionality, other DVRs offer it: SageTV, MythTV, Tvheadend, etc.
(It is beyond-trivial to change how things work. Any user claiming that what they want is easy likely has no real understanding of how things work, especially across UX concerns.)
Thanks for the reply. I have plenty of USB-3 stick drives around so I'll give it a try.
I was incorrect. Shield tube has SD slot. Tube has no USB.
Silly me, for thinking a piece of software called Channels DVR Server would act like a ... server. lol
1 Like
Good One ....
Yeah, I know; I have 2 Pro's and a Tube. I just figured you made a typo. The important info was the feedback about using adopted storage to increase the buffer. I should have a chance to try it out tomorrow. The grandkids have been needing a lot of attention lately.
Seems like the pause limitations can be mitigated by using Record. If you want to ensure that you see the end of a live program, then just start recording instead of pausing. It is only a few extra keystrokes and you can setup an extra 2 hours if desired. Why would you rely on the pause buffer that can be gone by an accidental keypress?
I see one problem with recording a program that you are also watching live, it requires another free tuner. which may be a problem for some. Enabling tuner sharing doesn't help for this.