B1310 Strange Update Process [Ticket in]

[musicjunkie917]

I am running a headless M1 Mac mini with 16GB of RAM, a 512GB internal SSD, and an external SSD for music storage. It was running the Roon server app with no user interface. I am also running HQPlayer Desktop 5 on the Mac mini.

I used the automated process available via the Roon client on a Mac Studio to upgrade. I did this before reading the release notes so I had no idea about the changes.

When the upgrade process was finished, only my Qobuz albums were available. None of my local albums showed up. So, thinking there may be some hiccup, I rebooted the M1 mac mini which I usually do after an upgrade. After the reboot was done, I had access to nothing. I “Screen Shared” into the Mac mini and discovered no Roon apps running. I was not able to find the server app anywhere so I ran the Roon.app. I was given the option of searching for a Roon server or to start up the Roon server on the local machine. I chose the second option. I was presented with a request to allow Roon to access external storage device which I granted. I can’t remember if this request popped up when running the Room.app or when the Roon server app was started.

At this point, my Roon clients were able to see both local and Qobuz albums in my Library. I clicked on the Roon icon in the menu bar and setup the Roon server to run at startup. I rebooted the Mac mini, and again, my Roon clients had no access to my Library. I checked to see if the Roon server was running on the Mac mini and it was not. I checked the to see if the Roon server was in my “Login Items” and its was. I rebooted again, and again, the Roon server did not run. I removed the Roon server from the “Login Items” list. I ran the Roon.app again which loaded the Roon server as I could see it in the menu bar. I again selected the option to have the Roon server run at startup and rebooted.

This time all started as it was supposed to and now Roon server is running on the M1 Mac mini after a reboot.

Of course I now know that Roon changed the apps so I had to allow Roon to access external storage which is why I could not initially access my local Roon Library after the upgrade. The other problems I had with the upgrade process are not see easily explainable. I am posting this in hopes that it might help others running Roon on Mac systems.

[pesky]

Same as @musicjunkie917 post. Running Roon Server on headless Mac mini M1. Same problem, same resolution.

[pesky]

Actually, one difference. After the update, even if I select “Launch at startup?” in menu bar, the Roon Server does not launch at start up. It does however launch just fine if I launch Roon manually, which I can then quit.

[musicjunkie917]

Manually delete the Roon item from “Login Items” and try it again. That is what worked for me…

[pesky]

That worked! thanks.

[wizardofoz (Mr Fix It aka The Wiz)]

I had the server installed in the past and it was set to not run in the menu options…now I just installed the B1310 roon file, then i got this and now it is set to run at startup in the menu icon and the is a new Open Roon option I think

seems its run it up already

Then I had to disconnect from my prod core and start a server on the mac in the remote

when I checked the settings about I see

It might be worth changing the icon for server to something different like the roon logo maybe

Open Roon from the menu option does open the remote and its fine regardless of my remote pointing to my production ROCK server that remains the server. so that’s good…also means the B1310 is still workable with a production Server install in my case ROCK

we now have Roon-Server.app as a component of the Roon.app