I believe he's saying that he's using Channels as a backend "tuner aggregated source" that then various platforms can access such as the Sage Boxes.
I use your Prismcast to source Dispatcharr (my source aggregator) and then port that out to CDVR, EMBY, TiviMate, Plex. I also source some of CDVR for TVE accessible channels.
Thanks for elaborating. Alright...convinced. There'll be some optionality built into the next release related to HEVC.
I have an admittedly unrelated couple of questions because I'm curious: why on earth do people want to do all this stuff? Is it just to tinker, or is there some really value that I, in my pretty simple/straightforward use cases, cannot quite see?
Bonus question: what is it with these static weather pages that people want to turn into channels? Why? I don't get it...there's hundreds of easier (and arguably better) ways to get the weather. Including just asking whatever device you're viewing!
The more I understand how the community uses PrismCast and has it engage with the ecosystem around it, the better I can contribute, or explicitly opt out of a certain path if I don't want to support something. Don't assume that I know what most of these other toolsets are - I do not.
(e.g. I had never heard of Dispatcharr before...and still don't get it's utility for a normie like me, but recognize others do).
As an FYI: proxying PrismCast to a source aggregator, particularly with Channels (it's primary use case) is not something I would advise. PrismCast increasingly ties into Channels DVR's API for some of it's more nuanced features and it relies on the fact that Channels is directly connecting to it. Proxying that connection in some way...you're on your own and I won't be supporting those setups (may work over the long term, may not).