-
Notifications
You must be signed in to change notification settings - Fork 690
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
Speech Rec Works Intermittantly #287
Comments
@HelloExactly it would help if you could give more information about your issue. IE: what branch are you using, what errors you see, etc. This is likely already a known issue #170 and I should have a complete fix this weekend. |
@HelloExactly have you tried just killing the running instance and restarting? That works for me. ALT-F4 to close the open window, use terminal and run the @evancohen I have the same issue. Today, I wiped and started from scratch to get a clean install. I still need to run I tested it on the new master and rss-dev. Keyword spotting is working fine. In testing, I got about 3 commands out of it and it stopped listening. I have not met quota and restarting will allow me to get a few more commands in. When I run it In addition, I see the ALSA errors in CLI but nothing is jumping out at me (and I am not as smart as you guys) that leads me anywhere. |
Reboot/restarting the app, semantics. @evancohen I'm using the Dev branch, and same as the above poster, I see no errors after KWS shuts off. |
Thanks for the details @GobleSt! Sounds like this is a bug. I haven't had this repro in my current build, but I'll do a clean install this week and see if I either missed a step in the documentation or if there's something up with the keyword spotter. |
Hey Guys: I'm getting the same also. KWS works one or two times, then seems to die. Below is my log:
|
So I was able to spend a few minutes looking at this tonight, and it looks like the keyword spotter is causing the alsa-sink to hang in a rewind (the hang itself is intermittent, which is probably why you are seeing it work for a couple times before stopping). I was able to get this to reliably repro when recording via the microphone debug utility ( From the PulseAudio logs:
The corresponding failure in the keyword spotter:
Maybe the error above is something that @chenguoguo has seen before (although I doubt it because PulseAudio is not their recommended audio input library, it's ALSA)? The "nice" part about this is that it's just the playback that I think is causing this issue, not the actual recording. Removing the playback of the "ding" sound should fix the problem (theoretically). If I have some time later tonight I'll take a look at pushing something to the dev branch. I'm guessing that the real solution to this is to ditch PulseAudio altogether, but there are loads of compatibility issues between microphones that PulseAudio takes care of. Ideally there's another way to specify the default input device for Electron when using webkitSpeechRecognition(). I've tried |
I have never seen this error before. And PulseAudio isn't my favorite way If the errors come from audio playback, why not use a different prompt, On Mon, Jun 13, 2016 at 9:51 PM, Evan Cohen [email protected]
|
I can confirm with a decent amount of certainty that commenting out line 19 of kws.py (the playback line) that the keyword spotting detection works reliably. |
The ding was causing a freeze in a rewind. This is a temporary workaround to stop the keyword spotter from hanging after a few utterances.
@kgrewohl I've pushed that change to the |
@evancohen I just re-cloned the dev branch and the mic is working like it was before. The ding was nice but functionality is way better. Thanks! |
@kgrewohl it won't be any trouble to add the ding back on the JavaScript side of things, the issue arose from the way the keyword spotter was playing audio. |
@evancohen confirmed. VC is working like a charm. If for no other reason to put the mirror to sleep and wake it up again is totally awesome. Issue 284 still exists but I would say 244 and 287 are outta here! Youtube also starts to play sound then stops and continues to play video. This appears to be a little intermittent as the bowtie plays a few seconds of audio and the new Jason Bourne trailer played almost 20 seconds of audio. Maybe poor wireless quality (hardware related to the pi) where it has a hard time caching both sound and video? I will look more into this when I can but VC is great!!! GJ guys! |
Seems like my GitHub automation got a little carried away there ;) Regardless, this fix is now in the latest master, thank you all for your help 🚀 |
I've noticed others with this issue so I thought I'd post it here. Speech rec works but not always. Sometimes 2 in a row will work, sometimes 10, sometimes none at all. Only fix seems to be a reboot but then the issue will start all over again.
The text was updated successfully, but these errors were encountered: