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).
Download âRoonâ from roonlabs.com, install it, and run it.
Log in. It found all my local music, was able to play it, etc.
When youâre comfortable with this solution, move âRoonServer OLDâ 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