@little-stone,
Welcome to the community!
It looks like ALSA is working for you which is great. As for the C++, let me test this and get back to you. The code hasn’t changed so I’m not sure what could be causing this but I will check.
As for the device or resource busy
issue, are you still having it? That should not happen if the recording has ended, unless some other program is using the mics.
If you provided me with more information as to what your environment consists of, I could try to replicate the error. What is your Pi make/model, power supply voltage and amperage, what RPi OS version, linux version (check with uname -a
in terminal), and what packages have you installed since first boot (you can check MATRIX packages with dpkg -l | grep matrix
in terminal)?
@luca,
Apologies for the delayed response.
I have not seen ALSA errors like yours before, it almost seems like ALSA is corrupted on your device because arecord -l
should just list the RPi mics regardless of MATRIX device configurations.
Could you also provide me with more information about your dev environment so I can try to replicate?
You said you are using a Pi 4 so what is your power supply voltage and amperage, what RPi OS version, linux version (check with uname -a
in terminal), and what packages have you installed since first boot (you can check MATRIX packages with dpkg -l | grep matrix
in terminal)?
Additionally, could you show me the output of your sound configuration file? The command is
sudo cat /etc/asound.conf
If you are able, I would recommend a fresh installation of Raspbian OS on your microSD for the Pi 4 with installations from here (the kernel module link I had sent before) to see if your mics work.
Best,
Samreen