Random buffering issues just started on all TVE channels again

#1

this is happening again. i had this issue a few weeks ago and it resolved itself randomly, but i'm seeing it again. it only seems to be on tve channels, other sources are fine.

the following is in the log for the locals, but TBS is buffering too and nothing obvious in the logs:

2021/11/07 15:44:43.071984 [WRN] Buffer for M3U-channelsbackend ATT ch2 is more than 75% full (clients=1, len=50364416)
2021/11/07 15:44:50.160746 [TNR] Closed connection to M3U-channelsbackend ATT for ch2 KCBS
2021/11/07 15:44:53.351973 [TNR] Opened connection to M3U-channelsbackend ATT for ch2 KCBS
2021/11/07 15:52:49.757871 [TNR] Closed connection to M3U-channelsbackend ATT for ch2 KCBS
2021/11/07 15:52:51.396627 [TNR] Opened connection to M3U-channelsbackend ATT for ch11 KTTV
2021/11/07 16:31:55.540867 [WRN] Buffer for M3U-channelsbackend ATT ch11 is more than 50% full (clients=1, len=33587200)
2021/11/07 16:31:55.590060 [TNR] Closed connection to M3U-channelsbackend ATT for ch11 KTTV
2021/11/07 16:31:58.275174 [TNR] Opened connection to M3U-channelsbackend ATT for ch11 KTTV
2021/11/07 16:32:10.989386 [TNR] Closed connection to M3U-channelsbackend ATT for ch11 KTTV
2021/11/07 16:32:18.721865 [TNR] Opened connection to M3U-channelsbackend ATT for ch4 KNBC
2021/11/07 16:32:41.971465 [WRN] Buffer for M3U-channelsbackend ATT ch4 is more than 50% full (clients=1, len=33568912)
2021/11/07 16:32:52.387140 [WRN] Buffer for M3U-channelsbackend ATT ch4 is more than 50% full (clients=1, len=33587200)
2021/11/07 16:33:02.089940 [TNR] Closed connection to M3U-channelsbackend ATT for ch4 KNBC
2021/11/07 16:33:05.394770 [TNR] Opened connection to M3U-channelsbackend ATT for ch2 KCBS
2021/11/07 16:33:17.659014 [TNR] Closed connection to M3U-channelsbackend ATT for ch2 KCBS

any ideas? internet speed doesn't seem to be an issue:

Screen Shot 2021-11-07 at 4.38.38 PM
Screen Shot 2021-11-07 at 4.38.38 PM1458×670 149 KB

#2

IIRC the buffer warning messages are in reference to your drive not being able to keep up with the data coming in.

Also, since it looks like you have a different server feeding that instance, you may want to check the logs for the server that is actually initiating the connection to the TVE websites. If those logs don't have any errors, then the problem is clearly within your home somewhere, and not directly related to TVE.

#3

they're on the same box, literally. it's a docker stack with two channels instances running.

#4

I gave up doing that because the back-end TVE server couldn't handle stream interruptions when the front-end server was recording the m3u from the back-end which was tuning the TVE.

#5

huh?

1 Like
#6

I had one docker container with a TVE source only that I called TVE.
I ran another docker container using an m3u source (that I called M3U) which pointed to the TVE docker container.

When the M3U container was recording, it would source it from the TVE container.

#7

also, this wouldn't explain why it's only TVE sources but not anything else having this occasional issue. none of my custom sources have any problems (also coincidentally coming from the same box, just my dizquetv container)...

#8

Can you expound on that? I understand the setup of using a backend/frontend with TVE, but what specifically was going wrong in this scenario? Are you saying that TVE disruptions from the source were not handled well when being fed through the "middle man" backend dvr causing recordings to have issues?

#9

Yes.
It's been too long ago to remember the details, but the TVE server (container w/TVE source) would treat the request from the M3U server (container w/m3u source pointing to TVE container) like a client watching the TVE channel live instead of as a recording being made by the TVE server.
Issues when the TVE connection dropped, timestamp errors and things like that are handled differently for watching TVE Live vs. recording TVE.

Use Channels-DVR as a tuner for Emby
#10

Was your m3u8 in hls or .ts?

#11

I had to lookup my posts since I couldn't remember.
Custom Channels in a Docker container referencing existing TVE source and it looks like it was MPEG-TS.

#12

Curious for those who do this 2 channels server thing, why? What do you get out of it that you wouldn’t normally.

#13

I made a request which ended up getting locked because of controversy.
So I created two TVE servers that serve my purpose.
When a TVE channel airs a series marathon, or a New episode of a Series I record, it may only air each episode twice. I want to make sure I record every airing in case one airing is interrupted or corrupted.

1 Like
#14

the ability to re-order the channels. at least that's why i do it...

1 Like
#15

Gives me the ability to share Tuners/TVE with multiple DVR's. Example, I have a DVR setup for my father, if they are completely separate and we watch the same baseball game then it will use two tuners. By using a "backend" DVR I can create an M3U output for both my DVR and his DVR... Both point the the "backend" and then share the same tuner for that one channel, but all of our recordings remain separate.