4 ms·
It has to, and as far as I understand it always has (as well as the operating system). Take for example echo suppression. For this to work, the algorithm has t
by sudosysgen 5y ago
It has to, and as far as I understand it always has (as well as the operating system).
Take for example echo suppression. For this to work, the algorithm has to be aware of the audio that's being output in real-time. We can't have the server do that, of course, and it would be very inefficient to do this in JavaScript (which also wouldn't have access to audio output by other tabs or processes).
So this has to be something done by the browser, in a very low latency and efficient way.
As far as I understand it, Chrome and Firefox have both been doing browser side DSP in WebRTC for a while. There is a way to disable this however.
- Nextgrid 5y agoI would've expected this to be done at the OS level, or at the very least have this configurable and opt-in at the browser level just so you know and can decide as I assume that it would be counter-productive to have both the OS and the browser do it.
- sudosysgen 5y agoModern operating systems provides APIs so they can coordinate this kind of audio processing, so you don't have to worry about it. It isn't opt-in at the browser level, but there is a standard in WebRTC to disable this across all browsers.