Closed andrewufrank closed 7 months ago
i have a separate install on a rasi 4 (again running debian bookworm) and installed snapserver and snapclient on it from bookworm-backports - gives 0.27 version). the setup works for mpd (using the alsa output) and pipes the stream to other snapclients, but not to the local snapclient (i.e. the same which runs on same cpu than the snapserver). again, aplay -l gives
aplay -l
aplay: device_list:274: no soundcards found...
it seems that mpd captures the output channel. i have switched off the output in mpd to alsa device (which has a noticeable delay compared to the pipe and snapclients!)
on the raspi 1b i have disabled the mpd server but still no soundcar found and no sound from the snapclient.
what command would help to find the card?
I reinstalled a raspi-os (bookworm) to exclude the issue is caused by the debian linux (tested images) bookworm for raspi. the debian linux gives for snapclient -l
only null, however sudo snapclient -l
gives a long list.
for the debian linux on a raspi 1B i have reasonable output with sudo snapclient -s 10
(but not with snapclient -s 10
) . changing /etc/default/snapclient
to SNAPCLIENT_OPTS="-s 10"
works.
however, on raspios (bookworm, but with the old version v. 0.26 for snapclient) I have sound output on user-land snapclietn -s 10
but not on sudo snapclient -s 10
and as a consequence it does not automatically start when enabled with systemd.
I conclude that the issue is caused whether one is running as user or as root; there is a difference between the raspian os (derived from debian) or in the version of snapclient (v.0.26 vs. v.0.27): one runs ok root privileges, the other works in user-land. I do not understand enough on how to tune the systemd controls to understand to fix this and would be interested to understand the background.
Please try with the v0.28.0 version, there are packages available here. The armhf-bookworn
images should run on your RPI1b.
Thank you for your efforts. it took me a while to get the time and the hardware together again to do any experimentation. I have downloaded the armhf
0.28-beta.1.1 and tried to install, but the the message, that it has the wrong architecture. i added the architecture armhf to the raspi 1b (which is armv6l) and installed ok, but when I run snapclient I get "illegal instructions". I take that armhf and armv6l are not compatible. - I have an installation working and will check in a few weeks how I got it working there.
Describe the bug the snapclient on a raspi 1b (running debian bookworm) cannot find the alsa output. Steps to Reproduce
snapclient -l gives
snapclient --player gives
Environment details raspi 1b, running debian bookworm (from debian tested images) headless snapclient installed from bookworm-backports snapclient/stable-backports,now 0.27.0+dfsg-1~bpo12+1 armel [installed]
the output is connect in the blue connector (no hdmi connected). it works with mpd and produces sound as expected and says "my ALSA device"
the snapcast sees two client ath this site, with the same ip, which I do not understand either. why is the alsa output not found. what are possible action to debug?
thank you for an otherwise working system (have a different client working and work with snapcast app, which shows even this raspi client, but no sound). andrew