No, everything else is happy with "Sign in for me", so I didn't want to screw with that setting.
wimp. don't be scared! working great over here. you are the one that made me add that anyway 
might wanna wait for next version - I am adding a feature so you can sign into every TVE with unique creds (or still use shared one like current).
Hey @KineticMan
It just so happens that I spun up a secondary fastchannels docker on a linux machine just yesterday and tried out the cox/spectrum TVE phone sign in function. It was a little funky , but worked!! I noticed in some cases the splash screens didnt match the actual expected channel that I thought I was authorizing, but it still worked pretty well. I did them all one by one starting with discovery. I did get authorization with NBC as well. I could not verify NBC universal channels using the fastchannels built in guide because of DRM issues. I tried loading the links into a chrome browser and playing with the secure content setting, but they wont play. But I did get past the authorization phase...... using the phone sign in method!!
I got myself into a pickle and could use help getting out of it. How do I "UNlock All" after I clicked this in the Default Feed? All my enabled channels are added to other feeds with my custom channel numbers.
I thought clicking Lock All in the Default Feed would lock those numbers and all other numbers in other feeds. It did not. It wiped those out.
And now I am not allowed to undo that action and unlock the channels. Nor am I allowed to re-apply my custom channel numbers with the Save + Reset Channel Numbers buttons in each respective feed.
KineticMan or Anyone Else who knows how, Please help this schmuck out and help me unlock the channel number locks and get myself back to operating with custom channel numbers again. I have a multitude of recordings scheduled that depend on particular channel numbers. And all those are now orphaned and won't find the numbered channel feed when the time comes.
Much thanks.
Oh, didn't even think of that! Whew, that saved my bacon! Thank god for your defensive planning and programming to put automated backups into the system's operation by default (unless I set it up manually and forgot about it, lol).
I may have actually done some work after 3:30am last night (insomniac here) and I know I did some this morning. But who cares. I'll redo those actions.
A Big Thank You!
One more request for guidance here. If I'm configured like this...
Where some, a few, not a lot of channels are configured in multiple feeds, Should attempting to use this again and click "Lock All" in the individual feeds but not ever Default to lock those numbers I have configured in Series / Pass schedules? Because while that might lock the 7601 - 8759 channel numbers, any channel in multiple feeds would get locked to one (the first I lock) but not the other feed? In addition the 11,111 and up Default channel numbers would get wiped out too?
I ask as some damage has been done to my Passes as the channel numbers have changed since the restore. And I'm looking to avoid that going forward. I guess having multiple Channel Numbers applied and locked to a Channel would be helpful.
Thanks again. BTW, send me a way to donate to your effort via PM here if there isn't something published publicly already I can click thru. I really appreciate this utility that I not only utilize in Channels but in my Emby instance as well. And want to support it financially too as I have the other two.
good question.. I'm like you and like multiple different feeds. I don't have a ton of channum locked, but I've done it from the Feed Editor and just edited the specific channel I wanted locked.
@chDVRuser you've been quiet for awhile - you ever mess with the Channum lock feature?
and for the donation, I appreciate the offer but its not necessary. I'm doing this for my own hobby and all I ask is people is to be kind and helpful to others on here!
Like before, excellent suggestion. I should only concern myself with locking channels that I have Series Passes recordings setup or commonly Watch/Record from in Emby or Channels. Thnx for that.
edit: tho damned if I can figure out how to lock just one channel number.
Ahh, I see now that that is invoked if I change a channel number. But how do I lock it if I want to maintain the number it is already set to?
There may be need for a refactoring in the UI here. Because for example I want channel Electric Now that I have set to 7876 to get locked. If I prefix a 1 before that in the entry field to make it 17876 and hit enter, I see the dialog pop-up to ask me about locking it.
But I clicked cancel, because having gotten burned with my global channel lock action earlier today I don't know if that will become immutable after, Disallowing me from changing it back to 7876 and then re-locking it.
If I manually lock it via this technique am I allowed to manually unlock it, change the number back, and re-lock it? Thanx.
got ya - let me look into this more and get back to you.. sounds like needing some UX work.
Curious
Would fastchannels handle the "are you still watching" prompt with the directv app on a tv stick?
Doesn’t use the DIRECTV app so it isn’t an issue.
Are you running Apple TVs and sticks on the same instance of ah4c, by any chance?
No. ah4c is written around the idea that virtual tuners in its pool are interchangeable. Running multiple instances of ah4c is no problem however, so one can be setup for ADB-based devices, and the other for pyatv devices.
But at least one would have to be run that is not connected to FC, then, as current FC only supports one AH4C server, correct?
Yes that's true, but FC doesn't work with pyatv devices anyway, only ADB.
My Docker Desktop on Windows 11 Pro wants to update to a new version. Is that any problem with FastChannels (which is the only thing I use it for right now), or should I not let it update?
I don’t see any reason not to let it. Won’t harm FastChannels.
1 Like
Docker Desktop has a fairly high tempo for updates. There's probably a new version every 2-3 weeks. It's certainly not required to install every version, but on the other hand, if one were to hold off for a number of months -- you'd be pretty far behind what's current.
WSL is typically updated every couple of months, and that needs to be done separately from Windows too. The same with whatever Linux distro you have installed. So, there's something of an ecosystem with these, that's really not covered by the standard Windows update process.
1 Like