Thank you, I just want the Pluto channels. I would have stayed with pluto-for-channels, but it seems to be having issues pulling guide data recently. I'll manually change the channel numbers so they line up with the old method.
Antenna and TVE use gracenote SeriesID.
Fast Channels use the individual fast providers SeriesID.
If you want them all to match, use gracenote station ID's for your fast channels.
If you go this route, I would be interested to see if it is possible to extract the caption data from Kodi and remux it back into the stream. The major problem with these capture techniques is they do not support closed captions. Either you have captions on and they are burned into the video or you get no captions at all. It’s not great.
2 Likes
Remind me again how to update Fast Channels in Portainer. Thanks!
1 Like
Stop the fastchannels stack.
Go into the Stacks-Editor for fastchannels, and scroll down.
Click Update the stack, and enable the Re-pull and redeploy slider, followed by Update.
Interesting idea. I’ll look into it more. Tnx
Thank you!!! Everything seems to be working and playing live!!!
1 Like
So here's the strange thing. One of the Amazon channels I have enabled is ABC7 Los Angeles. If I play it from the Channels guide (identified by using select sources,), it opens a window in Chrome and plays, then plays in channels. If I do the same thing from FC guide, it complains about not having a secure context. (This is in Firefox).
Just for the heck of it, I tried the same thing in Chrome, and it worked fine! But Firefox works fine via Channels. However, when I try Chrome on my other PC (not the one where Channels, Prismcast, FastChannels are installed, but instead my "daily driver), I get the same errors in Chrome as I do in Firefox.
I did a quick check, and I do have the insecure flags set in Chrome on both PCs.
The PC on which all my servers are installed is Windows 11. My typical client machine is on Windows 10.
ETA: Although in Chrome, playing via Guide, the test-channel plays just fine, the PrismCast setup test returns complete failure:
After the latest results (which were after I'd been away from my PC for a couple hours), although the ABC Los Angeles still played ok, everything else that needed Prismcast started failing also, and Prismcast decided that it had gone offline. That seems to happen often with Prismcast, which continues to be utterly flaky for me.
You may have seen my posts about difficulties on the Prismcast topic, but I haven't received any useful responses there. 
Generally, if I force-kill the process I can get it back running at least some of the time, but not at all reliable.