Skip to content
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

Sattelite +openWakeWord - wakeword refractory time issue #224

Open
nesty1990 opened this issue Sep 30, 2024 · 0 comments
Open

Sattelite +openWakeWord - wakeword refractory time issue #224

nesty1990 opened this issue Sep 30, 2024 · 0 comments

Comments

@nesty1990
Copy link

hi ...
as many other have noticed, there is an issue with multiple wakeword detection.
after watching debug from wakeword and adding some additional debug messages to sattelite.py i noticed that the way event from wakeword service is handled makes result of detection just postponed .. ie.. when wakeword event is allowed again, we get positive detection that happened long time ago on chunk of audio right after first one...

i really dont know why - is it async processing of queues or buffer on eth stack... or something else, i dont do a lot of python, but i made some quick and dirty fix -

call mute mic everytime snd is called - set detection refractory period to 5s from now..
call unmute with 0.1s delay after snd is finished and set detection refractory period to 1s here

this seems to always work, i get a wakeword detection during refractory period debug messages right after mic is unmuted and zero detections when there should be none ...

hope it will help somehow

@nesty1990 nesty1990 changed the title Sattelite +openWakeWord - mute microphone issue Sattelite +openWakeWord - wakeword refractory time issue Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant