I finally installed balenaSound on my Raspberry Pi 3. However, it seems that Snapclient has some issues playing audio. What can I do to solve this?
[Info] (onMessageReceived) Hello from b8:27:eb:19:0e:bc, host: 605bfde, v0.19.0, ClientName: Snapclient, OS: Debian GNU/Linux 10 (buster), Arch: aarch64, Protocol version: 2
snapcast-server 2020-04-03 18-48-11 [Error] (StreamSession) Error reading message header of length 0: End of file
snapcast-server 2020-04-03 18-48-11 [Info] (onDisconnect) onDisconnect: b8:27:eb:19:0e:bc
snapcast-server 2020-04-03 18-48-11 [Error] (StreamSession) Error in socket shutdown: Transport endpoint is not connected
snapcast-client 2020-04-03 18-48-11 [Warn] (sendRequest) timeout while waiting for response to: 293, timeout 2000
snapcast-client 2020-04-03 18-48-11 [Error] (worker) Exception in Controller::worker(): Can’t open default:CARD=vc4hdmi PCM device: No such device
snapcast-server 2020-04-03 18-48-12 [Notice] (handleAccept) StreamServer::NewConnection: 192.168.1.164
snapcast-client 2020-04-03 18-48-12 [Notice] (start) Connected to 192.168.1.164
snapcast-client 2020-04-03 18-48-12 [Info] (getMacAddress) My MAC: “b8:27:eb:19:0e:bc”, socket: 6
snapcast-client 2020-04-03 18-48-12 [Info] (onMessageReceived) ServerSettings - buffer: 1000, latency: 0, volume: 100, muted: 0
snapcast-client metadata:{“STREAM”:“default”}
snapcast-client 2020-04-03 18-48-12 [Info] (onMessageReceived) Codec: flac
snapcast-client 2020-04-03 18-48-12 [Notice] (state) sampleformat: 44100:16:2
snapcast-client ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave
snapcast-client 2020-04-03 18-48-12 [Error] (onException) Controller::onException
Hi there, quick question on this…did you deploy using the 64-bit version of the OS? (You will see a very small ‘64’ in the corner of the Raspberry Pi logo). If so, can you create a new Application using the 32-bit OS type instead, and give it another try? Thanks!
Hello dtischler
Is there any way to identify from terminal? I’m unable to connect the Raspberry Pi to a monitor atm. Although, I know I deployed balenaOS 2.46.1+rev1
Oh, I apologize, I should have clarified…this is seen in the balenaCloud dashboard, on the website. No need to attach a monitor and keyboard to the Pi. Sorry for the confusion.
OK - well, when deploying a new OS, I’m only able to select a 64-bit version for the Raspberry Pi 3. Or am I missing something?
You will need to create an entirely new Application, and select the 32-bit Raspberry Pi 3 device that way. It is a bit confusing in that respect, admittedly.
Alright, here we go. Switching to 32 bit worked. Now, audio is working fine. Thank you very much for your help 
OK - so the master device is now playing. Now I want to connect a second unit. I’ve created the device under the same Application and it’s synced up. But it doesn’t seem to recieve any audio. Or is it?
Latest log:
04.04.20 00:43:34 (+0200) fleet-supervisor
04.04.20 00:43:34 (+0200) fleet-supervisor Fleet subscriber > service.online Fleet publisher#eb65de07-8d91-4d49-81b3-0faeb6be6f35 on 8000
04.04.20 00:43:35 (+0200) fleet-supervisor Fleet subscriber > service.online Fleet subscriber#ee5ad9d0-e727-4658-8752-5bf9714ae30d
04.04.20 00:43:35 (+0200) fleet-supervisor Fleet publisher > service.online Fleet subscriber#ee5ad9d0-e727-4658-8752-5bf9714ae30d
04.04.20 00:43:35 (+0200) fleet-supervisor Fleet publisher > service.online Fleet publisher#8e5dbea6-7d3b-4bb7-97de-a9dca4a5f3a7 on 8000
04.04.20 00:43:35 (+0200) fleet-supervisor Fleet subscriber > service.online Fleet publisher#8e5dbea6-7d3b-4bb7-97de-a9dca4a5f3a7 on 8000
04.04.20 00:43:36 (+0200) fleet-supervisor Fleet publisher > service.online Fleet subscriber#80fcdbd9-7a55-4a70-a9e5-d93a4a45fa49
04.04.20 00:43:42 (+0200) fleet-supervisor Fleet subscriber > service.offline Fleet subscriber#ee5ad9d0-e727-4658-8752-5bf9714ae30d
04.04.20 00:43:42 (+0200) fleet-supervisor Fleet publisher > service.offline Fleet subscriber#ee5ad9d0-e727-4658-8752-5bf9714ae30d
04.04.20 00:43:43 (+0200) fleet-supervisor Fleet subscriber > service.online Fleet subscriber#ee5ad9d0-e727-4658-8752-5bf9714ae30d
04.04.20 00:43:43 (+0200) fleet-supervisor Fleet publisher > service.online Fleet subscriber#ee5ad9d0-e727-4658-8752-5bf9714ae30d
04.04.20 00:46:34 (+0200) fleet-supervisor Fleet subscriber > service.offline Fleet publisher#8e5dbea6-7d3b-4bb7-97de-a9dca4a5f3a7 on 8000
04.04.20 00:46:34 (+0200) fleet-supervisor Fleet subscriber > service.offline Fleet subscriber#ee5ad9d0-e727-4658-8752-5bf9714ae30d
04.04.20 00:46:34 (+0200) fleet-supervisor Fleet publisher > service.offline Fleet publisher#8e5dbea6-7d3b-4bb7-97de-a9dca4a5f3a7 on 8000
04.04.20 00:46:34 (+0200) fleet-supervisor Fleet publisher > service.offline Fleet subscriber#ee5ad9d0-e727-4658-8752-5bf9714ae30d
04.04.20 00:48:03 (+0200) fleet-supervisor Fleet subscriber > service.online Fleet subscriber#198c28b2-9d33-4264-8208-8aedfca98490
04.04.20 00:48:03 (+0200) fleet-supervisor Fleet publisher > service.online Fleet subscriber#198c28b2-9d33-4264-8208-8aedfca98490
04.04.20 00:48:03 (+0200) fleet-supervisor Fleet subscriber > service.online Fleet publisher#4d9bfc63-6207-4efb-9e39-6a47634f1413 on 8000
04.04.20 00:48:03 (+0200) fleet-supervisor Fleet publisher > service.online Fleet publisher#4d9bfc63-6207-4efb-9e39-6a47634f1413 on 8000
04.04.20 00:48:44 (+0200) fleet-supervisor Multi-room master has changed to 192.168.1.164, restarting snapcast-client
04.04.20 00:48:50 (+0200) fleet-supervisor Fleet subscriber > service.offline Fleet subscriber#198c28b2-9d33-4264-8208-8aedfca98490
04.04.20 00:48:50 (+0200) fleet-supervisor Fleet subscriber > service.offline Fleet publisher#4d9bfc63-6207-4efb-9e39-6a47634f1413 on 8000
04.04.20 00:48:50 (+0200) fleet-supervisor Fleet publisher > service.offline Fleet subscriber#198c28b2-9d33-4264-8208-8aedfca98490
04.04.20 00:48:50 (+0200) fleet-supervisor Fleet publisher > service.offline Fleet publisher#4d9bfc63-6207-4efb-9e39-6a47634f1413 on 8000
04.04.20 00:48:59 (+0200) fleet-supervisor Fleet subscriber > service.online Fleet subscriber#198c28b2-9d33-4264-8208-8aedfca98490
04.04.20 00:48:59 (+0200) fleet-supervisor Fleet subscriber > service.online Fleet publisher#4d9bfc63-6207-4efb-9e39-6a47634f1413 on 8000
04.04.20 00:48:59 (+0200) fleet-supervisor Fleet publisher > service.online Fleet subscriber#198c28b2-9d33-4264-8208-8aedfca98490
04.04.20 00:48:59 (+0200) fleet-supervisor Fleet publisher > service.online Fleet publisher#4d9bfc63-6207-4efb-9e39-6a47634f1413 on 8000
04.04.20 00:49:50 (+0200) fleet-supervisor OK
04.04.20 00:49:50 (+0200) fleet-supervisor > fleet-supervisor@1.0.0 start /usr/src
04.04.20 00:49:50 (+0200) fleet-supervisor > node server.js
04.04.20 00:49:50 (+0200) fleet-supervisor
04.04.20 00:49:51 (+0200) fleet-supervisor
04.04.20 00:49:51 (+0200) fleet-supervisor Hello! I'm Fleet subscriber#44bd3da7-43ff-4d68-b24a-8dd3821cee05
04.04.20 00:49:51 (+0200) fleet-supervisor ========================
04.04.20 00:49:51 (+0200) fleet-supervisor
04.04.20 00:49:51 (+0200) fleet-supervisor
04.04.20 00:49:51 (+0200) fleet-supervisor Hello! I'm Fleet publisher#10ca1297-0062-46ff-8eca-cd5d36318970 on 8000
04.04.20 00:49:51 (+0200) fleet-supervisor ========================
04.04.20 00:49:51 (+0200) fleet-supervisor
04.04.20 00:49:51 (+0200) fleet-supervisor Fleet subscriber > service.online Fleet publisher#10ca1297-0062-46ff-8eca-cd5d36318970 on 8000
04.04.20 00:49:53 (+0200) fleet-supervisor Fleet subscriber > service.online Fleet subscriber#198c28b2-9d33-4264-8208-8aedfca98490
04.04.20 00:49:53 (+0200) fleet-supervisor Fleet subscriber > service.online Fleet publisher#4d9bfc63-6207-4efb-9e39-6a47634f1413 on 8000
04.04.20 00:49:53 (+0200) fleet-supervisor Fleet publisher > service.online Fleet subscriber#198c28b2-9d33-4264-8208-8aedfca98490
04.04.20 00:49:53 (+0200) fleet-supervisor Fleet publisher > service.online Fleet publisher#4d9bfc63-6207-4efb-9e39-6a47634f1413 on 8000
04.04.20 00:49:53 (+0200) fleet-supervisor Fleet publisher > service.online Fleet subscriber#44bd3da7-43ff-4d68-b24a-8dd3821cee05
04.04.20 00:43:20 (+0200) bluetooth-audio Setting output volume to 100%
04.04.20 00:43:20 (+0200) bluetooth-audio Connection notify volume is 100%
04.04.20 00:43:21 (+0200) bluetooth-audio amixer: Unable to find simple control 'Digital',0
04.04.20 00:43:21 (+0200) bluetooth-audio
04.04.20 00:43:21 (+0200) bluetooth-audio Restarting bluetooth service
04.04.20 00:43:25 (+0200) bluetooth-audio Bluetooth agent registered
04.04.20 00:43:26 (+0200) bluetooth-audio Starting bluetooth agent in Legacy Pairing Mode - PIN CODE is "0000"
04.04.20 00:43:30 (+0200) bluetooth-audio Device is discoverable as "balenaSound a160"
04.04.20 00:49:39 (+0200) bluetooth-audio Setting output volume to 100%
04.04.20 00:49:39 (+0200) bluetooth-audio Connection notify volume is 100%
04.04.20 00:49:39 (+0200) bluetooth-audio amixer: Unable to find simple control 'Digital',0
04.04.20 00:49:39 (+0200) bluetooth-audio
04.04.20 00:49:40 (+0200) bluetooth-audio Restarting bluetooth service
04.04.20 00:49:43 (+0200) bluetooth-audio Bluetooth agent registered
04.04.20 00:49:45 (+0200) bluetooth-audio Starting bluetooth agent in Legacy Pairing Mode - PIN CODE is "0000"
04.04.20 00:49:49 (+0200) bluetooth-audio Device is discoverable as "balenaSound a160"
05.02.20 09:17:14 (+0100) spotify [2020-02-05T08:17:14Z INFO librespot] librespot (raspotify v0.14.0) 3672214 (2020-01-30). Built on 2020-02-16. Build ID: 7pZDdYUK
04.04.20 00:49:38 (+0200) spotify [2020-04-03T22:49:38Z INFO librespot] librespot (raspotify v0.14.0) 3672214 (2020-01-30). Built on 2020-02-16. Build ID: 7pZDdYUK
04.04.20 00:43:19 (+0200) snapcast-server 2020-04-03 22-43-19 [Info] (main) Adding stream: pipe:///var/cache/snapcast/snapfifo?name=default
04.04.20 00:43:19 (+0200) snapcast-server 2020-04-03 22-43-19 [Notice] (init) Settings file: "/root/.config/snapserver/server.json"
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Error] (Avahi) Failed to create client: Daemon not running
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Info] (start) Creating TCP acceptor for address: 0.0.0.0, port: 1705
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Info] (start) Creating HTTP acceptor for address: 0.0.0.0, port: 1780
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Info] (PcmStream) PcmStream sampleFormat: 44100:16:2
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Info] (PcmStream) metadata={
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Info] (PcmStream) "STREAM": "default"
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Info] (PcmStream) }
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Info] (onMetaChanged) onMetaChanged (default)
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Info] (PipeStream) PipeStream mode: create
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Info] (start) Stream: {"fragment":"","host":"","path":"/var/cache/snapcast/snapfifo","query":{"chunk_ms":"20","codec":"flac","name":"default","sampleformat":"44100:16:2"},"raw":"pipe:////var/cache/snapcast/snapfifo?chunk_ms=20&codec=flac&name=default&sampleformat=44100:16:2","scheme":"pipe"}
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Error] (PosixStream) Exception: end of file
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Info] (start) Creating stream acceptor for address: 0.0.0.0, port: 1704
04.04.20 00:43:20 (+0200) snapcast-server 2020-04-03 22-43-20 [Info] (main) number of threads: 4, hw threads: 4
04.04.20 00:43:34 (+0200) snapcast-server 2020-04-03 22-43-34 [Notice] (handleAccept) ControlServer::NewConnection: 172.17.0.1
04.04.20 00:43:34 (+0200) snapcast-server 2020-04-03 22-43-34 [Notice] (handleAccept) StreamServer::NewConnection: 172.17.0.1
04.04.20 00:43:35 (+0200) snapcast-server 2020-04-03 22-43-35 [Info] (onMessageReceived) Hello from b8:27:eb:64:3d:7b, host: a160d19, v0.19.0, ClientName: Snapclient, OS: Debian GNU/Linux 10 (buster), Arch: armv7l, Protocol version: 2
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Info] (main) Adding stream: pipe:///var/cache/snapcast/snapfifo?name=default
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Notice] (init) Settings file: "/root/.config/snapserver/server.json"
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Error] (Avahi) Failed to create client: Daemon not running
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Info] (start) Creating TCP acceptor for address: 0.0.0.0, port: 1705
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Info] (start) Creating HTTP acceptor for address: 0.0.0.0, port: 1780
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Info] (PcmStream) PcmStream sampleFormat: 44100:16:2
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Info] (PcmStream) metadata={
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Info] (PcmStream) "STREAM": "default"
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Info] (PcmStream) }
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Info] (onMetaChanged) onMetaChanged (default)
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Info] (PipeStream) PipeStream mode: create
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Info] (start) Stream: {"fragment":"","host":"","path":"/var/cache/snapcast/snapfifo","query":{"chunk_ms":"20","codec":"flac","name":"default","sampleformat":"44100:16:2"},"raw":"pipe:////var/cache/snapcast/snapfifo?chunk_ms=20&codec=flac&name=default&sampleformat=44100:16:2","scheme":"pipe"}
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Error] (PosixStream) Exception: end of file
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Info] (start) Creating stream acceptor for address: 0.0.0.0, port: 1704
04.04.20 00:49:40 (+0200) snapcast-server 2020-04-03 22-49-40 [Info] (main) number of threads: 4, hw threads: 4
04.04.20 00:49:51 (+0200) snapcast-server 2020-04-03 22-49-51 [Notice] (handleAccept) ControlServer::NewConnection: 172.17.0.1
04.04.20 00:49:52 (+0200) snapcast-server 2020-04-03 22-49-52 [Notice] (handleAccept) StreamServer::NewConnection: 192.168.1.136
04.04.20 00:49:52 (+0200) snapcast-server 2020-04-03 22-49-52 [Info] (onMessageReceived) Hello from b8:27:eb:64:3d:7b, host: a160d19, v0.19.0, ClientName: Snapclient, OS: Debian GNU/Linux 10 (buster), Arch: armv7l, Protocol version: 2
To clarify, is this the log from the first unit, or, from the second device?
Additionally, is it safe to assume that you have speakers connected to the second device, and are not hearing any audio output? If so, are those speakers connected via Bluetooth or via the line-out on device number 2?
Sorry for all the questions!
It’s the log from the new unit (second unit).
At the time I was testing I haven’t yet connected anything to the second unit, as the tutorial said that any new unit in the Application would automatically connect itself to the master unit.
Second unit was connected to speakers via line-out.
@DanielFrank there may be a situation where if you add a second device to the application whilst you’re already broadcasting to the master, that you’ll need to disconnect and reconnect, as the new device may have missed the signal to tell it which device is the current master.
The logs you shared above seem to indicate it’s working, near the end you can see where it says that the StreamServer is 192.168.1.136. This should match the IP address of your master device shown in the balenaCloud dashboard.
Keep us posted on how you get on; if there’s any way we can make the project easier for folks to get up and running we’re always interested!
Alright, I got it working by rebooting both units. If I come across further issues I’ll let you know. Thank you for your help so far.
Hi @DanielFrank, glad to know it’s working. Is your second device a Raspberry Pi Zero?
Even if you add a second device while the master device is already streaming, the second one should sync up fine. We’ve seen the Pi Zero fail doing this, so I’m interested in knowing if it’s an instance of that, thanks!
Hi.
I’ve just installed BalenaSound on my Raspberry Pi 3.
No sound from Airplay connection.
The Raspberry icon on my dashborad shows a small “3”.
I can’t tell if it’s 32 or 64 bit.
What should I check?
Thanks.
Hi !
I’ve just installed BalenaSound too on a raspberry pi3. I did this with the 64bit version. It’s easy to pairing my devices to the raspberry (by BT) but there no sound out from the HDMI or 3.5 jack port…
I’m new to this and I don’t understand what is going on…
PS : For information it gives me that king of messages on the “logs screen” :
18.04.20 17:59:22 (+0200) bluetooth-audio /usr/bin/bluealsa: Missing RTP packet: 1247 != 1244
18.04.20 17:59:22 (+0200) bluetooth-audio /usr/bin/bluealsa: SBC decoding error: No such process
18.04.20 17:59:22 (+0200) bluetooth-audio /usr/bin/bluealsa: Missing RTP packet: 1250 != 1249
18.04.20 17:59:23 (+0200) bluetooth-audio /usr/bin/bluealsa: SBC decoding error: No such process
18.04.20 17:59:23 (+0200) bluetooth-audio /usr/bin/bluealsa: Missing RTP packet: 1280 != 1278
What is RTP Packet ? Where and how could I get this ?
Thanks,
Ben
@marcopux on the dashboard, in the application list, there is a column called Architecture, if it’s 64 bit, the value will be aarch64. You can also see this in device summary page Type: Raspberry Pi 3 (using 64bit OS)
@eksadi3 can you try to use 32bit os?
hi, i ve tried both 64bits and 32 bits versions on my raspberry pi 3 with a DAl allo boss but i get no sound.
i ve disabled integrated audio RESIN_HOST_CONFIG_dtparam “i2c_arm=on”,“spi=on”,“audio=off”
and added this for the DAC BALENA_HOST_CONFIG_dtoverlay allo-boss-dac-pcm512x-audio
that s all i did, am i missing something?
thanks.
Hey,
Is the overlay for allo-boss-dac-pcm512x-audio installed into the boot partition?