When the "Wake Confirmation Tone" is used, it gets detected as "Ding!"
rarroyo6 opened this issue · comments
When the "Wake Confirmation Tone" gets enabled, it sometimes gets detected as the word "Ding!" immediately after saying the wake word, and it doesn't allow you to continue saying the command.
This doesn't happen all the time (about 30%-50% of the time), lowering the speaker volume helps a bit, but it continues to happen.
Maybe the microphones should be turned off until after the confirmation tone finishes playing.
Thank you, I'll try those suggestions when I get home.
I increased the VAD to 750, and it seems to be working OK now.
I'll try it for a few days and report back if there's still a problem.
I still think that the microphone should be disabled while the speaker is active, since this issue will continue to come up as more people start using Willow.
Thanks for the help.
I still think that the microphone should be disabled while the speaker is active, since this issue will continue to come up as more people start using Whisper.
My gut feeling says this will be too timing sensitive and actually make the experience worse, but we're going to test it locally and make a decision based on those test results.
You can download a Willow image that mutes the mic before playing wake confirmation tone and unmutes afterwards: https://github.com/toverainc/willow/actions/runs/7223902325
You can OTA update it via WAS following the instructions here: https://github.com/toverainc/willow-application-server#upgrade-with-your-own-willow-builds
As I suspected, mute is too slow and in my testing it's not a good experience at all. However I've never actually used the wake confirmation tone, so I've no previous experience to compare it against. Interested in getting feedback from others.
Same thing here, about 50% of the time. The "Ding" comes so quickly that it is sometimes difficult to get the command in first. Don't know if it is just the way I am speaking, when I am close to the device it seems to hapopen more often.