Does not Work ...
Thanks I know you are guide busy but I was testung running 2 Containers with different names but it did not work ....
docker run -d --init -p 5593:5593 --name adbtunerHDHR --restart unless-stopped -v adbtuner_config:/app/.config2 turtletank99/adbtuner
I'm sorry, missed your earlier question.
You should be able to have a mixture of HDHomeRun and other "channels" within one instance of ADBTuner presuming the related apps are on the linked Android devices.
Using a different port for a second container is the right idea, but the alternate host port needs to be mapped to the standard container port, like this: -p 5593:5592
. And, your host volume name needs to be different, not the path in the container like this: adbtuner_config2:/app/.config
I am testing now and have a mixture of URLs that open channels in YTTV, launch apps like Haystack News and TikTok, and now, some channels via the HDHomeRun app, all via the same original adbtuner container. I'm not sure what you're hoping to accomplish differently by having 2 different containers? Because that's not necessary to make this mixture work.
XFINITY Stream APP only Runs on the FIRETV's I use this to Capture HBO Showtime etc using URL.
The only DEVICES that Play DRM Channels from my HDHomeRun Primes are Google Certified devices but these do not Support XFINITY Stream
I am limited to 4 Streams using XFINITY Stream. I would like to use My Primes to tune the 5th Stream. That would cover my DRM Channels.
I cannot have the FireTV devices Trying to tune a DRM Channel from my Primes.
I guess one way of avoiding that is to somehow be able to force a particular stream to only use a specific device. I don't know if that can be done or not.
Setting up a 2nd Instance of the Docker did the Trick Just setup 2 ADB tuners in Channels the First one limited to 4 Streams XFINITY the 2nd HDHR one limited to 1 Stream for now ...
I got the extra ADBtuner container going ... and all is working great.
I've been using ADBTuner for a while with the NBC block of channels (and others) mapped to a range of channels just beyond the end of the YTTV TVE ones (7051+) - I wanted to move the channels back to their original TVE mappings, for example, NBC is at 6000, but when I do, I can't get the guide to populate - I just tried moving NBC only to 6000 via the ADBTuner config page - can someone else verify that this is working? Or is there possibly an issue? (Note: I also have the Gracenote Station ID populated for NBC and I am re-loading the m3u file)
my first guess is:
so, hang tight...
Thanks, I had no idea - I picked a really bad time to try this and do a "Delete and recreate database" because now I have no guide data at all...
Me Too lol but I was able to populate using the HDHomeRun EPG.
Does restoring a database file also restore the guide? I have a backup from a few hours ago
Nevermind: update is available...
This is working well for me, such a cool addition to adbtuner. I tested with two ATSC3 channels, of course the DRM on the other two is preventing playback. And so we wait.
I do admire the ingenuity of this workaround and really appreciate your awesome work on this.
Can confirm it was the extra activity on the package that was the problem. I watched it take care of a who’s watching screen tonight!
Perhaps it’s my imagination, but I do find the Chromecasts “tune” faster than the Fire Sticks.
Thanks so much @turtletank !
I have to use Both Firesticks to record of XFINITY Stream APP and Google Chromecast to record of HDHomerun.
I don't know if this is an ADBTuner issue, or a channels issue, but right now I have about 11 channels setup in my ADBTuner, I got a bunch of NBC app channels, and then some HDHR channels. When I go to create channel collections, and you can select a specific tuner and I select the ADBTuner, I only see a few of my NBC app channels, and none of my HDHR channels. If I go to the guide, all the way at the bottom I do see all of my ADBTuner channels, so I don't know what's going on there.
How do you find the speed between the two? I find the Chromecasts faster, but less reliable (as in I've had a couple of times where the app never launches).