Cannot get Roon running

Core Machine (Operating system/System info/Roon build number)
ROCK on a NUC i7, 8GB RAM, 256GB SSD Boot drive, 1TB USB HDD.
Roon remote : Old HP Pavilion desktop running Windows 10.

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
NUC connected to the Router via ethernet.

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

Description Of Issue
I was running the Core and remote on the same HP which wasn’t working. I purchased the NUC to spec from the knowledge base and got it setup fine. The Core crunched through about 375K tracks and now my Core hangs. When I try and load the remote it hangs on the waiting icon and then says waiting for Core. Left it go all night… no change.

I have setup a NUC i7 with 8 GB RAM and a 246GB SSD (also has a 1TB HDD). I connected it directly to my router as advised so it is not in the same room as my audio system. I can load the remote on my old pc connected to my audio system and TV it is asking for audio output but is only showing interfaces connected to the Rock Core. It doesn’t see my DAC. Which was my output device when my core was on the PC. How do I see the DAC now?

I am assuming your DAC connected to the old PC The issue is probably Firewall or Antivirus, try turning them off and see if the audio devices appear.

Ok. I have found the interaction. It was an old VPN software I used to use that was still loading. It occurred to me that as I have it setup now the remote software is getting the files over WiFi now because they are in another room. Will that affect sound quality

Only if the WiFi isn’t working fast enough, when you might hear clicks and pops. You’ll know if it’s there. Otherwise, don’t worry about it.

Thanks for the quick response. I’m trying to reload my library which is now connect directly to the Core. I have a pretty large collection and its having trouble cruching through it. I thought that processing was now done at the Core. I

Got through 77K tracks and it crashed…I have 10X that. What should I expect

Hi Ben,

Processing is done on the Core, where are the files in relation to the core?

Do you really have 770,000 tracks?

I do have that many. Maybe more. The files are connected to the core. It seems like the remote is crashing teyinf to render. I shut the remote down and then restarted it and the cruching was happening unabated. Roon has added 186991 files so far. I dont mind if it takes a long time to add as long as I can run it afterward. I have had a lifetime license for a year or so and am looking forward to having it work seamlessly without crashing. I think you have the best product on the market…if I can get it to run

I am sure that @support will be here soon to provide guidance.

Hi @Ben_Katz,

That’s quite a large database you’re trying to run there, and importing is a heavy process, especially if you’re trying to use Roon at the same time.

Why wasn’t this working? Did you also import the full 700k+ tracks to the HP and it was struggling?

I would start off with a smaller library to see if the size of it is impacting Roon. Can you try to set your current database aside and try importing 100k tracks or so?

  • Create a Backup of the current database
  • Stop RoonServer from running in ROCK’s WebUI
  • Navigate to your Roon’s Database Location
  • Find the folder that says “RoonServer”
  • Rename the “RoonServer” folder to “RoonServer_old”
  • Restart the RoonServer in the WebUI to generate a new Roon database folder
  • Try importing 100k tracks and verify if the issue still occurs

Also, if don’t mind analysis taking a bit longer, but have the system use less resouces during the import process, I would disable or set to throttled both On-Demand and Background Audio Analysis (under Roon Settings -> Library).

I know that it worked with 100k tracks. I was using it after I had imported 277k files.

All. As a first step I unplugged the media from the NUC and the remote popped right up. When I then plugged them back in the remote flashed the black screen and said waiting for the core… again. Can we confirm that my hardware can handle the collection. Also if all of that processing is happening at the CORE why does the remote crash

You need to throttle the machine. Limit it to a single core for importing and analysis.

1 Like

Once I unplugged the media and loaded the remote successfully I throttled both and then plugged the media back in and thats when it went immediately to “waiting to connect to the core” again

If you turn OFF the audio analysis, does it all work?

I didnt do that and I am back at work. I will try that. Again, does the processing power of the remote make a difference?

should not at all, the remote is just a viewing/control mechanism for the server, no processing is done on it.

1 Like

No, since ROCK is your Core here the database will be saved to that.

It sounds like your database size is taxing the ROCK setup too much. Do let us know if there’s a change if you turn off Analysis.

Ok i will turn it off and see. I bought a NUC to the spec for large libraries so I’m concerned what happens if I turn it off and it works?