Multi Room Client and Multi Room Server Crashing.

Project help balenaSound
1

New install on a PI 3 Model b V1.2

Tried installing the 64 bit release and then the release that just says “PI 3”

Getting this in the logs:

23.06.21 08:39:47 (+0200)  multiroom-client  - Snapcast version: v0.25.0
23.06.21 08:39:47 (+0200)  multiroom-client  Starting multi-room client...
23.06.21 08:39:47 (+0200)  multiroom-client  - balenaSound mode: MULTI_ROOM
23.06.21 08:39:47 (+0200)  multiroom-client  - Target snapcast server: 192.168.8.103
23.06.21 08:39:47 (+0200)  multiroom-client  2021-06-23 06-39-47.231 [Error] (Snapclient) PCM device "default" not found
23.06.21 08:39:47 (+0200)  multiroom-client  metadata:{"STREAM":"balenaSound"}
23.06.21 08:39:47 (+0200)  multiroom-client  2021-06-23 06-39-47.272 [Fatal] (Snapclient) Exception: No audio player support for: pulse

> 
> TCP) Error reading message header of length 0: End of file
> 23.06.21 08:36:29 (+0200)  multiroom-server  2021-06-23 06-36-29.300 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file
> 23.06.21 08:37:35 (+0200)  multiroom-server  2021-06-23 06-37-35.225 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file
> 23.06.21 08:38:41 (+0200)  multiroom-server  2021-06-23 06-38-41.515 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file
> 23.06.21 08:39:47 (+0200)  multiroom-server  2021-06-23 06-39-47.272 [Error] (StreamSessionTCP) Error reading message header of length 0: End of file

I’m either doing something wrong, have unsupported hardware, or the gods of Docker ain’t digging my groove.

I don’t appear to have audio on the 3.5mm jack - but hard to tell as the bluetooth isn’t very stable against an iphone.

Any thoughts appreciated.

3

Bluetooth issues seem to relate to;

All in all - getting the feeling that the Pi 3 is not the ideal hardware…

4

I had this problem on BalenaSound version 3.6.5 so I went back to 3.6.1 and now it works again.

6

Hey all, this issue was fixed on version 3.6.7 of balenaSound released June 24th. I suggest you update to latest by redeploying your app. Let me know if that doesn’t help. Cheers!

8

Thanks - can confirm this is fixed! Multiroom client and server are now running as they should.

Sadly, still have the problem with bluetooth. Samsung Galaxy S10, connected via bluetooth, start playback (from spotify) - plays for a few seconds and then I get

29.06.21 07:31:11 (+0200)  audio  E: [bluetooth] a2dp-codec-sbc.c: SBC decoding error (-2)
29.06.21 07:31:11 (+0200)  audio  E: [bluetooth] module-bluez5-device.c: Decoding error

Disconnect and retry

29.06.21 07:34:40 (+0200)  audio  W: [pulseaudio] module-loopback.c: Configured latency of 200.00 ms is smaller than minimum latency, using minimum instead
29.06.21 07:34:40 (+0200)  audio  W: [pulseaudio] module-loopback.c: Cannot set requested source latency of 66.67 ms, adjusting to 250.00 ms
29.06.21 07:34:45 (+0200)  sound-supervisor  Playback started, announcing 192.168.8.103 as multi-room master!
29.06.21 07:34:54 (+0200)  audio  E: [bluetooth] a2dp-codec-sbc.c: SBC decoding error (-3)
29.06.21 07:34:54 (+0200)  audio  E: [bluetooth] module-bluez5-device.c: Decoding error

Will try rebooting and connecting with an iPhone instead and searching the forums for this new error.

10

Hello @FrogHorn ,

This seems to be caused by this issue and potentially fixed by downgrading to OS v2.38.0+rev1. I’ve pinged internally to see if that’s still the best solution or if there’s something else in the works.

Cheers,
Nico.

14

Hey @froghorn, we’re still trying to track down what’s happening with that issue. It’s been very difficult to reproduce on this side. It would be interesting to know if downgrading the OS helped at all. Also, you mentioned you were going to try it with an iphone? Any difference there as well?

17

Hello @froghorn , were you able to test the downgrade? Let me know if you still need help with this.