I have a problem with my picroft installation, after update to the newer version picroft stop listening the wake word and the mic level stay stuck in —7.86 without any change. I am using ps3 eye as microphone.
OK, so those error messages are not related to microphone configuration. They are related to Mycroft trying to synchronize settings with the server - home.mycroft.ai - which occasionally times out.
I have just rebooted mine , with the Pi3 and the PlayStation mic and now it has stopped listening to the mic…
I have rebooted a few times hoping it would come good, but …nope… no audio level showing at all
I think I will give this up as a bad joke & go back to the Linux VM…
Did you guys used raspi-config to force all audio through analog speakers?
Seen similar issues, with that 7.86 number when I was screwing around with multiple sound-pulseaudio configurations. I believe, that force audio thing made the difference…
I have no problem with the audio OUT… That is working no problem , I can type a question and get an answer, but the USB mic has failed and attempting to change the device seems to make no difference…
So I completely restarted with a fresh image from the website and now the PS3 Mic STILL won’t work… It worked perfectly for 2 days .
Brilliant… I only bought the thing so I could use it with picroft! (and i got a new Pi for Fathers Day to set up!)
What goes on here @KathyReid ?
OK so that is WEIRD… I shut down the Pi, plugged the PS3 Mic into my Win10 PC and let it do it’s installing drivers thing, then plugged it back into the Pi and started it again and now it works again…
maybe there is some state or device id that is stored in the mic device that picroft “broke” ??
My guess here is that PulseAudio hit some sort of SUSPEND state. I’ve seen a lot of PulseAudio talk a lot about setting the status of sources to SUSPEND but I don’t know how to solve it.
thanks Sean… My USB mic has stopped working ( AGAIN) and I tried your edit to the default.pa file, (I actually simply added those two lines) , but it made no difference…
Sigh…
I had this issue and editing default.pa worked. You have to know what your USB microphone address or name really is. (It may not be “hw:0,0”). I actually used the device name, which is problematic, because if I ever change the microphone device, I will have to remember to change it.