I found the following information in a 2019 thread:
"To have more than one server (core) in the same network is possible. But keep in mind that:
You can’t use them in parallel when you have only one license.
Even if you have more than one license, you can only control one server at a time with a given control device.
You can’t stream from more than one server to a given output device at the same time." – Thanks BlackJack!
This would seem to answer my question. But to confirm before blundering forward with what I’m planning, it seemed prudent to ask & be certain!
Currently, my Roon core is installed on a DIY HTPC which contains >16tbs of music. I was wondering if I could install a 2nd. core on our QNAP NAS? Based on the above, it appears that I can.
My intent is to use the NAS’s 2nd Roon core for multi-room music streaming. This would be for elevatior/background music, when the 1st. HTPC core is shut-down (because the 2-channel audio room isn’t being used). Also, the NAS would contain a fraction of the music on the main core.
With that said, while I have Alexa speakers, it appears that there is no easy way to stream a Roon core’s files to them. Unless that is not true? Thus, I was thinking of obtaining Google Nest mini’s for that purpose.
Does Roon “play nice” with Google mini’s in a multi-room configuration? Using an Android phone as a remote, it would seem like Roon would just “find” the mini’s when they are on-line and I would be good to go.
How’s my plan? Might I be missing some logic, or a step or two?
You can have as many Roon cores as you want with only one license, but can only activate one at a time. However, you should be able to play music to multi-room locations from your current Roon core. You don’t really need a second core unless there is some reason you want to shut down your existing core.
You can control the Roon core from anywhere is your house that has WIFI access to your router using phone, tablet, or computer.
Do you intend buying a second licence? Otherwise, you’ll need to constantly authorize / deauthorize every time you switch cores. For your scenario, that doesn’t seem practical. Two licences will enable you to run them simultaneously on the same network with their library and database.
Roon does not work with Alexa devices, but will work with Google Minis (Chromecast). There are some limitations grouping non-RAAT audio zones. IIRC, you need to group these in the Google Home app first, but hopefully a Chromecast user can confirm this.
FYI I created Google Cast Groups on the Google Home app. Roon sees these groups.
But I’d imagine you could also create endpoint groups (or whatever they’re called) in Roon.
Roon sees my Google Cast Groups as well as the individual speakers (as separate endpoints)
*. It not only serves music to the big rig in 2-channel room in the basement, but it serves video to the 85" TV it is adjacent to. It never runs when the big rig (38-tube monoblocks and 8’hx3’w speakers) isn’t running and rarely runs for video, and it would never be necessary for multi-room background music.
Thanks Placebophile (BTW, good moniker), it’s good to hear that “Roon plays nice with Google Minis in multi room.”
Having 8 Alexa speakers, I generally use Prime’s non-HD music, but am limited by those offerings. But now and again it would be great to have access to some control and the use of my own tracks and playlists.
Not knowing, I would assume that authorization/de-authorization is a fairly simple process of a couple button clicks. Whether that is the case, or it is finicky and not always repeatable the first time, I would appreciate advice regarding the process. I’m disabled and futzing with what were once minor details, like plugging in interconnects or an A/C cord, is no longer the case.
But getting back on topic… I can understand why you want 2 cores. Personally, I’d buy a second license or I’d move that loud box somewhere it can stay on all the time.
Swapping or de-auth’ing a core is easy. You’ll point a remote at a Core without license. It will tell you that Core has no license and reference the Core holding license. You click on deauthorize. You may need to login to do this. Then the remote works as normal on the new Core.
I don’t really have much experience with multiple cores so hope others will chime in with experience. Realize, your “background” core will be offline when your main rig is running. Multiple people in the house might notice this. Another reason just to use 1 core for everything. If I had to explain to others in my house the 1 license multiple core thing I’d be single.
Thanks on the core switching advice! It’s good to know authorizing/de-authorizing was as I expected, no problem. One of the things among many, I found attractive about Roon, was that the interface once established, is rock-solid and just works!
Only wife and me in the house. So, no problem with the “background” cores. But thanks for the advice. It would definitely be important for some.
Never quite understood the gnashing of teeth over a background noise quandary. Most non-“silent” PC’s are fairly quiet and unless one is nearby, music and video generally overshadow what little, if any noise there is. For example, when there is no sound in my home theater room, the projector can be heard. But have some minimal sound and it can’t be heard. Of course, if one is mic’ing an Audyssey or Dirac pre-pro, the noise floor is very important. But yes, my HTPC is fairly loud. I threw more fans in it than maybe necessary, because of other’s having heat issues with the Corsair case and multiple HD’s. But a bat couldn’t hear the HTPC from the audio room in the basement with HTPC upstairs.