We cannot thank you enough for your continued patience as we navigate this issue. Not being able to access and connect to your core is immensely frustrating and I completely understand the gravity of this bug. I also wanted to thank everyone again for providing detailed reports of the issue.
I have a good update to share: we have discovered a solution to this issue, and are on the final stretch to getting it released to you all. I can’t comment on a specific timeline, but we are without a doubt on the home stretch.
In the meantime, if you’d like, you can download the Roon-all in one app which should connect normally. Let me know if you have any questions, and I will follow up soon with more updates
The basic Roon app, as I’ve circled in red, is also known as all in one, because it is in essence a roonserver and client in one package. However, it can also just be a client if you have another core alredy on the network, when you install it, just connect to that core and the server portion won’t be activated on the PC.
@Matt_Armstrong I think @benjamin means connect locally. So rather than install RoonServer on your Mini you would install the full Roon package on your mac Mini (probably the same one you installed on your MBP), and during initial setup you would choose the option that’s labeled something like “Setup this device as your RoonCore” (sorry, don’t remember the verbiage). Another way to think about it is you would install the same Roon dmg (circled above) on both your Mini and your MBP, but on the Mini you would set it up as the Core and on the MBP you would use it to connect to the Core. Hope that helps.
RoonServer v1.8 (build 970) stable on macosx
macOS Catalina 10.5.7
Mac mini (Late 2012)
2.3 GHz Quad-Core Intel Core i7
4 GB 1600 MHz DDR3
Networking Gear & Setup Details
A number of Google Wifi mesh devices. The Mac Mini is plugged into one of them by Ethernet. I’m able to connect to the Mac Mini with remote desktop.
Connected Audio Devices
n/a, as I can’t connect to the core at all
Number of Tracks in Library
Maybe 2-4K tracks?
Description of Issue
I upgraded the core and updated macOS at the same time. After this I can’t connect to the core. All my Roon remotes say that the core is “initializing”. It has been like this for a few days – I can’t precisely remember, as I left it for a while hoping it would fix itself.
So, a workaround for the problem where Roon Server fails to fully initialize and function is to run Roon instead of Roon Server. However, there is a problem: the two programs look for their database in different places. Here is how I addressed this problem on my Mac Mini:
Consider that I am a casual user of Roon, and this is not a recommendation coming from Roon support!
Log in as the user running Roon Server.
Quit Roon Server. No program from Roon should be running!
Open a Finder window and show the home folder.
Configure Finder to show the Library folder. (View → Show View Options and check “Show Library Folder”. Note: don’t mess around in the Library folder casually, it is hidden by default for a reason.
In the Library folder Ctrl-Click (or Right Click) on the RoonServer folder (within the now visible Library folder) and duplicate it.
Rename the new “RoonServer copy” folder to “Roon”. This is the folder the “Roon” app will use.
Rename “RoonServer” to “RoonServer OLD” (or move it to the Trash).
Bumping, I get this exact issue. Clients say the core is initializing. RoonServer says it’s running. Clients will connect once the Roon app runs on the RoonServer. However, the Roon app crashes almost immediatly.
Thanks again for your patience here! We’ve just released a new build (987) that should clear up any issues related to RoonSever getting stuck on initializing. Please update your core to enable the fix.
hi guys! due the new update some new features like mqa decoder ?
which will the best config?
mqa capabilities … decoder and render? when i select that… the streaming goe sfor 44 , but when i go to no mqa support goes for 88.2
rooopie - anthem str integrated via usb