"Limiting Roon Radio to library" with Tidal (2020-12-02)

Core Machine (Operating system/System info/Roon build number)

Windows 7 Ultimate
Intel i5-6600 CPU @ 3.3GHz
Roon 1.7 (Build 667) 64bit

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Router: Google Nest Wifi AC2200
Switch: TP-Link Gigabit unmanaged switch
Roon Core is hardwired to switch

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

MacBook Pro
Windows 10 PC
Windows 7 PC
Chromecast Audio
Apple TV
and more

Description Of Issue

I am a Tidal subscriber. I am new to both Roon and Tidal. I have a large library of local music. I have 767 plays so far in Roon.

I am receiving “Unexpected Error: Limiting Roon Radio to library” and “Roon Radio: Nothing Similar To Play!” errors when initiating Roon Radio.

I have tried several different Radios including the suggested Beatles: Abbey Road Radio.

I have restarted Roon Core (3) times.

I have logged in and out of Tidal.

My DNS is set to “Automatic” within Google Home on the Google Nest Wifi Router which is currently set to “”

Here is a screenshot of the error occurring on my Macbook Pro. I get the same error on iPhone, Windows, and OSX.

This seems to happen once in awhile.Having same issue tonight.

I’m having the same problem. Just started happening a few hours ago. I’ve tried reconnecting tidal, rebooting both my Nucleus and the roon app to no avail. Tried it with the beatles etc without luck.

I have the same error, it happened few hours ago

12/02 18:17:49 Critical: [easyhttp] [67] Post https://swim.roonlabs.net/1/session/begin web exception without response: : System.Net.WebException: Error getting response stream (ReadDoneAsync2): ReceiveFailure
at System.Net.WebResponseStream.InitReadAsync (System.Threading.CancellationToken cancellationToken) [0x000f3] in :0
at System.Net.WebOperation.Run () [0x001d9] in :0
at System.Net.WebCompletionSource1[T].WaitForCompletion () [0x00094] in <e62def21d44c48f3979e0652288240b1>:0 at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <e62def21d44c48f3979e0652288240b1>:0 at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <e62def21d44c48f3979e0652288240b1>:0 at System.Threading.Tasks.TaskFactory1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func2[T,TResult] endFunction, System.Action1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in :0
— End of stack trace from previous location where exception was thrown —

at Sooloos.EasyHttp.QueryAsync (Sooloos.EasyHttp+HttpMethod method, Sooloos.EasyHttp+Params p, System.Threading.CancellationToken canceltoken) [0x006d9] in <5477466545d54656a739f37f07f53905>:0
12/02 18:17:49 Critical: [mlradio] [2] failed to init swim: System.Exception: /session/begin failed: 999
at Sooloos.Broker.Music.Radio.SwimProxy.Begin (System.String profile_id, System.String user_id, System.String broker_id, System.Collections.Generic.IList`1[T] collections, Base.JDictionary seed, System.Int32 n_items, System.Int32 n_preplay, System.Boolean verbose) [0x001fd] in <1295ddc8c6aa41c3af1d916e70716b94>:0
at Sooloos.Broker.Music.Radio.MLRadioSession.Init () [0x007e1] in <1295ddc8c6aa41c3af1d916e70716b94>:0

Thank you for your feedback Peter, Karen, and Jason. This issue appears to have resolved itself. @Outlaw, how often does this happen? It’s not a big deal to me I was just worried there was something wrong with my specific Roon install since it’s so new.

To be honest, I didn’t know Roon Radio utilized Tidal until I got the error message! Which makes me curious, Is there a way to limit Roon Radio to only your library? I could see myself using both if so.


Sorry for the trouble here, everyone. There was a temporary outage last night that our team resolved, so everything should be up and running now.

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.