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.
Bluetooth issues seem to relate to;
opened 05:56PM - 07 Jun 21 UTC
After several attempts, versions, dongles and configurations, it is very frustra… ting not to be able to make a technology work that was presented to me as easy. Really the entire deployment is easily accessible and hassle-free, until you want to make it work in practice. From then on, nothing else worked, playback lasts around 3 seconds, the errors presented (SBC decoding error (-2), Unsupported fragmented SBC frame) left me very unmotivated, there is nothing clear about these problems, just comments that lead us to other factors like power supply and bluetooth adapters that don't result in any solution. A feather.
opened 10:46PM - 04 Dec 19 UTC
bluetooth
bug
Experiencing regular sound cutting off when using bluetooth project suggested he… re:
[https://www.balena.io/blog/turn-your-old-speakers-or-hi-fi-into-bluetooth-receivers-using-only-a-raspberry-pi/]
I added a new DEVICE CONFIGURATION variable, ‘RESIN_HOST_CONFIG_dtoverlay’ and set its value to ‘pi3-disable-wifi’ but this seems to have no effect - although I can no longer connect to the Pi 3 from the BalenaSound interface (because the wifi on my Pi 3 has been turned off, ironically) and so cannot change anything else now. Nor do I know how to turn wifi back on again since I can't PuTTY into it either...
Some discussion already here:https://forums.balena.io/t/balenasound-blueooth-audio-on-raspberry-pi-3-sound-skipping-dropping/40894/4
but I cannot connect via ethernet either. Device marked as 'Offline' by Balena web-interface.
Can anyone suggest a possible fix to this, please? I’m semi-competent with Pi but do need simple, clear instructions to guide me.
Without a fix this glitch is just too annoying to live with.
I would buy a dedicated bluetooth receiver for my stereo but I felt that re-purposing a Pi 3 would be more appropriate and allow me to stream via a DAC slound card that I am going to add to the Pi (if I can fix the sound issue).
Thanks in advance.
Nibbos
PS please don't ask for output files from the Pi since I am no longer able to communicate with it as a consequence of turning wifi off,
All in all - getting the feeling that the Pi 3 is not the ideal hardware…
I had this problem on BalenaSound version 3.6.5 so I went back to 3.6.1 and now it works again.
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!
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.
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,
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?
Hello @froghorn , were you able to test the downgrade? Let me know if you still need help with this.