Wadax Reference Server and Studio Player Out of Sync (ref#XQ4J08)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· I have the Wadax Reference Server and DAC and the Wadax Studio Player in another room. When grouped in Roon they won’t play in time. Everything connected by wires: studio player and ref server via Ethernet to network, reference DAC via Akasa glass optical cable to ref server. I have tried connecting both server and studio player directly to router with long Ethernet cables but they are still out of time. Have raised the issue with Wadax who say they are looking into it, but thought I would ask here too in case there are any settings on the Roon side I haven’t seen. Adjusting resync delay doesn’t seem to do anything, and anyway feels like two Roon ready players from the same manufacturer should just ‘know’ how to play in time! Any help much appreciated - thanks!

Tell us about your home network

· Draytek Vigor 2866 router. I have a Melco / Dela S1 switch and ADOT fibre converter, as well as a Waversa LAN filter before the ref server, but have taken all of these out of the loop and connected straight to router and the problem is still there.

Hi @Josh_Raymond,

Thank you for your patience and sorry for the delayed response here. We’d of course be happy to investigate this report. Group Roon Ready playback shouldn’t be out of sync.

Can you please provide the name of a track that exhibited this issue with the grouped Zones involved? We’ll use this to pinpoint the event in logs. We were able to request logs from the Reference Server instance in question.

Thank you and we’ll watch for your reply.

Hi Connor, thanks for your help. The track I tested a few times with different configurations was Becoming Insane by Infected Mushroom. The beats made the weird timing very obvious! Look forward to hearing what you find out :slight_smile:

Hey @Josh_Raymond,

We reviewed the logs for the issue, but there is a Roon API device at 192.168.137.1 generating so much logging noise that we are not able to review the diagnostics cleanly.

Please temporarily disable that device, then reproduce the issue once more and note the exact local date, time, and track when it happens. If you can capture that precise moment, we should be able to narrow this down much more effectively.

Thanks for the update. How can I find out which device that one is?

Your router will have a list in its admin web page of all devices connected to your network. You should find the IP address there.

Plus, how many devices using Roon extensions/API do you have?