element-call
element-call copied to clipboard
Figure out a saner way to route audio
Context: discussions on https://github.com/vector-im/element-call/pull/512

If we decide to always use the Web Audio API, we could then always route everyone's audio ~~to a single hidden audio element~~ directly to the destination, which would be pretty clean IMO
If we decide to always use the Web Audio API, we could then always route everyone's audio to a single hidden audio element, which would be pretty clean IMO
That, we are actually doing already :p
My reasoning for not using Web Audio for everything was that the Chrome AEC hack wastes CPU cycles, so it would be good to avoid where possible. (And possibly, spinning up an audio processing chain with no effects might waste resources a little bit too.) However, that could be sacrificed in favor of having a more maintainable model for audio routing.