Cannot Connect to Roon Core

Roon says it cannot connect to roon core.

REMOTE
core i7-5500
12GB Ram
64-bit windows 10 home
Wifi Connection to Linksys e1200
70.36.57.66

CORE
Intel Atom N2800
Windows 7
4GB Ram
Wired connection to Linksys e1200
70.36.57.66

Music is installed on external HD
Tidal opens and plays on its own. JRiver opens and plays. Problem is just with Roon and only started acting up recently. Message is “Waiting for Remore Core…”.

I recently switched to audiophile ethernet cables and while unlikely, I noticed the issue after that. When I switch back to old cables, it does not fix issue.
I also believe there was a windows update recently

I connect remotely through both my dell laptop and a Samsung Galaxy 7

My suggestions:

  • Reboot the router and both machines
  • Check any firewalls to make sure nothing is blocking Roon.
  • Try hardwiring the Remote, just rule out any Wi-fi router issues.

As an aside your Roon Core machine is under the recommended specification.

Missed this, it suggests issues lies with the remote PC, but still worth trying all of the above.

You are running Roon core on an Atom processor and with 4GB of memory? Surprised it works at all.
I had an Atom machine, it was the punkest thing going. Running the WIN10 GUI brought it to its knees.

Can you use the Atom for your endpoint and the i7 for your core?
It seems you have the machines reversed as far as functionality.

You know, your core machine can also act as an endpoint. That is, if you need in endpoint in the room where your i7 is, you can also put Roon core on that machine.

I ran the JShiver server on the Atom without a problem, but JShiver works differently than Roon core, so don’t use that as a yardstick.

@xxx Perhaps I don’t understand what you’re suggesting. The atom has a sotm usb interface and is optimized for audio. It’s fanless and hard-wired in a cabinet to a stack of gear.

@Carl unfortunately, your 3 suggestions did not resolve the issue. To clarify, I have no access to roon at the moment.

My set-up with 2 remotes (laptop, phone) and 1 core media server has worked flawlessly for the last 11 months but I understand if hardware requirements are not enough and I’ll consider my options going forward.

Is there a way to roll back the version of core?

Hey @Aaron_Learmont,

Because this device uses an Atom processor you may experience performance issues, particularly with larger libraries or DSP, or if you don’t use an SSD for your Roon database.

It’s hard to say whether the issues you’re experiencing are related to performance, but we do like to give people a “heads up” when their system is under spec, since it can impact the product in a number of ways, and you may encounter some limitations going forward.

On the Core machine are you running Roon or RoonServer? If you are using the all-in-one Roon installation, are you able to access Roon from the Core machine directly?

Can you confirm that you’re able to access this machine outside of Roon from one of the remote devices (i.e. navigate to it over the network using File Explorer or through other apps)?

For various reasons, downgrading to an earlier version of Roon is not supported.

Thanks,
Dylan

I’m suggesting that you run Roon core on the i7 and RoonBridge on the Atom. You can leave the SoTM USB interface connected to your Atom. You don’t need to change any hardware at that end or any end. Just reverse where the software is installed.

The core on the i7 should be set up to communicate with your Atom endpoint via WiFi or Ethernet.

An Atom w/4 GB or any amount of RAM is not powerful enough to run core.

Maybe we should agree on terms -

Roon - the whole software package - core, Remote (control), output
Roon Server - Roon core and output
Roon Bridge - the endpoint interface for output
Roon Remote - Roon control and output

You can run Roon (the whole package) or RoonServer (just the core part) on your i7 and RoonBridge (which deals with output) on your Atom. Roon or RoonServer will communicate with RoonBridge via WiFi or Ethernet.

The way you have it set up is backwards, with the punk machine doing core duties and the more powerful i7 with 12GB of RAM acting as an endpoint or maybe just as a Remote (control).

You need to move your external HDD, that has your music files, from the Atom to the i7.

@dylan @xxx I have switched to using the laptop as the Roon Server and atom-based server as a bridge and I’m back in business. Thank you all!

I’m still having trouble thinking about where the processing is now taking place (either with local files or through tidal). Won’t there be a sound quality penalty to involving my laptop (which is a multipurpose device) as more than a remote?

Running core on one machine that communicates with an endpoint over WiFi or Ethernet is the recommended way to use Roon. Whether a laptop adds noise or not is an open question; you probably won’t notice anything. After all, you been satisfied running core on an Atom.

In any event, you’re better off now than before.

1 Like

“Running core on one machine that communicates with an endpoint over WiFi or Ethernet is the recommended way to use Roon.” - interesting that. I’m just looking to get a NUC in a fanless case which I was going to connect directly to my hifi; would you recommend actually leaving the NUC as a complete standalone server core and outputting through my PC to hifi as a remote?

Depends on how you need to connect to your hifi. In my case, I need to have my ROCK NUC directly connected via HDMI to my receiver for multichannel playback; therefore I transplanted the NUC into a fanless case. If you are connecting your NUC via USB to your hifi system, then some will argue that it is better to connect over ethernet. Personally, I doubt whether I would hear the slightest bit of difference; YMMV.

Cheers Geoff, sounds like we have the same setup, so I’ll stick to HDMI output to hifi from the (once I’ve bought the NUC and set it up!).