Ya, I mentioned the files specifically because I already know the benefits of selfhosting.
i try docker pull Package pluto-for-channels · GitHub and receive in synology ssh and receive Using default tag: latest
Error response from daemon: Head "https://ghcr.io/v2/jgomez177/plex-for-channels.git/manifests/latest": denied
I am really having trouble understanding how to load github to synology containers. Would prefer portainer access but cant figure that out either. Are there are basic instructions on importing github packages to synology containers? I have been searching for hours
See if this helps
Thank you for the response, but after issuing ssh logout for docker and ghcr.io i still get the same denied response.
I had good luck using docker packages, and portainer to update them but having trouble using ghcr.io...
I had the same issue using github.
Watch this:
Synology NAS - SSH access to console via QuickConnect using Docker
I followed these instructions (except I went with a full debian version):
Start Debian container
Enable SSH in Control Panel
double click Debian container select Terminal
In the terminal window
Enter:
ssh youruser@yoursynologyip
Enter your password
sudo -i
Enter your Password
docker pull ghcr.io/jgomez177/pluto-for-channels
type Exit
type Exit
close the Debian window
stop the Debian container
Disable SSH in Control Panel
Create a container for Pluto
There are I am sure other ways to do the same process - SSH into your Synology from a desktop SSH client such as Putty.
1 Like
I'm trying to upgrade from the Maddox Pluto to the jgomez177 Pluto running in Windows 10 Docker. All of the stations appear in my guide, but there is no program information on any channel.
I can play any channel from the Channels Guide.
Docker run is:
Docker run -d --restart unless-stopped --name pluto-for-channels 7779:7777 ghcr.io/jgomez177/pluto-for-channels:latest
Channels URL is set to: http://localhost:7779/pluto/local/playlist.m3u
Stream Format: HLS
Guide Data: http://localhost:7779/epg.xml
What am I doing wrong?
1 Like
Your guide data URL is incorrect:
look at the url hosted at http://localhost:7779 to get the correct URL link
Thank you!
Have you thought about creating your own topic here and putting the latest info in the first post since this topic is for the maddox docker container?
Something in the Playground-Custom Channels category like "Pluto for Channels-joagomez"
Assuming the wrong original air date from Pluto is causing this title to appear with (1974) (1973) using both maddox and jgomez containers.
maddox container epg
<title lang="en">The Longest Yard (1974)</title>
<date>19731230</date>
<episode-num system="original-air-date">1973-12-31T00:00:00.000Z</episode-num>
jgomez container epg
<title>The Longest Yard (1974)</title>
<episode-num system="original-air-date">1973-12-31T00:00:00.000Z</episode-num>
<date>19731231</date>
I believe this is a more basic Pluto metadata issue. Look at the record just above it for Meatballs:
<title>Meatballs</title>
<episode-num system="original-air-date">1978-12-31T00:00:00.000Z</episode-num>
<date>19781231</date>
Notice how the <title> field doesn't have a year baked in like the one you showed for The Longest Yard. Channels is just concatenating whatever is in the <title> field with the year from one of these date fields, probably <date> .
I say this because the Plex container doesn't contain the episode-num system="original-air-date" and it still does the same thing:
2 Likes
I don't know if this is due to a problem with this Docker or a larger issue with Channels... but I have your updated Pluto docker running. For some reason, Buzzr is visible in the list of channels brought in by the docker and I can tune to it in the "All Channels" collection in Channels. I have a Channel Collection setup for Pluto specifically, but for some reason Buzzr is not one of the channels I can add to that channel collection, even when specifically choosing Pluto as my channel source. If I change the source to All Channels in the Channel Collection, I can't add it there either. It doesn't exist in the channel list. Super weird specific problem. @maddox @tmm1 any ideas if it's not due to this specific docker image?
Seems to be there for me.
Now depending on which playlist your are using, there may be a channel-id duplicate, especially with the "maddox compatible" in that the channel-id for buzzr is "buzzr" which would also be the same channel-id as what is in the TVE.
I believe maddox had done some alterations in his code for such duplicates that I did not include. In the first playlist listed I added "pluto-" to all channel-ids to avoid channel-id duplicates
so for
PLUTO LOCAL: channel-id="pluto-buzzr"
PLUTO LOCAL channel-id by "provider"-"id" (i.mjh.nz compatibility): channel-id="pluto-5812bfbe4ced4f7b601b12e6"
PLUTO LOCAL channel-id by "slug" (maddox compatibility): channel-id="buzzr" (Duplicates TVE BUZZR channel-id)
I am using the Maddox-compatible method and have it available in TVE, which may be why I'm missing it. I don't have de-dupes turned on in Advanced, but maybe this is why I'm not seeing it? Should I switch to the non-maddox-compatible list? I kept with Maddox since I was using his container previously.
Simple answer - look in your TVE to add that channel to your collection (channel 6750 is BUZZR) as you would have to rebuild your pluto channel collection if you changed to another playlist type with different channel-ids (as noted by @babsonnexus and why i added some compatibility - but again my "compatibility" isn't perfect as experienced by what you are hitting.)
2 Likes
I see what you are saying, and the answer is "kind of both".
As you said, if you try to add Buzzr to a Channel Collection, the Pluto one does not show as an option (for me, Pluto is 1xxxx stations):
If we look at the @maddox method, we can see the channel-id is pluto-buzzr:
But looking at the @joagomez method, we see it is just buzzr:
This is the exact same name as is used by TVE in Channels:
So it looks like Channels is getting them confused and picking one (TVE) as the overriding option. For a final comparison, if we look at the Tubi m3u (3xxxx for me), we see:
Thus, the difference in channel-id is what matters. As pointed out, Maddox put a manual fix in place to make sure there was no overlap. You can see this in the code (basically, if its on this list, concatenate pluto- to the beginning):
Both the regular and the i.mjh.nz compatible have unique channel-ids, so it would resolve this particular issue:
However, it would open you up to my original problem of destroying your favorite/hide settings on stations and their placement in manual Channel Collections. If you don't mind redoing that, then yes, just go with the regular one. Or, as was highlighted, you can just use the TVE source instead. It really just depends upon your use case and what's most important to you.
3 Likes
This is why with my initial playlist I concatenated all with pluto-. I personally did not want to deal with a bunch of one-offs. However this impacted your existing channels collection - thus the "maddox-compatible" still not wanting one-offs it ended up in this position for Buzzr
1 Like
FYI, the TVE stream is better than Pluto TV's stream:
| Resolution | Video Scan | Frame Rate (fps) | Video Bit Rate (mbps) | Audio Bit Rate (kbps) | |
|---|---|---|---|---|---|
| TVE (ch 6750) | 1920x1080 | Progressive | 29.97 | 4.4 | 129 |
| Pluto TV | 1280x720 | Progressive | 30 | 2.6 | 94 |
4 Likes
Thanks everyone for the insight on this issue!! I really do appreciate the education on how it's labeled on the various services. Also, thanks for pointing out the TVE version is actually better quality. For whatever reason, I thought the Pluto version looked best to my eyes, but I see that actually should not be the case since TVE is higher resolution and bitrate. I'm just worried for the inevitable day that I have to drop Spectrum as my CableCARD provider and seek out another provider that still has Buzzr on TVE.