In the house are two end points. Often (but not always) when playing music they are out of timing sync creating an awful maddening echo. The two house streamers are grouped. Shop one not playing when this happens.
I can’t sort and would appreciate any clues how to tackle.
If this info matters….House streamers are Lumins. Roon core is on a Grimm MU1 (scored a used one!). Switches are made by Ubiquity.
What streaming protocol are you using to stream to the endpoints? Airplay, Chromecast, RAAT?
RAAT (as employed by Roon Bridge devices and Roon Ready endpoints) is the most reliable for grouping zones and also allows you to delay zones in order to properly synchronise them:
However, you said that the synchronisation is often, but not always, poor. The 'but not always, suggests that a different streaming protocol is in use.
The solution, if there is one, will likely depend upon the streaming protocol in use.
I believe the Resync Delay configuration for the device helps prevent playback issues at the beginning of songs (such as silence or hearing pops/clicks) when playing a DSD track after playing a PCM one (or vice versa). Some devices (DACs) have trouble immediately playing a track that’s a different format from the prior one.
I’m only seeing one Lumin registered to your account with both Roon Ready and Airplay mode. Are you currently seeing both Lumins under Roon Settings → Audio? If so can you share a screenshot of what you see there?
Somehow one of the two streamers in question was set to airplay. (#!$SH*&^) Went into the lumin software and one streamer was no longer set to roon ready. It was once upon a time and how it got unset is a mystery just like having the same streamer using airplay in roon.
Great suffering catfish! I never once have used AirPlay. Sooooo. I deleted roon on my iPad reloaded, regrouped streamers and presto no more echo. Echo. Echooo.
I’m not so far gone having not remembered changing settings. The dog?
We’re glad to hear that changing protocols sorted out the issue. How the Airplay Zone was enabled is something that we’ll likely be unable to answer from remote diagnostics - this type of endpoint activation would require user invention in the interface.
It’s possible if you’d enabled the Airplay Zone in the past that a temporary loss of RoonReady availability causes the Airplay Zone (under the same name) to become listed with higher priority in the Zone picker. I can imagine a case where I would confuse these when selecting a Zone in a hurry.
In any case, please let us know if we can be of further assistance here.