I know a certain latency is to be expected when syncing all rooms, but I think there is much room for improvement. What experiences have you made? Any suggestions?
Have you looked into the SOUND_MULTIROOM_LATENCY setting here: Customization - Home to see if that helps?
Yes, it doesn’t improve anything. The thing is. after freshly restarting the services the latency is about 1-3 seconds, which is fine, but then when I want to play something a few days later, it is about 15 seconds, which is just not bearable.
1 Like
This is really my problem to. If you reboot both devices the latency is like 1-2 seconds, wait a couple days of them being on and then its around 15-30 seconds delay… must be some kind of bug or something?
1 Like
@apfsx, if you don’t need multiroom, then setting SOUND_MODE to STANDALONE will generally decrease command latency. See Customization | Balena Sound
I have the same problem. I have four instances of BalenaSound running. the SOUND_MODE for two of them are MULTI_ROOM_CLIENT while the rest are MUTLI_ROOM. One Multi_Room device is on a wired connection and is currently the only multi_room device that can broadcast to the other balenasound devices. The other Multi_Room device is on a wireless connection and is not able to connect to other balenasound devices, unless the whole fleet is restarted. The Mutli_room_client devices are both wireless.
Prior to installing my HATs (currently 3/4 devices have HATs), the latency was something like 18-30 seconds, which is far too much to enjoy using balenasound. My original suspect was the overheating and it still is, considering I have one device that is missing a HAT (which runs at around 52-55C).
For reference, the other devices run between 47-52C.
My current latency is somewhere between 2 and 18 seconds.
I used to set the latency, prior to installing the HATs (it didn’t really seem to help much) and have just reapplied the latency setting. Will do some testing over the next few days and report back.