Internet Radio is shaky at best. Playing streams (128k AAC) from DI.FM and encountering stutters and slow startup. Usually I have to start a stream twice to get it rolling. First time I get “Unable to play this station. Its address might have changed, or it may be temporarily unavailable”
At the same time, if I add the same station URLs to BlueOS they work flawlessly without any interrupts, so it’s not a server issue at DI.FM.
We’re sorry to hear about the issue. Usually, this symptom emerges when there is something blocking your Roon Core’s connection to the station server (like a firewall, VPN, etc.), but depending on how you’ve configured your network and what devices you are using for playback, there might be traffic filtering elsewhere in your network that is contributing to the problem.
Can you tell us a little more about your network setup and the conditions during which you experience this error?
Do you have any network firewalls engaged - or antivirus software - that might be filtering Roon’s upstream or downstream connection?
Diagnostics from your account show several Remotes in regular use. Do you experience this internet radio issue with one Remote device in particular (iPhone, laptop, etc.)? What about with any particular endpoint - is one of the Zones you mentioned above particularly cumbersome due to this error?
Do you have any DSP engaged when this happens?
Any issues elsewhere in Roon, like with Qobuz or Tidal streams, or with particularly large, high-quality local files?
Hrm… I think my UDM Pro has a firewall enabled. Since I run Roon directly from a NUC with ROCK installed, it has no antivirus that should interfere? When I am playing internet radio I assume no data gets sent from my client (my laptop for example) to the Roon Server?
Do you have any "best practises for ports or rules that should be opened for Roon to operate well in a Unify environment?
I use multiple remotes. My phone, my laptop, my computers, some iPads… The problems is consistent no matter which remote I use. Also, since this is mainly connected to Streaming (I don’t do playback of local files) I assume which remote I use should not matter?
No I have no DSP enabled right now.
I do suffer some issues with Tidal streams too, but not at the same rate as with internet radio.
It’s worth mentioning that I did also use a bunch of Raspberrys before as endpoints, and with them I didn’t have these issues. I think the issues are related to the NAD CI580v2. I have been posting multiple other threads about this device but got no good response. The issues clearly seems related to when this device is included.
If I playback to my Devialet Phantoms or Raspberry Pi Endpoints I don’t suffer the same problems… also, starting music / changing songs etc is much much quicker when targeting these devices.
The NAD CI580v2 just seems super sluggish and not reliable at all with Roon.
At this point I have had to resolve to using BlueOS only which is a shame… I am here to use Roon but currently it doesn’t work for me … (When I use BlueOS I can playback the same radio stations without any interruptions, as I try play in Roon with massive problems)
I too have suffered frequently from the dreaded “unable to play this station” problem with one of my two Roon setups. It’s a rural location, and internet access comes from Starlink and an OTA service from a local ISP. Both work well, but occasionally have latency problems depending on network congestion
I also have Unifi infrastructure, and use a pair of Devialet Phantoms and a BluSound endpoint, in additional to a couple others. After a recent string of exasperating problems with grouped playback getting out of sync and increased dropouts, I switched both the Pulse and the Phantoms to use Raspberry Pi’s and optical connections. Since switching, my dropouts have seemingly disappeared. Even when I’m streaming in the same group over wifi to an Escape P6 Air.
After looking through logs, I now think there is a problem with the Phantoms using RAAT in grouped playback. My log files have long shown timeout errors every 30 seconds to the Phantoms during playback, even though both have solid wired connections. I’ve come to guess the timeouts sometimes cascade into dropouts and “unable to play this station” errors.
So while using the Pi as a front end makes the Roon interface less elegantly useful (for volume changes especially), it has been very solid since I reverted back to the pre-RAAT days of the Phantoms. I’ve seen other posts about BluSound/NAD endpoints losing sync in grouped playback due to a recent firmware change, but that has also disappeared by putting my Pulse Flex 2 behind the Pi.
So if you have the Pi’s lying around, try putting them back in the chain and see if it solves your “connectivity” issues.
Hey David! Thanks a lot for your response… I did use Raspberry Pi’s in an earlier setup, and that was 100% stable. In that case I used Hifiberry Amp2’s but in this setup I run I need way more out put power so I have external amplifiers.
Right now I only use 3x NAD CI580v2 and I do suffer problems… I don’t even try to have the Phantoms at the same time…
The reason I don’t use Raspberrys is that I found they had an annoying “pop” sound when starting songs (when used as DACs)… Have tried about every DAC for Raspberry Pi and the only one without the pop was Allo Boss2, but they don’t really stack nicely in a rack
I have a setup that is rack mounted… so therefore I got these NAD CI580v2’s which on paper should be ideal…
Btw I did previously use Phantoms together with Raspberry’s in a WiFi environment and in that setup I did have problems. After wiring everything up on ethernet it did become stable though. I don’t think Roon is particularly well suited for WiFi in the way it’s coded. It really requires super stable and solid networking.
… (When I use BlueOS I can playback the same radio stations without any interruptions, as I try play in Roon with massive problems)