Hi, I built the client UI for this and... yea, I really wanted to get Firefox working :(
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.
Do you know why there's a difference in the performance of the algorithm in another browser? I would expect that all browsers run the code exactly the same way.
You prefer the management of Chromium, which makes billions a year from invading your privacy and force feeding you advertising, while also ruining the internet ecosystem?
Thanks for sharing. I did make some changes that seems to have improved things, although I do still see the occasional misfire. Perhaps good enough to remove that ugly red banner though!
Hi, I built the client UI for this and... yea, I really wanted to get Firefox working :(
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...
Do you know why there's a difference in the performance of the algorithm in another browser? I would expect that all browsers run the code exactly the same way.
Do not go by the warning message. It does work just fine on Firefox latest. Cool, demo, btw!
I hate that everyone just develops for chromium only
This site works fine in safari/mobile safari, it is not ‘chromium only’
WebKit and its derivatives then.
1 reply →
Mozilla refuses to implement some really cool standards.
https://mozilla.github.io/standards-positions/
That, and their shitty management shakes my faith in Firefox
They're not necessarily standards. I clicked on the first negative one and it said draft.
One browser vendor proposing things other vendor NAKing it makes it a vendor-specific feature. Like IE had its own features.
3 replies →
You prefer the management of Chromium, which makes billions a year from invading your privacy and force feeding you advertising, while also ruining the internet ecosystem?
1 reply →
A shame. They used to be the free (freedom) option.-
Likely a lot of people on HN use Firefox
It is working perfectly for me on Firefox (version 127).
Thanks for sharing. I did make some changes that seems to have improved things, although I do still see the occasional misfire. Perhaps good enough to remove that ugly red banner though!