Read the statement by Michael Teeuw here.
MMM-AssistantMk2 / MMM-Hotword Issue
-
What type of microphone is it? Is it USB?
Also, what version of Raspbian are you using? And is it Raspberry Pi 3+ ? -
@BJ-Duncan
The Mic is a combined Speaker / Mic HAT as see here… https://www.raspiaudio.com/raspiaudio-aiyI am running Raspberry Pi3+
Version…pi@raspberrypi:~ $ lsb_release -a No LSB modules are available. Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.9 (stretch) Release: 9.9 Codename: stretch pi@raspberrypi:~ $
-
Sorry @JonoGee mate, I may not be the best person to resolve as I have USB Mic so my settings will be different to yours.
I will attempt to do some research for you though and see if I can assist with a solution.
-
@BJ-Duncan
I realise both Speaker & Mic are on same Hat but does it make sense to you that the ID for aplay and arecord are exactly the same. Code included below…pi@raspberrypi:~ $ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sndrpigooglevoi [snd_rpi_googlevoicehat_soundcar], device 0: Google voiceHAT SoundCard HiFi voicehat-codec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 pi@raspberrypi:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 0: sndrpigooglevoi [snd_rpi_googlevoicehat_soundcar], device 0: Google voiceHAT SoundCard HiFi voicehat-codec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 pi@raspberrypi:~ $
-
@JonoGee I mean I supposedly I have to set both IDs in config file to hw:0,0.
-
@BJ-Duncan What Mic do you use mate? I might just buy same one.lol
-
Hey @JonoGee, mate I have been researching but to no avail. Sorry mate on that. I’m just not too familiar with your set up.
The Mic and Speakers I got are just some cheap USB type models.
Speakers | MicIf you do go by this type of setup then the previous code I placed up should work #fingersCrossed ;-)