Our app provides two-way communication b/w browsers via WebRTC with the spatial audio of the peers playing via the Babylon Sound component.
We’re noticing that there is a lot of feedback (echo) that we get in this process.
This is in stark contrast to what happens if we use the native audio element and push it to the DOM. There is almost nil echo in that case. We cant use this because we want spatial audio, which is why we use Babylon’s Sound component.
My guess is this is a deeper issue within chrome, where it tends to ignore audio that is playing in the browser but is not part of the DOM.
Curious to know your thoughts on it.