I thought setup of MR had gone perfectly; Sonic Orbiter site found MR on my network and the MR found my DAC, ‘hw 0,0’. I activated RoonReady and it is listed as Active in the Audio App Switcher. From the perspective of MR setup, everything looks perfect.
But Roon won’t find MR on my network. Have rebooted and restarted everything at least ten times. It’s been over 24 hours. Seems odd that I don’t have to do something on the Roon app to tell it to look for the MR, as I had to do with the SBT.
I must say that MR customer service has been fantastic. Looking forward to having this problem solved quickly.
Not Odd at all. The SBT is the odd duck in terms of setting up things. Roon broadcasts on your network all the time to see if a new endpoint has come online. When a new endpoint comes online, it responds to the broadcast and Roon automatically adds it in the network section. My guess is that broadcast is not getting to or from the MR for some reason.
The reasons can be different, two of the most common to check are:
There is a firewall setup somewhere between the core and the MR, if so, try turning it off and it that works, set an exemption so it lets Roon’s packets through.
Somehow the IP information for the MR and the Roon Core are on different subnets, for example, 192.168.1.1 for one and 192.168.0.3 for the other. So check the IP’s for each. If this is the problem set the one which does not conform to the rest of your network to match.
Hi jack, it depends on which number is different. In the example I gave above, the difference that matters is in the 3rd set of numbers. as shown by the ?'s in the following (192.168.???.xxx). If the difference is in the 4th set of numbers (where the xxx is in the example) then that is correct as no 2 devices can share the exact same IP number.
There were two primary problems, one of them a PEBCAK: The Ethernet cable to the MR was wired to my Comcast home-base router, which does not have a good wifi signal so I have an Apple Extreme also wired to the Comcast router. To me, something of a noob, even though the Comcast and AE are two different machines, I looked at the whole hard-wired system as one network (internet coming via coax into Comcast router, which is in turn hardwired to MR and AE), but in fact the Comcast router and the AE were two different networks.
My RoonCore is a MacBook that has the AE as its default network; I assumed that as Roon was looking for the MR it would backtrack through the hardwired system from AE to Comcast. This was an erroneous assumption on my part. It was not searching the Comcast router’s network and therefore could not find the MR, so I instead ran the MR’s cable to my AE. Even though that was the first step in the right direction, it did not fix the problem.
On the second problem, to be perfectly honest I haven’t the slightest clue how JR solved it. I’m not sure if I’m breaking protocol, but after many, many emails back and forth between J and I to no avail, he asked for permission to access my laptop through a 3rd party software. I could watch his cursor moving between various parts of the SO site that had identified my MR, from Apps to triple-checking the Custom DAC page to DAC diagnostics, activating Shairport and Squeezelite. He asked me to powercycle the DAC a few times and at one point it appeared that maybe he was reloading the MR software even though I was already running v2.3. After powercycling the DAC for maybe the second time, there was Roon Ready on my Roon page.
It has been working very well since. For the record, I enjoy the MR very much, and am simultaneously not sure that it trounces the SBT as much as I hoped it would. There have been a few instances where a song will stop playing and I have not gotten it to play high-res files yet, only Tidal thru Roon. I am not sure what the high-res problem is. I’m so relieved to have the issue solved that I’m going to enjoy it for a few days before I start fiddling again.