It the correct version, I put a 6 instead of an 8 on it. I will correct that in the morning. Thanks.
This is a user error not an application error in my opinion. You should always have your Win11 headless server set to auto login to a user account on reboot. You can store the password to enable this.
There's tons of stuff that would break if I didn't have this set.
Maybe I missed something in what you said, the program is set to run on startup and I haven't checked it on reboot.
No, huge security risk
(post deleted by author)
Looks like I can run 2 separate instances of this app now.
Have a 2nd .exe in a different folder, renamed the .exe for good measure,(added a M at the end meaning Mine) to differentiate it in running apps.
Since it auto changes port used now when run. and saves what port it uses. Stays open and seems to be working.
Only issue is that the built in Run at Startup, only codes in startup the original program, at the orginal location. I can just manually add the 2nd instance to startup.
It still starts with Account 2 when the first stream is requested.
I gave it some thought and came to the conclusion it would overcomplicate the simple design of this app. I do have a good idea of how to add this ability though. As soon as I get this to a point where I feel it is done, I will set a webpage up for it and offer a powershell script that will allow it to run in Task Scheduler as well as offer a second PS file to toggle the server off and open the dashboard for edits and then restart the server. I will add an html settings page to the yourip:port so the links can be copied without having to use the dashboard for viewing settings. That way those that are inclined to do so can run it as you described while other users can still enjoy the simplicity of this application.
I just released v1.0.9. This should be the last release for a while. I think I have it where I feel good about it. I am sorry for all the updates so often. I just prefer to make small, incremental changes in case I mess up I can roll back to previous versions and not get lost in the process. I made a few UI changes to the dashboard and added the playlist links to the IP:PORT location.
On a side note, I tried to get my application signed to avoid the untrusted app at install, but my application was denied because my reputation was not strong enough. If you want to help me, Star my project on GitHub if you find it useful. That will improve my reputation and hopefully get me to a point where I can get it signed. Thanks for all your help and support.
Were you able to fix the guide data having wrong dates etc issues?
I didn't see that on my guide. Is it all channels or select ones? The ones I looked at were correct. Also, which region was it in, I use US East and didn't notice it.
Thank you,
Your app as it is could be launched from Task Scheduler with just a few clicks. All that's needed is the ability to set the configuration and having it stick. I think you have most of that setup already from what I'm reading. I'll need to do some testing so see where it's at.
I started on the Powershell scripts to automate the process. Having the playlist on the IP:port should eliminate the need for most dashboard visits. As soon as I test the PS files, I'll put them on GitHub. Thanks for the suggestion. It "should" work fine as a service as is, but there are always little issues that are hard to envision without actually doing it.
Take a look at BBC News and Sky News channels, the show dates are all 12/31/69. Don't think this happened with the old Pluto feed. Also there are no New tags etc. Yes this is US East.
Ok. I'll look into the issue. Thanks.
Well, I'm lost. I just installed 1.0.9, but all I get when I try to watch a Pluto channel, is the "reconnect" error, and then it gives up. First time this has happened on the new version installs.
I think Channels is still looking for the server on Port 7777, and the new instance switched to 7781. I don't know how to get it back to 7777, OR get Channels to see it on 7781.
P.S. Duh, my brain must not be working this morning. All I had to do was change my Channels SOURCE URL to reflect the new port of 7781. SORRY!
I'm all set, and I'm leaving this post for others future reference, even if it makes me look a little dumb, lol.
Hopefully, this is just a issue with his docker solution....but, if not, could mean that DRM may be enabled on all Pluto channels at some point.
OK, I got it sorted. The issue was present in the original Docker version too. Pluto does not return a valid original air date for 24/7 live channels or non-episode content. It sends the Unix Epoch 0 timestamp 1970-01-01T00:00:00.000Z for those programs. I have a work around where when we see the 1970 placeholder, it now drops it and gives a clean display on the guide. I also improved the live content tag detection. I'll have the update built in a little while. It will be v1.1.0 and hopefully finished up. Thanks.
Thanks! You've been awesome with the quick hits on this.
I hope not. If so, we will just pivot to a different FAST provider. I feel like if they were going to go DRM, they wouldn't have been worried about adding limits to it, but who knows.
Pluto offers the most. Plex would be the next best. Samsung, not much. I don’t know about LG and I think there are a few others.
Some channels are offered the same on all of them at least in name but some air different programming or different episodes.
Thanks for all the great updates!