Hi
I noticed this in the last few days after listening happily for months. NOthing changed my end that i know of. Troubleshooted(? Shot?) with the help of ChatGPT (pfft) - description below. I lisetn to this station a lot so any help would be great.
Thanks
Simon
RRR Melbourne live radio consistently drops out in Roon 2.71 build 1683
I’m having a reproducible problem playing Triple R Melbourne (3RRR) live radio through Roon.
Roon Server: 2.71 (build 1683), production
Server: Late-2012 Mac mini, Ubuntu Server 24.04, Ethernet
Endpoint: Primare NP5 Prisma, Ethernet
Also tested: Roon System Output on a Macbook pro
RRR streams tested
All three RRR streams fail:
-
https://realtime.rrr.org.au/p1h— AAC, 128 kbps -
http://realtime.rrr.org.au/p13— MP3, 128 kbps -
https://realtime.rrr.org.au/p1l— AAC, 32 kbps
The failure occurs with both the NP5 and Roon System Output.
The stream normally starts and plays for approximately 20–30 seconds, then the endpoint reports repeated dropouts and Roon kills the stream.
Control tests
Other Internet radio streams work perfectly through the same Roon Server and NP5:
-
PBS FM HLS AAC — stable for 12+ minutes
-
SomaFM continuous ICY MP3/AAC — stable
-
3CR Melbourne continuous MP3 — stable
This therefore does not appear to be a general AAC/MP3, HLS/ICY, NP5, network, or bandwidth problem.
I also tested the RRR p13 stream directly from the Roon server using curl. The TCP connection remained open and continuously received data for approximately 10 minutes without an EOF, reset, or transport error.
Relevant Roon log
For RRR p13, the Roon log shows successful connection and ICY metadata reception:
Got ICY Stream Title [Local and/or General with Hal Langley]
Playback then starts normally. Approximately 20–25 seconds later:
[System Output] [raatclient] GOT [84] {"samples":13929,"status":"Dropout"}
[System Output] [raatclient] GOT [84] {"samples":22050,"status":"Dropout"}
[System Output] [raatclient] GOT [84] {"samples":22050,"status":"Dropout"}
[System Output] [raatclient] GOT [84] {"samples":22050,"status":"Dropout"}
[System Output] [raatclient] GOT [84] {"samples":22050,"status":"Dropout"}
[zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
[zone Loki] Track Stopped Due to Slow Media
[streammediafile] error reading stream:
Unable to read data from the transport connection:
Software caused connection abort.
Immediately afterwards Roon also reports:
[zoneplayer/raat] Error during streaming:
System.NullReferenceException:
Object reference not set to an instance of an object.
at Roon.Broker.Transport.RaatZonePlayer...
The Software caused connection abort appears to occur after Roon has already decided to kill the stream, so I don’t think this necessarily indicates that the RRR server closed the connection.
Question
Could this be an incompatibility/regression in Roon’s handling of RRR’s current Icecast/ICY streams?
The fact that all three RRR streams fail, while other continuous ICY streams such as SomaFM and 3CR work reliably, makes RRR’s particular stream implementation seem significant.
I’m happy to provide the full Roon diagnostics/logs if useful.