Settings/General/Library shows which machine is Core. If you have any concerns at all about billing then a quick email or message to or will get it sorted. In my experience the Roon team quickly sort out any issues arising from automatic billing relating to even one licence and I would expect them to be equally responsive where two are concerned. So far as I am aware you will not be automatically billed for two licences at the end of your trial period. configure the HTPC to accept Remote connections in Settings.copy the backup of your laptop database over the HTPC database.completely uninstall Roon on laptop and HTPC.backup your existing laptop database (C:\Users\App Data\Local\Roon\Database).If you do want to retain your existing database then: enter the IP address for the HTPC into the iPad app.reboot the laptop and install Roon as a Remote.reboot the HTPC and install Roon as Core.completely uninstall Roon on the laptop and the HTPC.If you don’t care about retaining your existing database, then the simplest thing to do is: Is there a glossary somewhere defining your usage of “core”, “remote”, “endpoint”, “private zone”, “Roon speaker”, etc.? Just so we can all be on the same page?Īside for those issues and a few other minor points of confusion typical of any new software system everything is going swimmingly. I ended up reinstalling under the normal user account (I probably did have to give an administrator password in order to complete the second installation). No sign of Roon anywhere, no launcher, no executable, search for “Roon” or “roon” turned up nothing. When non running Roon on the laptop the iPad app finds nothing, even when I enter the IP address for the HTPC… Am I going to be automatically billed for two licenses? Shouldn’t the account page have information somewhere as to what machines are licensed as “core”? If I understand your usage correctly I still want the laptop to be a “remote” machine.Īnother weird thing that happened while installing on the HTPC: I installed under an administrator account as is customary then switched to a normal user without password account I would normally be running. Now the iPad remote app does not see the HTPC but still sees the laptop when running Roon. (is it because I am still in trial mode?) I logged into my Roon account but was never prompted to unauthorize the laptop. I followed the above procedure but it did not play out as described. I then wanted to move it to my HTPC (core i7 Ivy Bridge in HDPLEX fanless chassis running Windows 8.1). ![]() ![]() I tried Roon on a laptop under Windows 7 for about a week. Hope this helps! We’ll be publishing more information about RoonSpeakers in the near future. Private zones will remain private–they’re meant to address a different set of needs, and we don’t want to create confusion by creating two mechanisms to accomplish this. This package is meant to solve your exact use case. It would be accessible regardless of whether the remote is running/connected, and would behave just like an MS200–discoverable and controllable from anywhere on the LAN. However, we’ll eventually be releasing a standalone RoonSpeakers package that runs as a service. You can initiate playback (from computer A’s library) from computer B to its own “private” zone, but other devices can’t play to computer B’s private zone, unless your stereo is a shared network endpoint. You can then launch switch to a remote on your first machine.Īs far as your remote question, we don’t support that configuration just yet. Unauthorize the first machine (you’ll be automatically logged out), and authorize the new one. When you attempt to launch it as a core you will be given an error message that says you’ve already authorized your first machine, and you’ll see an option to unauthorize it. Hey if you want to move your Roon core to a different PC, just go ahead and install it on the 2nd machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |