-
Notifications
You must be signed in to change notification settings - Fork 62
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
Using wake-word and transcribe intent at same time #64
Comments
I know about bash recipe https://github.com/synesthesiam/voice2json/blob/master/recipes/launch_program/listen_and_launch.sh But I believe time after voice2json wake word starting and actually starting recognition takes around 5-10 seconds. So, after executing intent it will be in not working state pretty long time. Or I understand wrong? Is this actual recipe or proof-of-work? |
So, 13 seconds to actually begin wake-word recognition, of course, it will detect, if word been sayed at this 13 seconds because linux pipe cache, but:
between "Waiting for wake word..." and "Recording voice command..." time 13 seconds, if I say next command right after previous. |
OK, I made it works, for chaingin audio device for simultanius access, sending wait-wake (without exit-count) to stdin of another program, and this program calls writing audio to 3 seconds wav file, and doint intent stuff. wake-word still running in this time |
As I did understand, there are two modes: wait-wake and dealing with speech recognition (transcribe).
Both works for me, but how to run both modes at once? I mean, system must wait wake word, and after than starting transcribing stream for intent command. Is there recipe for this? In ideal way, there is json in stdout, new line - new json, appearing when I say wake word AND intent after that. Super ideally: first JSON when wake word detected (so I will light up indicator LED and say "what do you want?" to speaker), and after that JSON when intent recognized.
Thank you after all for this cool project, runs brilliant at Jetson Nano 2Gb.
The text was updated successfully, but these errors were encountered: