As I have stated before, I do play records. Check my instagram account at @ongakumeansmusic if you want to see my setup and such. I also made provisions for accessing my local library via MinimServer and the dCS Mosaic app.
But all of this is beside the point. Right now, I have to worry about Roon and I have to make accommodations for when my internet connection flakes out. This, I would argue, goes against the Roon desire to become an appliance-like application.
The key point I am trying to make is that all of this could have been easily avoided while retaining all of the paradigms of cloud-based APIs. This is done in all enterprise-level applications that canāt simply stop working if the internet is out for 1 minute - which happens more often that you think even with the best of connections. I would like the Roon team to consider this and make a fix but I presume that they are knee-deep in the current design and such a change would require some rearchitecture and testing.
As for your test, it just proves my presumption of what the problem is: The Roon code works fine as long as one of the API calls to a cloud-based function is not touched. The moment it is something in Roon will fail. You donāt really know exactly when this will happen.
One more point here: Audirvana (which I own but never use other than for library checks) NEVER fails to play local files. Ever. And searches TIDAL and Qobuz blazingly fast. This is not to dismiss Roonās intention to move APIs to the cloud, just that some software designers like Demien from Audirvana will likely never break the basic tenet that playing local is an absolute must.
FWIW, I started trying to use 1.8 Legacy if/when my internet is out and my 2.0 core canāt be used. I played with it this morning becauseā¦ wait for itā¦ my internet was out!
Bottom line, even if I could get it to work (I didnāt) it would require not only installing 1.8 Legacy on a separate computer from my 2.0 core, cranking it up, and then transferring the license, but would also require using 1.8 Legacy remote software on my phone/iPad/etcā¦ All in all, likely far more trouble than itās worth if itās even possible.
Fortunately, my internet was only out for an hour or so, so my motivation dwindled quickly. And, maybe, just maybe, that is the best response to attempting to stream my local music when the internet is out.
Yes, the remotes need to be on the same version of Roon, either 2.0 or 1.8 legacy. You donāt really transfer you license, you simply unauthorize one core and authorize another core.
@Jim_F - right. Semantics. I meant what you said - unauthorize 2.0 and authorize 1.8 Legacy. But, as @wizardofoz said, I believe you actually need the internet to do the unauthorize/authorize dance.
You can use your cellular hotspot to do this. Before Roon ARC, I did this all the time when away from home. Since Roon ARC, I use Audirvana away from home.
I have a Roon Nucleus at home connected to my AT&T U-Verse ISP. Away from home I use my Dell laptop Roon core connected to the internet by my Verizon cellular hotspot using iPhone or iPads. Itās as simple as falling off a log to open Roon on my laptop and click on āDisconnectā the Nucleus and then āUse This PCā and āUnauthorizeā the Nucleus. What could be easier?
Your situation is not the same to other peopleās situations. I donāt listen to music on the run. I enjoy music from my non-portable systems. Heavy two channel speakers, heavy amplifiers, heavy preamplifier, heck, even a heavy DAC.
I donāt usually listen to music seriously any other way.
I donāt know where the Roon server is located, but youāre talking to it via the internet. Youāre not talking to your own Roon server at your house. Thatās the point.
I was closed to subscribe after my free trial period. However I just discovered that I must be connected to the internet in order to run the software. I was on the plane and wanted to listen my music from Roon (launching a custom playlist that I built from my libraryā¦but it refused to open until I connect to the internet). This is so disappointing. All my music is local (more 5k albums) and I really love how Roon made me navigate to my own library, better than any other streaming plateformā¦but the fact that I was not able to listen to my own music playlist offline (on the plane) is definitely a BIG disadvantage of the software. I am not sure to subscribe anymoreā¦unless the support will explain how to bypass this or will this be plan for a next release?
Just to be clear: I got the point that Roon needs internet to do things like authorization and authentication, gathering data on my local files in order to create connections (even if for this one I am doubting) or display very cool things about music authorsā¦
However, all this should not avoid an offline usageā¦at least for a small period of time. By doing caching or whatever. I am really disappointed. I thought I found THE BEST software for navigating through my musicā¦but this is point is to me a killer
Thatās a very good question and the simple answer is that Roon have just designed the software to work that way now to improve search performance. However, it is unfortunate that one cannot just use Roon as a local file player anymore, as one would Foobar2000 or VLC (navigate to a folder, right click, Play With Roon). This avoids completely having to use a search engine in Roon, just use the OS one.
So either just install a local file player if you have a laptop. Or use Roon ARC on a mobile device with pre-downloaded music, as you would the Tidal player.
One question for you, is it clearly stated on the Roon website that an always on internet connection is now required?
EDIT: to answer my own question it is stated in the Roon KB via the System Requirements page link at the bottom of the pricing/subscription page. Not exactly hidden but not exactly obvious either. Not on the front page of the website.