Let me know if you’re able to select a zone, and if you’re able to adjust volumes from that zone as well. If you arent seeing Marcel available, try disabling and re-enabling it from the audio settings page.
I’ve enabled System Output and can play music on the Mac mini’s internal speakers. which is obviously less than ideal. I only use the Marcel zone, normally. At present, I can not select Marcel or any other zone.
. . . . three hours later.
Everthing works the way it should!! Roon Core is back to normal and is accessible from any of my devices. What made the difference>. Beats me, but I rebooted the M50.2 earlier today and music actually comes out of the hi-fi now.
Thanks for all your help and persistance Ben! If there are any relapses, I’ll let you
know. Fingers crossed
Well, declaring victory was a little premature on my part. Core is inaccessible again and rebooting the M50.2 doesn’t work anymore.
Later still . . . Every thing is working again.
But to carry on re your last question: at the moment, I can select other zones in Settings>Audio and the zone zone picker. Am also able to to control volume in the chosen zone. I usually have every zone set to fixed, however, as I only ever play Roon through the hi-fi system.
These sporadic outages/recoveries have me a little spooked, so I’m reluctant to retire the topic just yet.
(Smoke me a kipper, I'll be back for breakfast!)
Split this topic
Thank you for the update! I’m glad to hear the system has come back around, if only for a short period.
These sporadic outages sound like they could be network related. If possible, could you give your network and router a hard reboot, and reconnect once your setup has fully restarted?
From there, if you do run into another dropout, could you please send over a specific timestamp or two of when this happens? From there, I can have our team take a deeper look into what is happening at the time of the dropout.
I hard rebooted both network and router and Roon seems to be working as it should. Over 24 hours have passed without a recurrence of the disappearing Core, so I’m feeling a little more optimistic. If (when?) the problem returns, I will let you know. Thanks again. -David
On May 28 I initiated a support inquiry on this forum. As of today, July 6, my Roon Core is still inaccessible despite sporadic and brief periods of Roon functioning as it should, I made the mistake of declaring the problem solved after one daylong interlude where everything was fine. Three days later, the topic was shut down by Roon and sure enough, the problem had resurfaced.
@Ben Cap is the rep who had assisted me and he recently stated that the difficulty had been identified and there would be an update which would neutralize the problem, My fingers are crossed, but the amount of time I’ve spent trying to restore Roon to a functioning state I find unconscionable. In short, Roon is a great product when it works but often it doesn’t. At which point, you’ll wish you had a degree in network administration, since your only recourse is to this forum and other far flung locations on the sprawling Roon web presence,
I have my doubts about a business model that places so much of the tech support onus on the shoulders of the consumer. Is Roon too sophisticated for its own good?
Thanks for reaching back out, and my apologies for any confusion here! As @Carl mentioned, the system will auto-close threads once a solution has been found. I’m sorry to hear you’ve run into this issue again!
Unfortunately, we don’t have specific identification on the issue you’re having (perhaps you were thinking of a similar issue where many users had their cores stuck on initializing?)
A few things to note, if possible, please update all your Roon devices to the most recent build (988) and see if that helps.
We’ll need to enable diagnostics on your account and grab a set of logs from your Mac Mini to better identify what might be going on.
Please use the directions found here and send over a set of logs to our File Uploader? Please include a timestamp of when you are attempting to establish connection, or when you lose connection to your core. This will help the team pinpoint things more specifically.
OK @Ben, I’ll see if I can get the logs to you, but I can’t use Roon in any capacity at this point, even on the install lMac Mini. Roon is listed there among its applications, but I get the pulsing Roon logo when I try to connect…
Thanks for sending them over. After review, it appears that your Mac Mini is functioning as expected, even with it being able to play music yesterday (Chris Potter on a Sunday sounds like an excellent combination!)
Are you still having issues, David? If so, are they occurring on another device, not your Mac Mini?
HI Bern, Yeah the problem persists with brief periods when I can use either one of my remote devices or the Install Mini to play music. I have no clue what brings about these remissions, or what causes the problem to recur. Today, I was able to use Roon Core to play an album for about 5 minutes, for instance. I’m trying to be zen about this, because my NAD M.50 enables me to play all my files using BluOs without recourse to Roon. but the Roon UI is so far superior to BluOs that this workaround I\s less than satisfactory. Do you suppose Roon and BluOS are conflicting with each other? The M.50 is supposedly Roon Ready.
Our team had a chance to review your log set again, and was able to find repeating logs that are pointing towards network difficulties. Here is a snipbit:
07/10 10:19:48 Warn: [rnet/RnetJsonClient] failed to connect Connection refused
It is difficult to pinpoint specifically what might be going on, but signs are pointing to your mesh network. If possible, you can examine your network in more detail using the Fing app. It’s also worth double checking that you’ve disabled any firewalls around Roon.
If you haven’t already, you can also completely unplug your mesh network, and reintegrate back into your setup to see if that clears it up.
For issues with your iPhone dropping connection, try turning off “enable Lock Screen controls” in the set-up tab of settings. We’ve seen this help some users in the past.
I apologize for not being able to provide more details here David. Our team would like to investigate a fresh set of logs, if you could send over another set that would help us continue to look into things for you.