Pluto TV connectivity flaky over the last week

Playground Custom Channels
#1

Has anyone else noticed any issues watching Pluto TV through Channels in the last 1-2 weeks? Generally it's pretty solid for me, but lately I can only watch a couple of minutes before it keeps buffering and finally the connection fails.

If I watch Pluto TV directly (either through the website or their app), things work fine, so it seems to be some interaction with Channels.

I have moved house in the last 2 weeks, so potentially it's an ISP issue, however the fact that it works just fine via the native apps, seems to suggest something else is going on.

Any similar experiences or any pointers on how I can troubleshoot this?

Thanks!

EDIT: Here are some logs for a channel that stopped after a few minutes.

2024/06/10 10:41:24.086798 [M3U] stream timestamps: forever-kids: start_at=2024-06-10T10:41:23+12:00 end_at=2024-06-10T10:41:43+12:00 live_delay=15s
2024/06/10 10:41:24.087102 [TNR] Opened connection to M3U-Pluto for ch9389 Forever Kids
2024/06/10 10:41:24.087102 [HLS] Starting live stream for channel 9389 from 100.93.56.73 (bitrate=3321kbps)
2024/06/10 10:41:34.147951 [ERR] Probe failed for live stream after 10.0601783s and 0 bytes
2024/06/10 10:41:35.408454 [HLS] ffmpeg: ch9389-dANY-ip100.93.56.73-remux:  [hls @ 00000000031e5880] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2024/06/10 10:41:35.755976 [HLS] Session ch9389-dANY-ip100.93.56.73 started in 11.6688746s
2024/06/10 10:41:36.890736 [HLS] Probed live stream in 295.4168ms: h264 1280x720 progressive 2481360bps
2024/06/10 10:41:36.955362 [ENC] Starting encoder for ch9389 in D:\Media\ChannelsDVR\Streaming\ch9389-dANY-ip100.93.56.73-2151260570\encoder-1-4204181438 at 1 (0.066667) (encoder=remux, codec=, acodec=, resolution=, deinterlacer=, bitrate=6000, segment_size=0.01)
2024/06/10 10:45:53.594674 [HLS] ffmpeg: ch9389-dANY-ip100.93.56.73-remux:  [mpegts @ 000000000262b640] New data stream 0:2 at pos:85101584 and DTS:265.76s
2024/06/10 10:46:33.869830 [ENC] No segments have been generated in 20.1101189s. Stopping transcoder.
2024/06/10 10:46:34.044925 [ENC] Encoder stopped for ch9389 in D:\Media\ChannelsDVR\Streaming\ch9389-dANY-ip100.93.56.73-2151260570\encoder-1-4204181438 after encoding 1 to 56
2024/06/10 10:46:34.358135 [HLS] Probed live stream in 309.4788ms: h264 1280x720 progressive 2501978bps
2024/06/10 10:46:37.447740 [ENC] Starting encoder for ch9389 in D:\Media\ChannelsDVR\Streaming\ch9389-dANY-ip100.93.56.73-2151260570\encoder-57-2386402917 at 57 (270.826667) (encoder=remux, codec=, acodec=, resolution=, deinterlacer=, bitrate=6000, segment_size=0.01)
2024/06/10 10:46:37.448250 [HLS] Couldn't generate stream playlist for ch9389-dANY-ip100.93.56.73: Playlist has not been updated in 23.8729299s
2024/06/10 10:46:37.448787 [HLS] Stopping transcoder session ch9389-dANY-ip100.93.56.73 (out=4m40.712s finished=false first_seq=1 last_seq=58)
2024/06/10 10:46:37.470345 [ENC] Stopped encoder for ch9389 in D:\Media\ChannelsDVR\Streaming\ch9389-dANY-ip100.93.56.73-2151260570\encoder-57-2386402917 after starting from 57 without encoding any segments
2024/06/10 10:46:52.147335 [TNR] Closed connection to M3U-Pluto for ch9389 Forever Kids
2024/06/10 10:46:52.147335 [SNR] Buffer statistics for ch9389 Forever Kids: buf=3%,0%-100% drop=3%
2024/06/10 10:46:52.147335 [SNR] Streaming statistics for ch9389 Forever Kids: timeouts=2 segment_timeouts=2 playlist_timeouts=0
2024/06/10 10:46:52.844602 [HLS] Stopping transcoder session ch9389-dANY-ip100.93.56.73 (out=0s finished=false first_seq=0 last_seq=-1)
2024/06/10 10:46:53.923691 [M3U] stream timestamps: forever-kids: start_at=2024-06-10T10:46:52+12:00 end_at=2024-06-10T10:47:12+12:00 live_delay=15s
#2

What Pluto source are you using? Have you tried a different one?

The errors Playlist has not been updated in 23.8729299s and timeouts=2 segment_timeouts=2 playlist_timeouts=0 means the stream playlist stopped getting updated.

Could be the source, your DNS, the CDN you're using to access the source, many things could cause that.

#3

I'm using https://nocords.xyz/pluto/playlist.m3u, I haven't tried a different one yet.

Does the playlist need to be constantly updated? What other information would help to troubleshoot?

Thanks for your reply

#4

Yes, the stream playlist containing the segments does.
The master playlist (that points to the stream playlists) usually doesn't get updated.

That would be up to the developers if they want to.
You could record the channel and then view the debug recording log, which will be quite large, looking for errors in there (search for err=).

You can view the debug recording log by finding the recording and choose :gear: Options > View Debug Log

Screenshot Channels Debug Recording Log
Screenshot Channels Debug Recording Log851×466 27.4 KB

#5

Is it possible to extend the tune timeout? It appears to be 12s. Perhaps if the timeouts were a bit longer I'd be able to watch it. As I say, I can watch it directly from the pluto.tv website. All used to be fine for me until I recently moved, and it seems I have rather poor international bandwidth in my new location.

[HLS] Couldn't generate stream playlist for ch9030-dANY-ip100.93.56.73: HLS: 901 Tuner Unreachable: Could not tune to ch9030 after 12s

More logs

2024/07/19 16:57:07.891796 [HLS] Couldn't generate stream playlist for ch9030-dANY-ip100.93.56.73: HLS: 901 Tuner Unreachable: Could not tune to ch9030 after 12s
2024/07/19 16:57:07.891796 [HLS] Stopping transcoder session ch9030-dANY-ip100.93.56.73 (out=0s finished=false first_seq=0 last_seq=-1)
2024/07/19 16:57:07.892312 [TNR] Closed connection to M3U-Pluto for ch9030 TV Land Drama
2024/07/19 16:57:07.894500 [ERR] Probe cancelled for live stream after 8.2879318s and 0 bytes
2024/07/19 16:57:07.907991 [SNR] Buffer statistics for ch9030 TV Land Drama: buf=0% drop=0%
2024/07/19 16:57:07.907991 [SNR] Streaming statistics for ch9030 TV Land Drama: timeouts=0 segment_timeouts=0 playlist_timeouts=0
2024/07/19 16:57:16.239435 [M3U] stream timestamps: tv-land-drama: start_at=2024-07-19T16:57:10+12:00 end_at=2024-07-19T16:57:30+12:00 live_delay=15s
2024/07/19 16:57:16.239435 [TNR] Opened connection to M3U-Pluto for ch9030 TV Land Drama
2024/07/19 16:57:16.239435 [HLS] Starting live stream for channel 9030 from 100.93.56.73 (bitrate=3321kbps)
2024/07/19 16:57:22.852096 [HLS] Couldn't generate stream playlist for ch9030-dANY-ip100.93.56.73: HLS: 901 Tuner Unreachable: Could not tune to ch9030 after 12s
2024/07/19 16:57:22.852616 [HLS] Stopping transcoder session ch9030-dANY-ip100.93.56.73 (out=0s finished=false first_seq=0 last_seq=-1)
2024/07/19 16:57:22.853155 [TNR] Closed connection to M3U-Pluto for ch9030 TV Land Drama
2024/07/19 16:57:22.855431 [ERR] Probe cancelled for live stream after 6.6154141s and 0 bytes
2024/07/19 16:57:22.861754 [SNR] Buffer statistics for ch9030 TV Land Drama: buf=0% drop=0%
2024/07/19 16:57:22.861913 [SNR] Streaming statistics for ch9030 TV Land Drama: timeouts=0 segment_timeouts=0 playlist_timeouts=0
2024/07/19 16:57:30.526712 [M3U] stream timestamps: tv-land-drama: start_at=2024-07-19T16:57:27+12:00 end_at=2024-07-19T16:57:47+12:00 live_delay=15s
2024/07/19 16:57:30.527227 [TNR] Opened connection to M3U-Pluto for ch9030 TV Land Drama
2024/07/19 16:57:30.527227 [HLS] Starting live stream for channel 9030 from 100.93.56.73 (bitrate=3321kbps)
2024/07/19 16:57:39.879154 [HLS] Couldn't generate stream playlist for ch9030-dANY-ip100.93.56.73: HLS: 901 Tuner Unreachable: Could not tune to ch9030 after 12s
2024/07/19 16:57:39.879154 [HLS] Stopping transcoder session ch9030-dANY-ip100.93.56.73 (out=0s finished=false first_seq=0 last_seq=-1)
2024/07/19 16:57:39.879661 [TNR] Closed connection to M3U-Pluto for ch9030 TV Land Drama
2024/07/19 16:57:39.880211 [ERR] Probe cancelled for live stream after 9.3528249s and 0 bytes
2024/07/19 16:57:39.894863 [SNR] Buffer statistics for ch9030 TV Land Drama: buf=0% drop=0%
2024/07/19 16:57:39.894863 [SNR] Streaming statistics for ch9030 TV Land Drama: timeouts=0 segment_timeouts=0 playlist_timeouts=0
2024/07/19 16:57:48.927909 [HLS] Stopping transcoder session ch9030-dANY-ip100.93.56.73 (out=0s finished=false first_seq=0 last_seq=-1)
2024/07/19 16:57:54.432345 [ERR] Failed to start stream for ch9030: M3U: Could not fetch playlist from cfd-v4-service-channel-stitcher-use1-1.prd.pluto.tv: Get "https://cfd-v4-service-channel-stitcher-use1-1.prd.pluto.tv/stitch/hls/channel/5d40bebc5e3d2750a2239d7e/master.m3u8?advertisingId=&appName=web&appStoreUrl=&appVersion=unknown&architecture=&buildVersion=&clientTime=0&deviceDNT=0&deviceId=7218fd6f-458b-11ef-8b3c-48210b35b6fc&deviceMake=Chrome&deviceModel=web&deviceType=web&deviceVersion=unknown&includeExtendedEvents=false&serverSideAds=true&sid=d0400b59-2f7f-4107-a5ab-ac522fd347e2&userId=": unexpected EOF
#6

Have you tried opening the stream url for that channel in VLC?

#7

I hadn't tried that, just gave it a go. Let me know if I did it right. I went into Channels DVR sources, opened the Pluto settings and then downloaded the playlist.m3u file, searched through that for "TV Land Drama" and then copied the URL into VLC.

It opened it up pretty quickly and played for 5-10 seconds. I'm not sure if it should have continued playing or not. EDIT: I tried it using my mobile as a hotspot (which is a different provider to my broadband), and it works fine and continues to play, so I answered my own question there :slight_smile:

This was the URL - https://cfd-v4-service-channel-stitcher-use1-1.prd.pluto.tv/stitch/hls/channel/5d40bebc5e3d2750a2239d7e/master.m3u8?advertisingId=&appName=web&appVersion=unknown&appStoreUrl=&architecture=&buildVersion=&clientTime=0&deviceDNT=0&deviceId=7abb7e32-4655-11ef-a540-8b9d3ee54ace&deviceMake=Chrome&deviceModel=web&deviceType=web&deviceVersion=unknown&includeExtendedEvents=false&sid=478f18cd-27a4-4873-bd82-38f21411c3b2&userId=&serverSideAds=true

#8

Try changing the DNS server your Channels DVR uses.
Popular ones are quad 1, 8 and 9 (1.1.1.1, 8.8.8.8 and 9.9.9.9)

#9

I use a DNS proxy service. I'm in New Zealand and we don't have access to Pluto TV, which means I can't change DNS.

I'm pretty comfortable that the issue is my ISP's international capacity, so I was hoping there might be a way to increase the Channels timeout.

1 Like
#10

No, we won't be increasing the timeouts. They're the longest they can reasonably be and have the rest of the system function. If a stream hasn't returned an m3u8 or the first segments haven't been able to be downloaded in 12 seconds, nothing is going to work right.

It's likely there's something going wrong for it to have taken that long.

#11

Thanks for the reply @eric , I wasn't suggesting you alter your timeouts globally, I was asking if there is any kind of advanced configuration setting that would allow me to adjust the timeout on my setup.

I know 12 seconds is way too long, and I know it's an issue with my ISP. But I also know it works via the pluto.tv website, so I was hoping as a temporary workaround I might be able to increase the timeout - just until I get the underlying issue resolved.

#12

It's not possible to increase the timeouts.

It sounds like the website is also stalling after 5-10s of playback for you?

1 Like
#13

What I'm seeing is most of the time I can successfully watch pluto tv via their website or app. Using the chrome dev tools I can see that it's able to switch to the lower resolution files, and work up to the higher res, but as soon as things are too congested it switches back to the lower res. I'm not sure if Channels can do the same kind of thing?

Only sometimes will Channels be able to play a pluto tv channel. I 100% know its an issue with my ISP which has really poor international bandwidth, and at different times of the day it's more congested than others.

#14

fyi - im having same thing in Kodi using my Pluto playlists.
I suspect Pluto have changed something and we need to change our methods for generating the streams.
https://forum.kodi.tv/showthread.php?tid=378151

Someone did say the other pluto addon works. That doesnt use pre-scraped streams but generates them in the add-on itself (unique stream per user)

#15

That's interesting Matt - could possibly be related to what's happening for me, but it doesn't seem to quite fit.

I have trouble even with the native pluto.tv website, and for me it's definitely related to my ISP. Works ok when I use my mobile hotspot. However I haven't been able to test my channels setup via the hotspot - so maybe it is a different issue.

I figured if it was a wider issue I'd see things popping up in the pluto for tv nocords thread, that always seems pretty active.

#16

No issues with Pluto TV here. Either in Channels or the native app/website.

2 Likes
#17

Same here. I'm using the other container tho (the joagomez one) so maybe that helps. I used to use the nocords one until recently.

1 Like
#18

@tmm1 how does Channels decide which stream to use? Can I influence this decision at all?

Here is a sample .m3u8 file (the star trek channel):

#EXTM3U
#EXT-X-MEDIA:TYPE=SUBTITLES,GROUP-ID="subs",NAME="English",DEFAULT=NO,FORCED=NO,URI="subtitle/en/playlist.m3u8?terminate=false&sid=c1f586df-6004-4a95-80aa-87821ece83a4&deviceDNT=0&deviceModel=web&deviceVersion=unknown&serverSideAds=true&appName=web&deviceId=c788c396-4eed-11ef-996e-7312bd25222a&appVersion=unknown&deviceType=web&deviceMake=Chrome",LANGUAGE="en"
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=1042180,SUBTITLES="subs"
1042180/playlist.m3u8?terminate=false&sid=c1f586df-6004-4a95-80aa-87821ece83a4&deviceDNT=0&deviceModel=web&deviceVersion=unknown&serverSideAds=true&appName=web&deviceId=c788c396-4eed-11ef-996e-7312bd25222a&appVersion=unknown&deviceType=web&deviceMake=Chrome
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=1577180,SUBTITLES="subs"
1577180/playlist.m3u8?terminate=false&sid=c1f586df-6004-4a95-80aa-87821ece83a4&deviceDNT=0&deviceModel=web&deviceVersion=unknown&serverSideAds=true&appName=web&deviceId=c788c396-4eed-11ef-996e-7312bd25222a&appVersion=unknown&deviceType=web&deviceMake=Chrome
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=2294080,SUBTITLES="subs"
2294080/playlist.m3u8?terminate=false&sid=c1f586df-6004-4a95-80aa-87821ece83a4&deviceDNT=0&deviceModel=web&deviceVersion=unknown&serverSideAds=true&appName=web&deviceId=c788c396-4eed-11ef-996e-7312bd25222a&appVersion=unknown&deviceType=web&deviceMake=Chrome
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=3321280,SUBTITLES="subs"
3321280/playlist.m3u8?terminate=false&sid=c1f586df-6004-4a95-80aa-87821ece83a4&deviceDNT=0&deviceModel=web&deviceVersion=unknown&serverSideAds=true&appName=web&deviceId=c788c396-4eed-11ef-996e-7312bd25222a&appVersion=unknown&deviceType=web&deviceMake=Chrome
#EXT-X-STREAM-INF:PROGRAM-ID=1,BANDWIDTH=640930,SUBTITLES="subs"
640930/playlist.m3u8?terminate=false&sid=c1f586df-6004-4a95-80aa-87821ece83a4&deviceDNT=0&deviceModel=web&deviceVersion=unknown&serverSideAds=true&appName=web&deviceId=c788c396-4eed-11ef-996e-7312bd25222a&appVersion=unknown&deviceType=web&deviceMake=Chrome

In the Channels log I see this:

2024/07/31 15:48:11.547251 [HLS] Starting live stream for channel 9039 from 127.0.0.1 (bitrate=3321kbps)

I'm assuming that it is trying the 4th stream, the one with BANDWIDTH=3321280. Is it possible to make it chose a lower bandwidth? Does it do any kind of adaptive streaming?

Thanks!

#19

Final update on this. I got in touch with the dns proxy guys that I use, and they added an additional domain for pluto tv into their dns proxy. That has improved things greatly for me, it seems that I have better bandwidth to their proxy, so for the most part things are working again.

Thanks all for any help offered!

1 Like