It's a window, an fft, a filter around a primary frequency range, an integration, and an N second timer since the last time the audio crosses the threshold.
Discord's current implementation drops in the middle for words! It's crazy.
It's a window, an fft, a filter around a primary frequency range, an integration, and an N second timer since the last time the audio crosses the threshold.
Discord's current implementation drops in the middle for words! It's crazy.
also as a phoenix dev (just released my first big site), you picked the right stack :)
Edit: I've adjusted the thresholds to try and tune it, but it's been very hit or miss.
It's usually specific users whose words get dropped, maybe their activation threshold is just low enough. But still, seems to me like this should not happen, especially in the middle of sentences, since the beginning of the sentence is recorded just fine.
(Windows 10 Pro)
Skype, Google Hangouts, teamspeak, ventrillo, mumble, and tox all support my microphone and voice activation correctly.
Its even more useful in competitive gaming and/or streaming where many want to chose what to say to their team/friends and themselves/the stream.
(can you tell I’ve played Overwatch?)
That said, I use a for-realsies dynamic microphone with tons of off-axis rejection and a wall-mounted arm (I play games in my office/recording space, that's the engineer station mic). So I probably could use voice detection and be fine. But habits die hard.
The rise of mechanical keyboards has made PTT practically the only option. Otherwise you just hear little clicking all the time.
Last time I tried it the browser app was especially prone to this, to the point of rendering push-to-talk completely unusable.