Live radio stops and starts

@support I have an issue where radio plays for about 3 seconds then stops for three seconds.

Sometimes the station is not loaded, but then loads.

Normal music is fine on Roon, I can play all radio to the same Sonos speaker directly without any issues.

It’s all Ethernet connected with no network issues.

Currently I’m using Roon for music but have to use Sonos for music, I was hoping to move to one control app.

What can cause these issues, I am running an old Mac book pro on Linux as the core.

Cheers Phil

Can you access the MP3 streams? There is an ongoing issue with AAC files in Roon.

1 Like

Yes that works, updated my default to mp3, thanks Chris.

I wonder if this will be resolved, I know the BBC have caused streaming issues on certain platforms.

There is an open ticket on this, I find I cannot play AAC files locally or via Tidal. I have a QNAP core.
I find I cannot group Meridian and Bluesound zones either.

Hello @Phil_Ryan, I’ve moved your posts to #support. As @Chrislayeruk says, there is a known issue with .aac streams at the moment, and the more data points support have the better.

On the second point of stations sometimes not loading, a couple of us are seeing this too. I suspect that is to do with Roon’s backend servers and I hope should be sorted soon.

1 Like

Even on mp3 I seem to get intermittent cut outs which are not seen on Sonos.
For radio it makes Roon unusable and Sonos must be used as a reliable source.

I’ll monitor for improvements and await conformation of a fix.

@support as @BrianW mentioned there is definitely an issue with Roon’s Live Radio backend services.

Hi @Phil_Ryan,

The next time you see the Station Unavailable message would you kindly make a note of the time it occurs as well as which station you were trying to open? We’ll enable diagnostics and take a look.

Thanks!

15:29, although they both appeared after retrying.
BBC Radio 2 and BBC 6 music

I don’t get the stop/start error, but I do see station unavailable temporarily. Swapping back and forth between stations produces it after a bit.

A 404 error is returned.
Relevant bit of log…

Summary

11/02 16:28:17 Debug: [easyhttp] [3801] GET to https://internetradio.roonlabs.net/2/api/stations/9465e0f1-c88a-4d4d-bef8-9f6aa277b536?format=msgpack returned after 186 ms, status code: 304
11/02 16:28:19 Debug: [easyhttp] [3802] GET to https://internetradio.roonlabs.net/2/api/stations/7c828d71-6de4-4a86-962f-6f5c0b5e2072?format=msgpack returned after 180 ms, status code: 304
11/02 16:28:21 Info: [stats] 22829mb Virtual, 2011mb Physical, 634mb Managed, 276 Handles, 65 Threads
11/02 16:28:22 Debug: [easyhttp] [3803] GET to https://internetradio.roonlabs.net/2/api/stations/e109ae35-563e-4542-bd42-297d515cfc27?format=msgpack returned after 189 ms, status code: 200
11/02 16:28:24 Debug: [easyhttp] [3804] GET to https://internetradio.roonlabs.net/2/api/stations/7c828d71-6de4-4a86-962f-6f5c0b5e2072?format=msgpack returned after 176 ms, status code: 304
11/02 16:28:29 Debug: [easyhttp] [3805] GET to https://internetradio.roonlabs.net/2/api/stations/826c932e-5a68-4c5a-b713-7d12149cccbd?format=msgpack returned after 180 ms, status code: 200
11/02 16:28:31 Debug: [easyhttp] [3806] GET to https://internetradio.roonlabs.net/2/api/stations/b7e2260b-19bb-464e-b284-9a538bc09144?format=msgpack returned after 181 ms, status code: 404
11/02 16:28:36 Info: [stats] 22829mb Virtual, 2011mb Physical, 636mb Managed, 276 Handles, 64 Threads

EDIT. Did my best to reproduce, and now can’t.

Thanks @Phil_Ryan and @BrianW — I’ve passed a report along to the QA team on this and will follow up once I have their feedback.

1 Like

Hi @Phil_Ryan,

Can you give some details on the network setup? I had a chat about this with the team today and around this time they’re seeing some errors in the logs that are seemingly network related — It looks like your machine tried to communicate with our servers to pull up the page and that communication failed. It looks like it’s intermittent which is why other times it loads fine.

Hi Dylan

From my main router the server and all end points are Ethernet connected and I didn’t see any other issues if I played non radio content.

I’m not sure if this applies to everyone Roon seems to display the error page until the station page loads. Today this is only visible for a millisecond or two.

I suspect this is the default and a timing issue exists where if the station is not connected to the default error page is displayed.

It seems OK today and will monitor and switch over my core to the house main desktop and see if I can replicate the issue.

Cheers Phil

I had this behaviour during the week-end, now can’t reproduce. Roon backend struggling with the extra number of connexions in the week-end?

Rather than create a fresh thread, I thought I’d chime in on this one. I mostly listen to some of the excellent FIP stations from Paris and a few from BBC (Radio 4, 6 and World Service).

The FIP stations seem to play perfectly with rarely a problem, but the BBC stations seem to bomb out frequently and randomly. Sometimes I can listen for 20-30 minutes without interruption, sometimes I can’t even get a couple of minutes before they stop. I can re-start them without a problem but then I can only listen for a short while (sometimes a minute or less) before it stops again.

Edit: additional.

Initially I wondered if it was a WiFi issue, but as I said, I have no such problems with FIP. Plus I have tried listening to the BBC stations on outputs with a wired connection and the same problem persists.

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