We needed a way to measure voice-to-voice latency from the end-user's perspective, and found Silero voice activity detection (https://github.com/snakers4/silero-vad) to be the most reliable at detecting when the user has stopped speaking, so we can start the timer (and stop it again when audio is received from the bot.)
Silero runs via onnx-runtime (with wasm). Whilst it sort-of-kinda works in Firefox, the VAD seems to misfire more than it should, causing the latency numbers to be somewhat absurd. I really want to get it working though! I'm still trying.
The code for the UI VAD is here: https://github.com/pipecat-ai/web-client-ui/tree/main/src/va...
https://mozilla.github.io/standards-positions/
That, and their shitty management shakes my faith in Firefox
One browser vendor proposing things other vendor NAKing it makes it a vendor-specific feature. Like IE had its own features.
I hate using chrome, but I’m forced to with any application that uses we busb/web serial or Bluetooth.
And no, you're not forced to use google. You can make native applications when it's necessary to use privileged interfaces.