ALSA device card error

[michaeldessen]

Thank you for the work on this great software, Kevin! I tried following the instructions you provided on the Sonobus list to set up a HifiBerry, and encountered an error. I was able to set up and access a Pi with the latest release and did the following 2 tweaks you suggested:

1. used the terminal to run these commands to get the new startup script, which appeared to work fine:

sudo cp -p /usr/local/bin/sonobus_start.sh{,.bak}
sudo wget https://github.com/kdoren/jambox-pi-gen/raw/jambox-rt/stage3/08-install-sonobus/files/sonobus_start.sh -O /usr/local/bin/sonobus_start.sh

2. then I did these updates to /boot/config.txt
   Added these lines:

# hifiberry 
dtoverlay=hifiberry-dacplusadcpro 
force_eeprom_read=0 

And commented out the line
# dtparam=audio=on

When I then double click the Sonobus icon on the Desktop, I get the following error in the sonobus_start.sh
ALSA Device card 2 is not available: PLAY_RESULT: 1, RECORD_RESULT: 1

Do you know what I need to do to fix this? Many thanks!

Michael Dessen

[kdoren]

What is the output of "arecord -l"?

The file /etc/jackrdc.conf tries to choose the last capture card number it sees.
So maybe you have other audio interfaces plugged into USB, but if that is the case it should work with that, not error.
Only other explanation I can think of is that you accidentally uncommented the "DEVICE=hw:2,0" line in /etc/jackdrc.conf.

I would expect hifiberry to be Card 0 in your config.
In /etc/jackdrc.conf, you can force it to choose Card 0 with:

DEVICE=hw:0,0

[CAguayo]

Yeah, I think we got ourselves in trouble when we tried to say, "no one would ever want to use the built-in audio." The /etc/jackdrc.conf file works great for most interfaces as long as the dtparam=audio=on is left uncommented in /boot/config.txt. Adding hardware via dtoverlay is required for audio "hats," but we complicate things by disabling built-in audio; that forces us to get the jack options just right; which are all over the map for different interfaces. The first thing to try when testing an on-board sound card is to *only* add the dtoverlay line required for that particular hardware in config.txt, and see if it works with no other changes. If not, then we should have the string required in /etc/jackdrc.conf, it's the string reported by aplay -l. Carlos

…

On Sat, Jan 16, 2021 at 2:24 AM Kevin Doren ***@***.***> wrote: What is the output of "arecord -l"? The file /etc/jackrdc.conf tries to choose the last capture card number it sees. So maybe you have other audio interfaces plugged into USB, but if that is the case it should work with that, not error. Only other explanation I can think of is that you accidentally uncommented the "DEVICE=hw:2,0" line in /etc/jackdrc.conf. I would expect hifiberry to be Card 0 in your config. In /etc/jackdrc.conf, you can force it to choose Card 0 with: DEVICE=hw:0,0 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#23 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKJTE7OXZAMFFQLPDMJB3DS2FSNNANCNFSM4WE7XY4Q> .

[michaeldessen]

Thank you both! I did not have any USB interface (or anything other than headphones/mic) connected to the Pi.

I followed Kevin's suggestion to add the line DEVICE=hw:0,0 in etc/jackdrc.conf and then Sonobus opened successfully.

FYI, before I did that, the output of arecord -l was this:

pi@jambox:~ $ arecord -l **** List of CAPTURE Hardware Devices **** card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplusadcpro], device 0: HiFiBerry DAC+ADC Pro HiFi multicodec-0 [HiFiBerry DAC+ADC Pro HiFi multicodec-0] Subdevices: 0/1 Subdevice #0: subdevice #0
Following Carlos' suggestion, I also left dtparam=audio=on uncommented in /boot/config.txt, which did not cause any problem.

Thanks!

Michael