· Other
· None of the above
· Other
Some (most) radio stations not functioning
I run Roon on a Sonicorbiter and use a Sonore Bridge to send a UPnP stream to my NAIM streamers. It works great. I run Tidal, my own collection on NAS, and I love to stream internet radio, especially the FLAC stations, using Roon. Everything is ethernet wired. No problems, until now...
Hi @John_Carter1,
Thanks for reaching out to us for help with this issue. I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
Hi Daniel
Thank you for replying. I just tried again. 1700 GMT March 13, 2025. Same problem. I go to Roon Live Radio, select for example, Radio Paradise Main Mix. This is a station that has worked fine for years. I click ‘play’. The player begins. It tells me what’s playing. The signal quality indicator shows it’s a FLAC station. But no sound arrives, and then it cancels the selection, going back to the start where I would have to select ‘play’ again.
This is the case for most stations. An exception is Sveriges Radio P2, a Swedish station broadcasting with a FLAC signal.
BBC stations now appear to be working. But Soho Radio, another local station, does not.
I cleared out ‘My Live Radio’ so these aren’t old presets, I’m playing from the Roon lists.
My UPnP is playing fine through Roon. The music folder for that is on the same Sonicorbiter as my Roon. Tidal is also playing fine through Roon.
It’s just those pesky radio stations.
Thanks you for your help.
Hi @John_Carter1,
Thank you for the follow-up - these details help us narrow down the issue significantly.
Let’s summarize the evidence we’ve accumulated:
Most importantly, these symptoms accumulated suddenly without an obvious change to your network topology, settings, or Roon configuration.
We’ve pulled diagnostics as indicated above. Here’s what the RoonServer on the Squeezebox reports during live radio interruptions:
The URL requests to stations sometimes take longer than usual. Sometimes, they are rejected entirely. The latter case is unusual. Do you have any network security or firewalls active that might be filtering traffic?
The downloads can’t feed the Sonore Bridge fast enough - the buffer is empty when the firmware expects it to have received data. This causes the endpoint to request a teardown of the audio stream. Sometimes, audio has finally reached the buffer by the time the teardown is received by RoonServer, so music might play briefly, and then stop.
Taken together, this strongly suggests that DNS settings in the router might play a part. I’d enter your router settings administration page and verify that a reliable DNS server is assigned, like Cloudflare (1.1.1.1) or QuadNine (9.9.9.9).
If there are managed components anywhere in this network connection, please elaborate on the software and topology involved.
Thank you!
I am also having no problem playing the same stations directly from my streamer without using Roon. My equipment is Naim, not the latest generation. (I use Roon to play mainly FLAC stations which I can’t play directly from my streamer, and Hi Res Tidal files.)
So it’s unlikely to be a problem in my network if I can play the same stations using Naim but not using Roon.
The problem arose around the same time as I installed the latest Naim firmware, which was required due to changes in NAIM’s radio provision. Is there perhaps an IP address issue? Or something in the new firmware that isn’t playing nicely with Roon?
Many thanks
John
Hi @John_Carter1,
We understand your resistance to tinker with network settings, but the errors in RoonServer diagnostics point to a network, not a firmware, cause.
With a Sonore streamer in between RoonServer and the Naim, RoonServer will not be interacting directly with the network interface of the Naim. We haven’t identified any errors related to the connection between the Naim and the RoonServer instance in logs.
RoonServer logs show requests to upstream URLs are either failing entirely or, if they succeed, are taking longer than expected. As a result, the buffer on the Sonore will eventually fail and the audio stream tears down.
Reviewing logs from before the last several day, we also see download failures with Tidal content.
In Roon, the symptom would be a long delay with the playbar either at “0:00” or entirely empty of content after attempting to play a station URL.
How does the Naim’s pathway to the main router differ from RoonServer’s? What is the network topology involved?
The Sonore is handling the UPnP audio stream to the Naim in this chain, but we can see the Naim’s UPnP announcements in RoonServer logs as they reach it over the network. If you haven’t tinkered with your DHCP settings in the router admin page and only have one subnet, it’s unlikely to be an IP address issue. You might investigate whether there are settings related to UPnP timers in your router admin page, and add some time to the expiration on those. That’s likely not the cause of this issue, however.
We want to see if a managed network component is inadvertently restricting RoonServer’s internet connection or scheduling packets in a way that Roon doesn’t expect. The more precisely we know this network topology, the better we’ll be equipped to assist.
Thank you!