BBC R3 stream dropping - sanity check please

Sanity check please, before I disappear into the weeds trying to work out what - if anything - I can do about it…

I often have the BBC R3 320kbs stream running while I’m doing something else. A few times over the years it’s just stopped, but I can manually restart it. No great problem. Over the last few days, it’s dropped more frequently - maybe three times over a couple of hours. Hmm. Maybe it is a problem…

A quick look at the logs suggest the stream is being interrupted on the ‘internet’ side, rather than anything local, but (to me) doesn’t tell where/why.

Is anyone else experiencing a similar issue, possibly with any of the BBC streams?

Chain is Virgin fttp 250mbs to Virgin Hub 3 (modem mode) to MikroTik hAPax3 to NUC/W10pro/Roonserver (wired) to Naim ND5XS2 (wireless). No issues with continuous stream from Tidal. Cloudflare diagnostics suggest connection is all good.

1 Like

Still doing it…

The log entries are like this -

10/14 21:26:54 Warn: [easyhttp] [8933] GET https://as-hls-uk-live.akamaized.net/pool_904/live/uk/bbc_radio_three/bbc_radio_three.isml/bbc_radio_three-audio%3d320000.norewind.m3u8 web exception without response: socketmsg (SocketError):  The SSL connection could not be established, see inner exception. The SSL connection could not be established, see inner exception.

Upstream congestion on the Virgin network?

1 Like

Playing continuously for the last 12 hours… :roll_eyes:

1 Like

Yes, similar issues here with R4 and 6 Music for last few weeks. Also note that the Naim streams for these stations have new logos, so wondering if there changes BBC side that need reflecting. :thinking:

1 Like

I think the Naim issues were all related to problems with vtuner - which I understand are now resolved by Naim hosting their own ‘radio’ aggregator - so are probably unrelated… but that doesn’t mean Auntie hasn’t coincidently changed something!

I need to widen the scope of testing to see if a pattern emerges; non-bbc radio and non-Naim endpoint for starters - time consuming though!

Still dropping - occasionally

Tried to provoke it this morning. R3 and R6M to two different endpoints, two 192/24 streams from Tidal to another two. All endpoints wifi. Lots of traffic, no apparent stress on Nuc or router. No drops…

@BrianW - is there anything about the BBC streams that would make them more likely to drop than (say) Radio Paradise?

Hi. If only to provide a bit more evidence…had similar problems with BBC 6 music and BBC R4 at the weekend- wouldn’t start the stream at all on Saturday morning…embarrassing because my better half is not a fan of using Roon and gives her a “told you so” moment as to why I should return to my old Pure tuner which I mothballed the day I signed bought my first Roon ready device

1 Like

The BBC streams are quite different - chunked .ts streams instead of a straightforward flac or aac.
However, that shouldn’t (!) cause drops after some hours.

I would have thought many more users would have complained by now, so suspect (possibly) something with your setup.

Probably worth posting in Support so the Devs can see your logs.

Thanks Brian.

It seems there are a few people eperiencing something similar, but my feel is it’s inconsistent and occasional. If it hadn’t dropped two or three times in as many minutes a few weeks ago, I wouldn’t even be looking.

My internet connection is plenty fast, but the VM Hub 3 is a DOCSIS modem, which is apparently not brilliant for latency. It’s possible it’s an SSL timeout, but the error message (same one every time) doesn’t tell whether it’s Roon being impatient, or the BBC servers giving up. I have a set of logs from the frequent-drop period - I’ll post something in support.

1 Like

Posted. Unconvincing response…

For the benefit of anyone seeing similar issues…

My workaround has been to turn Cloudflare off, and revert to the ISP DNS servers provided via the MikroTik router. It’s a compromise - no stream drops, but the Roon UI is notably slower. It’s also contrary to the usual Roon best practice to use Cloudflare/Google/whatever DNS in preference to the ISP service.

The support thread has been closed, despite no-one having actually worked out why Cloudflare DNS was (apparently) an issue. Not a priority I guess. Oh well.

It was an automatic closure by the system. I’ve opened it again.

Thanks. I hadn’t noticed it had been marked solved, so was surprised when it was automatically closed. I think it would be good to understand the failure mechanism; but the impact does seem pretty limited!