I am on the initial two week trial, trying to run the core on an imac with an m1 chip (8ghz, 512 gb ssd). I am also running roon on a macbook (m1 as well). Streaming to a Bluesound Node. The core keeps logging out even though I have the imac set to not go to sleep or shut down, and when I logged back in it said I needed to log out of the core as I had another one set up, though I haven’t done that.
In addition, I have thousands of flac files on an external ssd that are reading as corrupt that I’ve never had issues with playing on any other system, but they read as unable to play in roon, though it categorizes them and in some instances even downloads the album art.
I really want to make this work as if this is operator error this program could make my life easier but the constant logging out (though I have rock solid internet) is a problem.
This is from the iMac. The external SSD is attached to the iMac. This is what I was wanting the core to be, and how it was initially set up. Everything is wifi; the Bluesound Node is ethernet connected to my router coming into the apartment.
Wifi can be hit and miss. It may work for endpoints and remotes (until it doesn’t because the neighbor bought a new microwave) but Roon strongly recommends having the Core on ethernet. Not sure if it’s the issue, but if you can, I would recommend a temporary ethernet cable for the Core at least to rule it out.
I suppose the Node is seen and enabled as Roon Ready in Roon > Settings > Audio? Don’t upgrade its firmware by the way, the latest BlueOS firmware update broke Roon and Bluesound is working on a fix.
Though none of that explains well why the Core keeps logging out. Even if it went to sleep or streaming stopped, it should stay logged in at least. Nor does it explain the SSD reading issue.
We have seen many random networking issues solved by switching the DNS settings on the router from often dodgy ISP-provided DNS services to Cloudflare. And often the affected users first didn’t see why it would help, but then it did So in the absence of better ideas for now I’d start with that.
I think that rules out the possibility that the MacBook is also running a core, and I know you mentioned that that wasn’t the case, but it’s easy to misconfigure Roon when you’re first starting out.
At this stage I’m puzzled as to why Roon would think you have more than one core. Did you just install the main Roon app (for core and control) or are you using Roon Server (core) and Roon (for control)?
So I guess that’s the Roon Server installer on the iMac, the thing without the GUI? This should be just fine and less prone to misconfiguration. (It would be possible to install the regular Roon software on both and set up the one on the iMac as Core, but still use the GUI on the iMac as well. This would have more potential for misconfiguration).
I deleted and reinstalled the apps on both the imac and the macbook. It now shows “Roon Core” on the imac…which I guess is what I’m supposed to be doing? I’m really confused. Should I have server on here?
Install regular Roon on both iMac and Macbook. Regular Roon provides both a control GUI app and the Core (server) software. In this case you can control Roon both from the iMac and the Macbook. And you can choose to run the Core on either. You need to take care that you configure only one of them as the Core.
Install Roon Server on the iMac and regular Roon on the Macbook. The server runs without a visible GUI. You can control Roon only on the Macbook.
(Has the advantage that it uses less resources because it runs no GUI. So if you never want to control Roon when sitting at the iMac you can take advantage of that)
In either case, if you start the regular Roon app on the MacBook for the first time, there should be a configuration screen where you can choose between options like this (stolen screenshot from another thread):
The option at the top, Find my Roon Core (Nucleus, ROCK, etc.), looks for the Core on another machine, in this case on the iMac. Click this to configure the iMac as the Core.
In the lower option, Set up a Roon Core on this Mac, “this Mac” refers to the machine you are sitting at, so this would be the Macbook in this scenario. Don’t click it, because you want the iMac to be the Core.
(Ignore the option at the very bottom, Configure Roon OS devices on your network, this is not for you. It’s for accessing the admin interface of Roon Nucleus and ROCK only)
(If you run regular Roon, and not the Roon Server, on the iMac as well, then the GUI app there would show the same options, but the meaning of the options would be reversed. Then “this Mac” would refer to the iMac and you would click this to configure the iMac as the Core)
Roon works with one machine being setup as a server that should be left on. Other PCs can then have Roon loaded as a client to the main server. Sounds like there are a couple of issues, but, making sure there is only one core running is the first step.
When you install Roon you have an option to use it as the Core. If you install Roon on a second computer, you need to make sure that you choose to connect to the other core instead of “use this pc” or you will in effect have setup two different cores, which is what sound like has happened.
On the PC you don’t want as the core, uninstall Roon. Make sure Roon is running on the PC that is going to be your server. Then re-install Roon. During setup, you will be given the option to choose the other PC as the server. Do so and finish the setup.