I updated my MacMini M4 from MacOS 26 to 27 without a problem with the Roon Server.
(MacOS 27 is not meant to run on MacMinis with Intel).
I updated my MacMini M4 from MacOS 26 to 27 without a problem with the Roon Server.
(MacOS 27 is not meant to run on MacMinis with Intel).
You’re the second person to say that you didn’t have a problem with MacOS 27 but what’s with the big banner from Roon at the top of the forum list on how to get around the devices problem then?
My system is not working. Tried the “terminal” fix above. No luck. I’ll wait for the official fix. Initially thought my Auralic Vega G2 had died.
And there were more who at least could fix it by the usual network permissions switching, before the banner went up.
Then this didn’t help for someone and after investigation they came up with a workaround involving the terminal and the scary banner went up.
Yes, it is strange. Maybe the more severe issue affects only a subset of machines? I don’t know
I can’t answer your question to the banner and its content since I had no issues when upgrading.
For obvious reasons with multiple systems, SW stacks and protocols interacting from different vendors on each user’s computer(s) and network(s) - you may want to postpone the upgrade until most issues have been identified and ironed out or work arounds provided by one or the other vendor.
Why wasn’t this issue identified and resolved when MacOS27 was available in beta?
Because Roon developers don’t have the ability to change the internal MacOS sandbox code. Only Apple developers can help Roon and that won’t happen.
Won’t happen? Are you saying some people won’t be able to use a Mac as a server to run Roon?
No, I’m not saying that. Roon requires some OS knowledge and networking knowledge by user. That said, I’m not sure of your level of Mac OS or networking knowledge, so I’m not referring to yourself by that statement. Maybe try upgrading and then if it doesn’t work for you, follow the workarounds as already provided by Roon to get around the Apple issue.. If you do run into an issue, there are many knowledgeable users here in this community that will be willing and able to assist you. ![]()
So it will never be fixed? And it wasn’t detected when MacOS27 was in beta?
Nobody said that. Apple might fix it or Roon Labs may implement a solution if Apple doesn’t
There are so many things broken in Apple betas that 3rd-party developers may have to prioritize. It’s also often not clear what Apple will or will not fix until final release.
Generally, recent major Apple updates were so broken that it’s better to wait for the x.1 release. Nobody “has to” update on day one. Aside from Roon, macOS 27 released, for instance, with an entirely broken Mission Control, the central mechanism for window management on macOS
Actually, Jason_McHugh1 said that.
“Because Roon developers don’t have the ability to change the internal MacOS sandbox code. Only Apple developers can help Roon and that won’t happen”
I have at least five Mac computers, and they are running different versions of macOS, ranging from macOS 12 to macOS 27.
Only two of my Mac computers—the Mac Studio and the Mac mini M4—can be upgraded to macOS 27.
After the update, my Mac Studio suddenly could not see some of my endpoints, while the Mac mini had no issues.
The strange thing was that even some of the Macs running earlier versions of macOS 26 or older also stopped seeing the endpoints.
However, when I shut down the Roon Server on the Mac mini, some of the other Macs suddenly became able to see the endpoints again.
When I started the Roon Server on the Mac mini again, the other Macs experienced the same problem.
In the end, I had to run a Terminal command on each Mac to fix the issue.
I had 192.168.50.xx just fine… I did update 8pm eastern… I lost network…
I had macOS 27 and Roon running just fine on my Mac Studio … now only audio available on This Mac…
I had OS 27 and Roon (previous no updated version) running all network devices I had been using for years.
This doesn’t mean it won’t be fixed.
I had no problems with MacOS 27 until I installed the latest version of Roon just now (2.73 build 1694). The banner says that remotes are not affected but Roon remote on my laptop does not connect. On my Iphone it does.
EDIT 1: a reboot of the Mac Mini 4 restored remote access from my laptop.
EDIT 2: a reboot of my DAP (Hiby RS8) restored the connection. My Auralic streamer is also visible, so it seems that everything is still working fine for me with MacOS 27. I hope it gets resolved soon for other users.
My m4 Mac mini is also fine with OS27