Hi @support - here’s a question from from a puzzled newbie
Looks like I got the “white screen with pulsing Logo” sickness - just checked the knowledge base and did everything that is mentioned there (delete Tidal access, reinstall core, re-boot NAS, Mac, etc.) - unfortunately no success. Logo still beautifully pulsing
Anything else I can do to get access to my library?
Background: Core on Synology NAS, Mac Book Pro as client, everything updated with newest releases, big collection, initial scan, was working well (albums coming in continuously) until yesterday. Since than: NAS working like hell, but on Mac only pulsing logo.
To me it looks like Roon is caught in an infinite loop, and - while busy working on it - loosing it’s connection to it’s core on the NAS. I choose “Look for another core” - Roon is initializing, it takes a while, re-connect, and pulsing logo again … hmmmm
Help is really appreciated
Thanks for sharing your report with us, @Bernhard_Krusche!
May I ask that you please provide a brief description of your current setup using this link as a guide.
Make sure to describe your network configuration/topology, including any networking hardware currently in use, so we can have a clear understanding of how your devices are communicating.
Is this only happening on the MacBook remote? Are other remotes able to connect okay?
Thanks for jumping in - my network configuration is very simple.
There’s a standard router (CBN, provided by my provider Vodafone), NAS is connected via LAN, DHCP on, Roon remote access via WLAN (Macbook & LG mobile on Android). Most basic configuration I can think of
Not only my MacBook isn’t able to access Roon - tried it with my Android, same story. And it already worked quite well - Roon was visible and busy collecting Albums and is running for about 4 days now. I didn’t touch anything, suddenly there was only the White Screen with Logo … really strange.
Is there anything else you need in order to understand what’s going on?
How big is your collection?
Quite big - around 14 GB.
But I was waiting quite a while (around 30 min) before I get impatient watching a white screen with pulsating logo ;
I have enabled diagnostics on your account so our technical staff can get some more insight into what’s going on here. The next time your Core is active a diagnostics report will automatically be generated and uploaded directly to our servers
Once that’s been received, I’ll be sure to update this thread and pass the diagnostics over to the team for further analysis.
The diagnostics report has been received and I’ve passed it along to our technical team for analysis. In order to get them all of the information they’ll need for their investigation, may I ask that you please verify the following for me:
- What is the model of the NAS you are using as the Core? Is the Core stored on an SSD?
- Does the same behavior occur with both the NAS and MacBook connected via Ethernet?
it’s a Synology DS 1813+, with the core stored on SSD.
Connected Macbook and NAS on LAN = same behaviour.
And NAS is doing wild things - all disc lights are flickerung constantly since 2 days, means this machine is heavily working. If I restart the NAS, it continous to do so right from the start … never had that before, especially for such a long time …
And theres’s another thing that might be interesting: after a while, hanging with the white scrren, Roon says: Do you want to look for another core? I say: Yes. It starts looking for a few moments, than showing my NAS again, initalising, and ready to connect. I re-connect, and the same loop starts again …
Thanks for the details here, @Bernhard_Krusche!
I spoke with the team regarding their analysis of the diagnostics report, and we’d like to propose a test that should give us some greater insight into what you’re experiencing.
- Stop all instances of RoonServer on the Core machine
- Locate your Roon database according to these instructions
- Rename the entire Roon (or RoonServer) folder to
- Relaunch Roon, sign in, and configure a new install (note - don’t add your watched folders just yet).
Try to connect to the Core with your remote once you do this. Are you able to connect or do you still experience the same issue?
unfortunately I’m travelling the next few days, so I dont have access to my NAS. I’ll check that asap, and let you know the results …
Thanks, @Bernhard_Krusche! No rush at all here. Whenever you try this just let me know and we can move forward with next steps from there.
Alright - I*m online again. Did every step as mentioned above, and it’s no problem to connect to the core. So now?
My apologies on the delayed response here, @Bernhard_Krusche!
I’m glad to hear that you were able to connect after doing this. Next go ahead and ad back in your watched folders — Are you still able to connect after doing so?
Dear Dylan, after setting up a new core (and updated to the newst version of Roon) I started to add my folders on the NAS. Didn’t re-onnect to Tidal yet, though. Roon started to add files, so everything seems to work fine. After adding app. 9500 albums, Roon starts to slow down - I’am able to see the running process indicating files quite fast, but adding albums / titles is very slow. It takes around 5-10 minutes for each album. That means some weeks of work for the NAS? Switched off file normalization in order to save computing power, but still no speed. Rebooted Core, restarted NAS, no difference. Looks like Roon is having some trouble when it comes to bigger libraries?
Any idea how to speed up this process?
Thanks for the update, @Bernhard_Krusche.
I noticed that the Core machine you’re using for your Roon Core falls short of our recommended specs.
Because this device uses an Atom processor you may experience performance issues, particularly with larger libraries or DSP.
It sounds like the Core machine may be having trouble with size of the library in use. How many tracks do you have total in your library?
It may be better to try using the MacBook Pro as your Core machine. The processor in the MacBook Pro should allow you to have better performance than the Synology.
Hm - that’s too bad. Don’t want to use my notebook for that. And hard to believe that the Synology NAS is already outdated to use Roon. It’s definitely not a low spec machine, especially this model…
So, is it simply that Roon will take some time to scan the library, or do you expect serious limitations when using it in daily life?
Library is quite big, but if Roon is made for serious music lovers it should be able to deal with big libraries, don’t you think? I mean - who else is collecting a lot of music?
It can - but it also relies on the underlying hardware to have sufficient horsepower available, and the Intel Atom CPU in this Synology NAS simply can’t handle it…
That means: Roon will not run properly on this machine? Taking some time to create it’s library would be OK, but using Roon afterwards should work like expected. Do you think Roon will work smoothly after indicating all the files in my library?