I spoke too soon… while re-booting the Roon ROCK solved the issue for that listening session, I have now found that the problem returns each time I power cycle the SDH. The only fix I have found is to re-boot the ROCK after the SDH is powered on every time. Once that sequence is complete, all works OK…
The ROCK does not have to be rebooted to play to another zone (a Roon-ready Escape P6 portable speaker). Only to the SDH. And the SDH plays other sources (AirPlay, direct connected TV, etc.)
I have the same/ similar issue, too, since the last 2 releases of Roon.
Every time I power on the SHD and select the zone to play, the SHD gets “kind of initialized” (the display briefly lights up), and the zone/SHD seems to be playing, but there is no sound output and playing indication in Roon soon stops. If I re-boot Roon Server (on a Synology NAS) - while minidsp SHD is still powered on - then playing works.
My current alternative to get the SHD playing instead of rebooting Roon Server is to go into the zone settings and change + save one setting and then set-it back and save again (eg. Volume control: fixed volume >> device volume + save and then set-back + save again) This reliably works but is not a long-term solution…
(other zones, eg. a Sonos Five or MacOS Core Audio don’t show this behaviour)
It happened last night and again this morning… I’ll make note of the exact time it happens next and reply. But it’s still happening. other info:
Roon ver 2.60 (build 1629)
Roon Server version 2.60 (build 1629)
RoonOS version 2.1 (build 271)
OS Version RoonOS version 2.1 (build 271)
What’s odd is that the SDH shows up as a device under “Audio→roon ready” along with the other roon-ready device (an Escape P6Air) even when this issue occurs. Everything plays fine on the P6. On the SDH, though, the device shows up, and clicking “play” on any track has the effect of:
the track time/progress counter/bar NOT intrementing/advancing. stays at 0:00 for several seconds
after several seconds, a move to the next track in the list, which exhibits the same behavior
after moving through a few tracks, a “Too many failures. Stopping playback” message is displayed, and no further attempts to play a track are made.
I can change the device over to the P6, and all works fine. Change it back to the SDH, no joy.
Hey @Jim_Bohlman and others who have chimed in on this thread, thank you for the additional information and reports!
After reviewing a fresh diagnostic report from your Roon Server @Jim_Bohlman, I can confirm you’re unfortunately experiencing a known issue our team is actively investigating. Here’s the link to the tracking thread regarding it:
Any updates from our team will be posted to the above tracking thread. I’m sorry, I don’t have any immediate next steps for you, although there has been some community discussion around potential workarounds.
Our Early Access pre-release testing branch has a constellation of fixes included that target the symptom you’ve reported here.
At your convenience, please follow the steps presented in this article to try migrating your Roon Server and Roon Remote machines to the Early Access branch. This will involve installing the Early Access version of Roon on both machines, and it will not affect your Roon library or customizations in any way.
Joining Early Access will permit you to test the latest Roon fixes and features in advance of their release via a publicly available update.
Here are instructions:
We will also be sharing updates pertaining to this release in the main tracking thread here:
This seems to have fixed the issue for me. Tested several times across a few days from different roon “remotes” (MS PC based and iPhone) and so far, connects just fine on statup without me having to do anything special.