Okay, using the beta (20180801 preview) on a Pi3 and a “no-name” usb conference mic which at least claims to be a CM108 (https://www.amazon.com/gp/product/B0797SDH6T, but it doesn’t show up in lsusb… at all. odd).
Anyway, I changed /etc/mycroft/mycroft.conf to use plughw:1,0, and still couldn’t get the microphone working until I changed
defaults.pcm.card to 1 in /usr/share/alsa/alsa.conf, at which point I could record with arecord, play with aplay, and run the test-microphone script.
Heeeere’s where it gets odd. In the CLI, the mic level is active for about half a second (maybe a full second) after I start the voice module again (
start-mycroft.sh voice). And it’s working; if I am silent, it shows small numbers and then freezes, and if I’m loud, it shows large numbers and freezes. But either way it seems to freeze! The lights on the USB interface keep blinking as if it was recording, but nothing happens on the mic level side.
Most curious. Any ideas? I know the new stable is out soon and I’ll switch to that, but this was an odd one. Perhaps the little USB adapter is at fault, but this seems quite peculiar, and very repeatable (just starting the voice module again will cause the mic level to fluctuate for a half second…)