I have my ROCK up and running (specs below) but I need to figure out the best Roon endpoints for my TV room and living room.
The ROCK is co-located in the TV room with the internet connected router, NEST WiFi router, Denon - AVR-X3700H 8K Ultra HD and surround speaker setup, etc.
Right below in the living room is the Krell KSA-300S and KRC-3 with another NEST WiFi router with an AirPlay enabled Airport Express connected via RCA to the preamp. There are a pair on unused balanced XLR inputs on the KRC-3 that would be ideal for a Roon endpoint.
There are also a pair of Sonos speakers in the kitchen, a single in the bedroom and in the office along with more NEST mesh nodes. I can live with the sound from the Sonos speakers, but Iād like to get the best bang for my buck on appropriate Roon endpoints for the Denon and especially the Krell. Iād hoped the ROCK could be coerced into service as an endpoint since it sits on top of the Denon receiver, but no joy based on my research. Suggestions?
You canāt use HDMI out on the NUC to the Denon AVR? The Denon should support AirPlay (my Marantz does) so you could AirPlay from Roon to the Denon but HDMI out from the NUC to Denon would be better.
As for the Sonos stuff Roon can supposedly (I donāt have any Sonos stuff to verify) use Sonos devices as audio devices. Do any of them show up as options in the Audio settings of your Roon remote?
I get that there is no āConnected to coreā section, there never has been on my ROCK build. I have no idea why that might be since the build is fairly turnkey, especially since I used the recommended hardware.
Weird. Everything functions, in that you can play to other endpoints, right?
I guess, if it were me, I would try to attach a DAC to a USB port on the ROCK and see if that showed up.
As long as ROCK installed and your other endpoints work, then I shouldnāt think so. I guess anythings possible, although I never screwed around with BIOS to get the basic outputs connected to Core.
I suppose youāve rebooted everything, probably several times at this point.
The Sonos speakers and all the devices running Roon remote (my iPhone, MBP, iPad) work fine too. Itās just getting the best audio to the Denon and Krell setups that Iām trying to figure out.
If I had a USB DAC, Iād certainly have tried that. Trying to figure out what my optimal choices for endpoint hardware was, after all, the starting point of the post.
If anyone from Roon has any insights on why my ROCK/NUC might be showing no āconnected to coreā devices, and whether thatās a config/bug/feature issue Iād be delighted to know.
Just to confirm, the reboot option and I are well aquatinted enough that weāll need a room soon.
Did you make any changes to the BIOS to begin with? Iāve got two different NUCs and donāt recall seeing any BIOS options regarding HDMI but there are audio related options. Maybe one of those?
The MacBook Pro was the original Roon Core, but having the server stop running every time I closed the lid got very old. I migrated and deauthorized the MBP to bring up the ROCK/NUC.
Just in case I had a case of terrible space dementia I closed the lid of my MBP just now and Linda and Nelson continued playing, so I think Iām safe saying itās not my Roon Core. And then there is thisā¦
The instructions about configuring the BIOS were directional and not step-by-step. I flashed the updated BIOS as instructed and then went in to make the configuration changes, but found the documentation didnāt match the actual BIOS UI. I only changed things that were required: Enable legacy boot/disable UEFI, changed boot order, etc. I made no changes to anything else that wasnāt required.
I used the link to the specific NUC on Amazon from the Roon article to avoid the unexpected. However, given the mismatch between the documented process and what I had to do, there might have been something changed in the updated BIOS.
Since the ROCK/NUC was sending the screen output over HDMI to confirm it was running, and display the URL for the system status page, I donāt think I did anything to the HDMI options.
BTW - Kudos for understanding you werenāt giving away the keys to the kingdom by not hiding your IP. Many people believe that 192.168.0.xxx is a deep secret that only they should know.
Iāve been there. Just last night, as a matter of fact.
Anyway, tagging @AceRimmer or anyone who can move this thread to the appropriate section where more ROCK users might happen upon it.
Good luck.
AceRimmer
(Smoke me a kipper, I'll be back for breakfast!)
20
Trying to figure out what my optimal choices for endpoint hardware was, after all, the starting point of the post.
