Read the statement by Michael Teeuw here.
Solved Hello-Lucy using Adafruit Voice Bonnet
-
@sinbad339 said in Hello-Lucy using Adafruit Voice Bonnet:
With MM still running, specifying the hw explicitly results in an error.
ok, so MM is using that device
while mm is running do
ps -ef | grep arec
u should see the arecord process and the parms passed
from one of my apps that uses arecordarecord -D default -q -r 16000 -c 1 -t wav -f S16_LE -
the trailing dash means stream content to stdout (which is captured by the upstream library)
-
-
@sdetweil
So the arecord -l lists card2 as my expected capture device (seeed-2mic-voicecard). I find it interesting that it enumverates as #2 with no #0 or #1.Anyway, I ran your ps command; not sure what this output means (as I’m sure you’re aware by now, I’m a Noob on Linux).
ps -ef | grep arec pi 1953 1927 0 11:04 pts/0 00:00:00 grep --color=auto arec
-
@sinbad339 hm…
should have used arecord…
try
ps -ef | grep rec
(there are only 2 apps… arecord or rec )
the output from ps
pi 1953 1927 0 11:04 pts/0 00:00:00 grep --color=auto arec
user that started process
the process id
the parent process id +
(i don’t know, 0)
the time the process was started
(i don’t know, pts/ )
how much cpu time has been used since started, in seconds
the string used to start the process, pgm name and then parms -
ps -ef | grep rec root 76 2 0 11:02 ? 00:00:00 [vchiq-recy/0] pi 2320 1927 0 11:24 pts/0 00:00:00 grep --color=auto rec
Not sure what vchiq-recy is…
But no arec or arecord. -
@sinbad339 said in Hello-Lucy using Adafruit Voice Bonnet:
But no arec or arecord.
well, that explains the error…
you did run the installation dependencies script, right?
cd Hello-Lucy/installers bash dependencies.sh
-
@sdetweil
Yes, I did run it. Its been a while, and I remember warning about depreciated versions, but nothing that I thought could be an issue. OK to run it again? -
@sinbad339 said in Hello-Lucy using Adafruit Voice Bonnet:
OK to run it again?
i don’t think there is a need
add debug:true to the module config section
module: config: { debug:true, .... whatever else was there }
and then
pm2 stop all cd ~/MagicMirror npm start >somefile.txt
when error reported
alt-spacebar, n to minimize mm
ctrl-c to stop mm
and look at somefile.txt -
@sdetweil
WELL, now it seems to work. Running from command line w/ debug, I don’t get microphone with ERROR, and if I say “Hello Lucy”, it prompts for a command, then does it, and issues the “ding”. I’ve done this three times now, and its worked every time. Here’s the debug outout:> magicmirror@2.18.0 start /home/pi/MagicMirror > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js [05.01.2022 11:55.24.384] [LOG] Starting MagicMirror: v2.18.0 [05.01.2022 11:55.24.394] [LOG] Loading config ... [05.01.2022 11:55.24.404] [LOG] Loading module helpers ... [05.01.2022 11:55.26.860] [LOG] Initializing new module helper ... [05.01.2022 11:55.26.864] [LOG] Module helper loaded: Hello-Lucy [05.01.2022 11:55.26.866] [LOG] All module helpers loaded. [05.01.2022 11:55.27.040] [LOG] Starting server on port 8081 ... [05.01.2022 11:55.27.066] [LOG] Server started ... [05.01.2022 11:55.27.069] [LOG] Connecting socket for: Hello-Lucy [05.01.2022 11:55.27.071] [LOG] Starting module helper: Hello-Lucy [05.01.2022 11:55.27.073] [LOG] Sockets connected & modules started ... [05.01.2022 11:55.27.482] [LOG] Launching application. [05.01.2022 11:55.37.133] [LOG] Hello-Lucy has recognized: ALL IS THE [05.01.2022 11:56.16.829] [LOG] Hello-Lucy has recognized: NINE
-
The difference is how MM is started. If I do it the manual way, the microphone works (with or without debug enabled). If MM does its normal autostart, using mm.sh that includes DISPLAY=:0 npm start, then the microphone doesn’t work.