Hej there, I cannot use snips anymore.
test microphone leads to the following recording
What is the problem here?
sam test speaker works flawlessly.
sam status
OS version … Raspbian GNU/Linux 9 (stretch)
Installed assistant … ai
Language … de
Hotword … hey_snips
ASR engine … snips
Status … Live
Additionally, the contents of your /etc/snips.toml file, specifically the mike= line?
Most of the time, when people have this issue, it is because the name of their microphone in the snips.toml configuration file does not exactly match the name of their MATRIX microphone.
Okay I reinstalled the matrix-kernel-modules. Now I think I only got a problem with snips.
The snips-audio-server is running but still does not recognize its hotword…
After re-installing the kernel modules, what’s the hardware card and device of your MATRIXIO-SOUND card?
sam test speaker and sam test microphone use the /etc/asound.conf file to work whereas the snips services uses the /etc/snips.toml config, so it may help to double check that the hw numbers are correct in the line below in /etc/snips.toml.
I also just tested on Raspbian Stretch 4.19 and the workaround here seems to be working for me.
Whatever was causing the issue of lack of hotword detection had been resolved on the Snips side (was a portaudio issue) but seems like it may be back again.
Thank you very much @Samreen
This problem is solved now.
Now I only got a problem with snips. I cannot get the iobroker app to work.
So they should help me
Thank you very much again!!!
Great work
Hi, I’m testing my Matrix Creator with “snips.ai” and I have the following problem in step 5:
“sam test microphone” doesn’t work
Also doesn’t work (step 1):
amixer set PCM 100% && arecord recording.wav -f S16_LE -r 16000 -d 5 && aplay recording.wav
It’s funny that “sam test speaker” works, and that the microphone works when I type in the command prompt:
arecord -D plughw: 2 --duration = 10 -f cd -vv ~ / rectest1.wav
aplay ~ / rectest.wav
Any solution to my problem … tomorrow I try another Raspberry Pi
Generally, “sam test microphone” issues can be traced back to the configuration in the /etc/asound.conf file and whether or not the MATRIX kernel modules were properly installed. I know you got everything working in the end from the contest page, is that how you fixed it?