-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding latest okay nabu wake word #216
base: develop
Are you sure you want to change the base?
Conversation
that1guy
commented
Dec 27, 2024
- Adding latests Okay Nabu wake word to hopefully increase success rate
- testing to see if better UX
Did you try lowering probability cut-off? I have it on 0.8 for ok Nabu. |
@formatBCE where do I do this? Currently in my testing this wake word is giving me pages of warnings, which then cause the TTS response to stutter when playing back. Sometimes the response takes 30 seconds to play back because mWW is eating up the ESPs processing power: |
Damn, that's something weird! I don't have that on Respeaker, will try to reproduce on SAT1. Is it because of newest wake word? 0_o |
Yes. This appears to only reproduce in this PR with latest wake word to my knowledge. Please do let me know if you can reproduce this. I'm seeing this on two Sat1 devices in my home. |
- This is performing well on my end. - On desk near the user and in-ceiling 15ft from user. - Please test
@formatBCE @gnumpi I'm running the even newer Okay Nabu wake work model with a probability cutoff of 0.8. Please test it's performing very well on my end. |
I tried it. For me it works worse than the first one... Much less responsive. |
how are you concluding it is "much less responsive"? |