My Raspberry Pi used to stay in synch with my Bluesound Node 2, life was good. But that was a few months ago and many updates since. Now my Pi will drift at least a few seconds per minute so I cannot group it with other zones. The Pi’s timing sounds good when played on it’s own and the Node 2 also plays well on its own.
Any ideas? How do I start to debug this? Thanks!
Config.
Endpoints and core are all on wired 1Gb ethernet.
Core
Version 1.5 build 354, 64 bit
Windows Server 2012
Bridge (Raspberry Pi)
Version 1.0 build 164
Linux 4.14.34-2-osmc
See under Device settings -> advanced, try setting it to 1 to see if it makes any difference. Yes re. convolution, just ruling it out as some filters introduce time delays.
Edit: Also worth rebooting all devices, including your router and any network switches, if you haven’t already.
Thanks for the advice dhusky but sadly no joy. It worked initially for about 30 minutes then I couldn’t get them back in synch no matter what I tried. Will try again once Bluesound confirms a fix.
Very disappointed in the interoperability of these components of a supposedly premium system.
Sorry to hear that - it is curious that it used to work…perhaps @support will have some other ideas to try but I’m not optimistic for you. It is indeed frustrating, particularly when it was first reported to Bluesound at least a year ago.
There is a known issue regarding the Bluesound Node 2 and its synchronization behavior while playing as a part of a grouped zone. Bluesound is aware of the issue and investigating a fix.