It would seem the Roon client solution is network jitter sensitive which in turn can break the multiroom synchronization. The team here have spent a few days trying to replicate this one and there is quite a stack up of demands for it to break. We’ve been waiting a week for a reply from Roon on this, but overall they supplied the code / solution and we want guidance on this one.
Once we get feedback from Roon we can then Work out the best way to go on this. From our side we haven’t changed library for quite a while but Roon and multiroom synchronization bugs are not a new thing.
Apologies we can’t get more concise advice for now, but this is really all Roon code and we have no control over it.
Thanks for the fast response. I am still unsure why it happens to me within 10 minutes of using the Muso with 4.4.1 where as the other two with 4.3.1 are used all the time and in perfect sync? If it was a Roon issue would it not be happening to the Musos with 4.3.1. Sorry to harp on but I am trying to understand
jitter in that network. Typically from distance from router / other wifi devices all sharing the sane link.
Muso/qb s810 streaming card.
Roon multiroom
Roon got back to me and we’re going to go over things with their CTO, as Roon multiroom has always been a trouble maker and be nice to get to the bottom on what is going on.
When the test team first supplied me results from the measurement it was in theory all working to spec. I then requested a wider range of test conditions and this then started to expose that something maybe on the edge.
When I wrote Muso/Qb I mean its all the same streaming platform, the code is the same so it doesn’t really matter what product is used. However, replicating this bug is not easy and as shown from your own setup you see it on ethernet, not wifi (I assume you’re on the same code for all?). We couldn’t replicate it on Ethernet without using network simulation tools to add in network jitter.
Hence why I believe this is all right on a knife edge of working. The most subtle of things have likely changed and the algorithm in the code for synchronization ends up out of spec.
@Stevesky I have reported to Roon at 16:52 CET one of the Musos went out of sync and continues to be so. It has Fw 4.4.1. The other two musos are in sync with the 4.3.1. Fw. Hopefully you are getting somewhere
For anyone watching this I received this response from Roon this morning:
"Our Partners team will be working with Naim directly on this issue. We’ll share updates as available from behind the scenes, particularly concerning the timeline to resolution.
Please stand by and we’ll have additional comments as soon as possible."
Roon haven’t been able to give us the necessary support on this so far, but we are going down the strategy of re-integrating absolutely very latest Roon RAAT code + glueware fixes. This should be in the next build that should go live in May.
@Stevesky thank you very much for the update, I very much appreciate it. Disappointing to hear you are not getting the necessary support from Roon. They have intimated that they were working with you.
It indicates the key member of staff who can help debug this issue is on maternity leave at Roon.
We did a good debug session on this last week, so goal is that ln the next code release we’ll aim to get this back on the right side of the cliff edge.
This may or may not be related to a Roon specific multiroom issue as discussed here, but I have found a steady increase in sync issues over the last few months. These have been when using Roon, Naim app, Airplay and Qobuz (the latter is a beta issue though )
Been running 3.11 / 4.5.0 for a few hours and it has fixed the problem, works similarly to how it was before the update last year . Sounds great too. Many thanks @Stevesky and the software team for fixing this, appreciated.
)
. Sounds great too. Many thanks 