| The first thing I was thinking is using PulseAudio somehow. It has some bad image issues but its swiss-knife-of-audio-routing chops are undeniably present. It's Linux only though, so probably wouldn't be useful here. I'm trying to figure out what the actual context in question is, particularly in terms of technical connectivity. Is this being used for remote DJing? Or conferencing? Or an audio recording situation? If you're prepared to throw money at the situation, it's possible this may be fixable with a simple bespoke solution. I say "possible" because, unfortunately, I just did some digging and found https://bugs.chromium.org/p/chromium/issues/detail?id=453876: > Unfortunately we don't support multi-channel > 2 nor multiple devices at the moment. > ... > Are there any future plans to support these two features? Is this a w3c issue or a Chrome issue? > ... > I am quite skeptical about this; I was told this requires a huge change in our WebRTC-side infrastructure, but I am not sure what the current status is. > The spec indicates getUserMedia can be configured with 'channel count', so I assume this is Chrome issue. That immediately nukes WebRTC :( Could make for a fun project. I'm very fascinated with audio handling myself and this sounds interesting, but I'm unsure I'd personally have the skills (or mental stamina/attention span :< ) to be sure I could follow through. I'm also only on a Linux box, which brings up the platform-native problem. |
Honestly, the best answer is probably to continue using multiple Skype instances. Which is gross. But, y'know.