Thanks for chiming in bhnf. I am an edge case actually. I use DISPATCHARR in between my sources and CDVR as I like the management and redundancy abilities it provides, hence I didn't share the Channels Source as it doesn't exist in the manner you would otherwise assume it was in.
Here's a screenshot of my sources within DISPATCHARR:
The FDL-ADB did populate channels previously when I did a direct install of FDL (though they didn't work, but the channels populated). In trying to redo this using the OliveTin approach, I've mucked it up differently than it was previously mucked up. Now there doesn't seem to be an ADB.m3u for it even to pull into:
I can go in an correct the link within the existing ADBTuner channels to the correct configuration, but doesn't there need to be a segmentation then at the virtual channel level since it would send different commands for my various sources (Paramount+, Amazon Prime, ESPN+). Said another way, Virtual Channel Lane 1 wouldn't be able to have all 3 sources come through, it would have to be dedicated to just one of those 3 sources. So I should have say CHannels 1-25 dedicated to ESPN+, Channels 21-35 dedicated to Paramount+, and Channels 36-50 dedicated to Amazon)?
But without the ADB.m3u, I can't even make sure DISPATCHARR is calling to the appropriate virtual channel within ADBTuner regardless of how it's supposed to be configured.
It doesn't work that way with Prismcast, but I believe that's because Prismcast can accept the correct configuration for web access using the deeplink which is just the http address vs. having to call up specific apps like in ADBTuner. And I think I mentioned, I do have Prismcast working in FDL.
Apologies, I realize my edge case is making things more difficult than it would otherwise be and I am probably misinterpreting the design of one or more of these components.
Jay