Multiroom playback out of sync after few tracks [Investigating]

[Bandi92 (Daniel)]

Hello everyone!

I have the same problem for 2 or 3 months.

I group 3 NAIM devices in my playback multirom: ND555, Muso Qb2 and Muso 2.

The Muso 2 desynchronizes after 20 minutes of playback. The ND555 and the Qb2 are and remain perfectly synchronized.

No problem before, any idea?

Thanks in advance,
Daniel

[Bjorn_Levidow]

I have created this feature request to keep track of this issue. All Naim users who have experienced this issue, please upvote it.

[stevet]

Thanks, you got there just before me

[stevet]

I have created a second feature request to enable zone group delay for Airplay devices

[benjamin]

Hi @stevet,

In the meantime, we noticed that Naim also released new firmware in October, we’d be curious to see, if it’s possible - to get in touch with Naim support directly and ask to rollback to the previous firmware version, and test if the same issue occurs.

Let us know if you’re able to give this a go! Thank you

[Bjorn_Levidow]

Naim released yet another update on 12/18/2024, version 4.4.1 (6600). I’m going to update to that and see if it fixes the issue. I’ll report back.

[stevet]

I’ll let you know what they say @benjamin
I tried that @Bjorn_Levidow but it made no difference for me sadly

[Pascal_Coumans]

Hi, same here; updated Naim Mu-so and Mu-so QB with latest version but on RAAT they go out of sync where Airplay remains in sync. Hope can find a fix… Both wirelessly connected, was not a problem until end of 2024 when I first noticed. Airplay workaround but would be a shame if that’s the final outcome.

[Axel_Lesch]

Same issue with the Mu-so Qb 2 update also appeared in my setup today.
I tried everything, changed master clock priority and zone grouping delay, ungrouped the zone and restarted the system, regrouped the zone > the effect lasts about a quarter of an hour, for a few tracks, and then drifts more and more apart. The issue is limited to RAAT. The same problem seems to have been going on at Bluesound for a time without anything being done?
Unfortunately, Raat’s multiroom capabilities were a main factor in my decision to use Roon.

[Axel_Lesch]

A correction to this:
I reset the Mu-so to factory settings, then reconnected it to the network and was surprised. The December update for the Mu-so apparently did not go through correctly, even though the Mu-so showed exactly that and no update was available.
Anyway, after the factory reset, the update I had already done was shown as available again and after that everything seemed to work as it should. Super pleasing if it were like that and if it stayed that way
Quite relieved at the moment, obviously in my case the culprit wasn’t Roon.

[Pascal_Coumans]

Thanks for addition Axel; tried the same, however remained on 4.4.1, as was apparently already correct. And RAAT problem persists unfortunately.

[Axel_Lesch]

What a pity. I would have wished the same for you.

[stevet]

@benjamin I’ve been in touch with Naim. They have been very responsive but ultimately unable to help us that much.

• They are not able to roll back the firmware for both technical and legal / commercial reasons.
• Interestingly they have not been able to replicate the issue. I asked for details of the setup they have but they couldn’t give that many details - a range of network environments and Roon version 2.0 - if by this they mean the Sept 2022 release then that might be significant
• They are not aware of the issue other than my report
• This has not been flagged to them by the Roon software team.

I tried doing a factory reset on the Muso 2. It came back on version 4.4.1 but as for @Pascal_Coumans it didn’t fix the issue.

I’ve also updated Roon to 2.0.46 but with no effect

[Axel_Lesch]

Hi all,
Since you’ve already tried so many things without success, you might try restoring a Roon backup that was created before this September update:

RoonOS (Nucleus / ROCK) 2.1 is live!

Hello Everyone, We’re excited to announce the latest release of Roon OS, now featuring native Tailscale support! While many users enjoy seamless connectivity with ARC, we recognize that some encounter challenges due to ISP restrictions, router configurations, and other technical issues. To address this, we’ve integrated a simple Tailscale setup into Roon OS. You can now enable Tailscale with just a few clicks. Note that you’ll still need Tailscale running on your phone for ARC, but the setup o…

Why I want to suggest this:

Issue with database corruption

@benjamin @daniel Can I chime in here, I’m not sure if I should start my own thread about this? (NUC 7i7 Rock, Ethernet, no switches, all wired, 1700 album library, nearly all Qobuz) Starting with the September update I have had similar symptoms. Until suddenly at the beginning of the year a blank screen appeared that prompted me to the Database Corruption Help Pages. Shortly before, I had cleared an extraordinarily long queue that would have run for two and a half days. After rebooting the…

After restoring a backup created before September 26th, a number of problems previously unknown to me disappeared.
Since then everything has been working fine again, the delays and other oddities are gone.
However, my server runs on RockOS and I don’t know when the corresponding update for other systems was released.
In my case it was the update that introduced native support of Tailscale.
It might be worth a try.
Good luck.

[stevet]

Thanks for the suggestion @Axel_Lesch. I installed a backup from February last year but it made no difference.

[stevet]

@benjamin I took my Muso over to my dealer to investigate this further using his setup - a Muso 2 running older firmware (4.3.2) and an ND5XS2 with upto date firmware. I set up a group with all three devices and played from Qobuz. The playback from both Musos got out of sync with that from the ND5XS2 after about 30 mins whereas the playback from both Musos were in sync with each other. Conclusion for me is that it’s not related to the 4.3 - 4.4 firmware update, nor to my network, not to my Muso 2

Whilst I’m no nearer to a solution to this, hopefully this is usefull information for you guys.

[Bjorn_Levidow]

@stevet : So, no Roon in the mix at all in this test?

[stevet]

Sorry for not being clear. Roon was part of this @Bjorn_Levidow