I can’t speak to any of that, myself. I’m just some luser out here on the interwebs. A thing I can tell you that might be worth mentioning is that Foundry’s Module ecosystem is mostly user-created/useer-maintained, rather than first-party. My ignorant outsider guess at the most likely path to getting an option like this is:
- Foundry team adds some additional functionality to their product that allows an audio source to be streamed through the “Playlists” tab with its own volume control
- Foundry team adds features to the API that handle this new element, and release documentation about it. (Foundry’s direct involvement is likely to end, here.)
- One or more community members band together to write a module that interacts with this new part of Foundry and does the stuff we’ve talked about here.
- Those community members probably come talk to you a lot lol
Foundry’s monetization scheme doesn’t involve any ongoing fees or subscriptions, and it seems like they have a verrrrry small team. (There’s a fair amount of first-person-singular writing in the public-facing company comms?) They charge once for their software, and update it for free in perpetuity. I think this is one of the reasons their fanbase is kinda, er… let’s say “vocal in their dedication;” the one-time price is a market differentiator. I point this out because it means their dev “team” might have a pretty full docket of stuff to work on, over there, as it is. >__<