W3AXL
Add a web player resource with a customizable URL for audio streaming.
Add a new console resource that supports stream URLs as receive-only (RX) resources, using the same UI as the existing radio resources.
To make this easier, I might create a separate small program (rc2-stream or similar name) that can handle multiple web streams as individual virtual channels (similar to how rc2-dvm works).
Adding all the channel activity detection & connection logic to the console frontend would be a much harder endeavor.
Sorry for the lag on this,
A separate app would kinda be a pain IMO, it'd be cool to just use the current radio resource UI and a toggle to play the stream. No need for RX indicators or anything like that,
@DevRanger I've already gotten a headstart on this but I built it within the rc2-console itself, it does work well there. I think in some cases it's nice to just have the console do they heavy lifting without having to run a demon if not needed. I do need to do quite a bit of dis-entangling of my changes before I can get it in to a proper PR, but It's doable and does work. That being said though, I may just rework it into something like rc2-stream like @W3AXL mentioned
The one issue I have with doing everything console-side is the additional CPU overhead for doing the sound detection/auto activity processing. Of course, it's entirely possible that's a non-issue, but CPU profiling of the console will be necessary to make sure we're not adding a ton of overhead.
I agree from an implementation standpoint keeping it in javascript does make things easy.