I’ve merged your reports to have all the information in one thread. I wanted to touch base with some good news, we’ve been able to reproduce this issue in the QA lab and have submitted a ticket for the team to investigate this further!
That just says “we strongly advise”. Not we will deliberately release an update that will make your old core stop working. If that was the case why not issue a new release and then just say that you can keep running the old release but Roon won’t get any better. That way those of us using old macOS systems can make a decision to live with it an old system or upgrade our cores.
I have had one response ( Cannot see DAC on Mac 10.12.6, Build 904 - #31 ) but its not looking good as to whether it will get resolved given the time elapsed and the fact as pointed out above we are running an OS version behind the advised minimum requirements.
Just following up on my colleague @Yaohan’s response earlier. We apologize for the troubles you’re having. This is a known issue that we’re currently working on a solution to. This emerged from a recent build and effects machines that are running on Mac OS that don’t meet our system recommendations of 10.14+.
Please follow this thread for further updates. If you’re unable to use Roon entirely and you have another MacOS machine running 10.14 or later (or a Windows machine) you can migrate your Core to that and restore Roon immediately.
The roon core (the one that I can’t access the audio outputs) is on an iMac (10.15.7) that is also the where the dac to the main system is physically connected (usb-denafrips aes conveter - dac on active speaker), and library HDD. It’s connected to the network via WiFi. I have another iMac also WiFi (10.13.6, because it supports standalone Lightroom - very important). That’s the “control terminal” for the system.
It doesn’t see the the core’s audio sources and won’t find roon OS from the Setup page.
And neither do any of my roon iPad/iPhone remotes.
All up to date.
Nothing in my system had changed (i did update the roon core’s OS to the latest supported following forum advice). It worked beautifully till the 903 and subsequent builds.
Just to be clear, what you’re saying is, it’s the remote iMac (10.13.6) that’s pulling down my system, including access from the remote iPhone/iPads?
All your control/remotes and core need to be on the same IP address range. Core should as recommended by Aron be on a Lan point connection and not WiFi.
In hopes of fixing this problem, I just upgraded my Mac Mini where the Roon Core resides to OS 10.14.6. That is also the computer that is connected to my sound system. However, I still have the same issue where the core does not show up as an audio device. The other computers I use to control Roon Core are able to see the following audio devices:
Laptop running 10.12.6: Does not see the core or itself. Does see a Chromecast enabled tv.
iPhone 13 Pro running 15.3.1: Does not see the core. Does see itself and the Chromecast tv.
Laptop running 10.13.6: Does not see the core. Does see itself and the Chromecast tv.
Hoping to get this resolved asap. Roon has been nonoperational for 22 days now. Thanks.
Everything has been peachy for nearly two years with no variation in my system config. The only change was the update to Build 904+ which broke roon.
You seem to be suggesting that from Build 904+ (404?), roon doesn’t support WiFi?
From looking at your system diagnostics you’re running Roon Server, not Roon (all in one). (Edited: previous wording Roon Core was a poor choice as Roon Server is Roon Core) Let’s start by getting your Roon Server machine wired to ethernet. As a rule we strongly suggest a wired LAN connection for Roon/Roon Server. How did you migrate Roon Server to that machine?
Where are you looking when you’re unable to see these devices? The Audio page, the zone picker or both? Can you post a screenshot please? You won’t see Roon OS unless you’re using Nucleus or ROCK. That part is normal behavior.
The underspec Mac on 10.13.6 shouldn’t interfere with normal functioning of your iPad/iPhone remotes. Can you tell us what you’re experiencing on those devices? Is the behavior the same, you’re unable to see devices?
Can you post some screenshots of what you’re seeing on your problematic devices? I’m particularly interested in what you’re seeing on your iPhone. Thanks!