RAAT Broken on Rasperry Pi? [Resolved turning off jumbo frames]

Hi, I’ve used two different images including the rather large image from HiFi Berry and such. I can strem to my computer and I can stream to the Raspberry Pi, However, I can only stream to the Raspberry Pi if I enable a protocol other than RAAT such as Apple’s AirPlay.

This all happened since the latest software update to Roon. Working one minute, next minute RAAT no longer working.

Does anyone else have this problem? I’ve been lazy hoping someone else would find it, but it’s been a few weeks now.

I should mention, the Error’s I get are seemingly unrelated, such as ‘There’s a networking Error with Tidal’, an audio file is loading slowly, this may indicate a networking or performance problem. But of course, if I switch away from RAAT it works.

Thanks.

Running a total of four Pi as roon bridges, no problem streaming to any of these via raat.

Thanks, that’s good to know. Just to confirm, you’re running the latest version of Roon on server etc?

My server is on Linux, out of interest what’s your server platform?

Thanks.

I too run several different pi distro’s (dietpi, iqaudio, ropieee, volumio) and all having no issues with roon bridge…some using DAC/amp hats and others just USB DAC’s

All are LAN wired connections for the record and all RAAT but some also using airplay outside of roon

All Linux (For the most part) in my network. I own several Pi’s and using RAAT with no issues at all around my network.
Here is a full detail post of my setup:

Hope this helps.

Thanks. I guess it’s all pointing at my setup then.

Very odd.

I guess you can uninstall roon bridge and reinstall on the pi’s

Have done that. Airplay works on it. Re-imaged the whole card with HiFiBerry image, same result, except that doesn’t have airplay of course (and slow to boot).

It’s also detected by Roon server in all instances. Since AirPlay works it’s not likely to be network related, it doesn’t stutter or anything, just play’s to the 1 second point, no sound comes out, then fails.

Am thinking I try re-installing the server. Just trying to hunt down the logs in case they give clues.

Thanks everyone.

Found them at /var/roon/RoonServer/Logs

Well there’s lots of:

05/07 15:54:13 Warn: Error in web request https://push.roonlabs.com/push/1/connect: NetworkError (The remote server returned an error: (502) Bad Gateway.)
05/07 15:54:13 Trace: [push] request to manager failed
05/07 15:54:13 Trace: [push] retrying connection in 2245590ms

And

05/07 16:02:32 Trace: [zone] [Lounge] Playing 1 Items
05/07 16:02:32 Trace: [zone] [Lounge] Selecting Source
05/07 16:02:32 Trace: [zone] [Lounge] Playing TransportItem
05/07 16:02:32 Trace: [musicpowerstate] music is playing, preventing idle sleep
05/07 16:02:33 Trace: [tidal/http] GET https://api.tidalhifi.com/v1/tracks/10904956/streamurl?countryCode=NZ&sessionId=c7b9fef8-66aa-4e8e-b73f-7134ff40ea3c&soundQuality=LOSSLESS => Success
05/07 16:02:33 Trace: [tidal/http] GET https://api.tidalhifi.com/v1/tracks/10904956?countryCode=NZ&sessionId=c7b9fef8-66aa-4e8e-b73f-7134ff40ea3c& => Success
05/07 16:02:33 Info: [zoneplayer/base] Playing: http://64.audio-pop.tidal.com/d283043ef0425e9ed9bdd0e9555a89b0_26.flac
05/07 16:02:38 Info: [zoneplayer/base] Open Result (Playing):Result[Status=Success]
05/07 16:02:38 Info: [zoneplayer/base] Starting playback
05/07 16:02:38 Debug: Get SRC plan for StreamParams[SampleRate=44100, BitsPerSample=16, Channels=2, Layout=CH_2_0 FrameCount=11393676]
05/07 16:02:38 Debug: => SRCPlan[
original format: StreamParams[SampleRate=44100, BitsPerSample=16, Channels=2, Layout=CH_2_0 FrameCount=11393676]
initial src format: StreamParams[SampleRate=44100, BitsPerSample=16, Channels=2, Layout=CH_2_0 FrameCount=11393676]
src filter type: minimum_phase
is compatibility: False
dsd processing ok: False
]
05/07 16:02:38 Trace: [zoneplayer/raat] StartStream 1323832455: Sooloos.Broker.Transport.RaatZonePlayer+Endpoint => StreamParams[SampleRate=44100, BitsPerSample=16, Channels=2, Layout=CH_2_0 FrameCount=11393676] streamid=StreamParams[SampleRate=44100, BitsPerSample=16, Channels=2, Layout=CH_2_0 FrameCount=11393676]
05/07 16:02:38 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] SENT [6]{“request”:“setup”,“format”:{“sample_type”:“pcm”,“sample_rate”:44100,“bits_per_sample”:16,“channels”:2}}
05/07 16:02:38 Debug: Lastfm ‘44a2900a5c450538ccacc2b34e2ac31c’ START: Hootie & the Blowfish - I Will Wait
05/07 16:02:38 Trace: [prebuffer] ready 149940/441000 (34%) @ 0/258 sec
05/07 16:02:38 Trace: [streamingmediafile] immediate read of http://64.audio-pop.tidal.com/d283043ef0425e9ed9bdd0e9555a89b0_26.flac at 524288 length=33058022
05/07 16:02:38 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [6] {“message”:{“signal_path”:[{“method”:“analog”,“type”:“output”,“quality”:“lossless”}]},“status”:“OutputMessage”}
05/07 16:02:38 Info:
–[ SignalPath ]---------------------------------------------
SignalPath Quality = Lossless
Elements:
Source Format=Flac 44100/16/2 Quality=Lossless
Raat Device=HiFiBerry DAC+
Output OutputType=Local_Analog Quality=Lossless

05/07 16:02:38 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [6] {“clock_port”:56279,“audio_port”:33657,“status”:“Success”}
05/07 16:02:38 Trace: [zoneplayer/raat] Endpoint HiFiBerry DAC+ State Changed: Idle => Prepared
05/07 16:02:38 Trace: [zoneplayer/raat] synced to endpoint clock. realtime=23314259388609 rtt=369us offset=22436269571us delta=22436269571us
05/07 16:02:38 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] SENT [7]{“request”:“stream”,“stream_id”:1323832455,“first_seq”:0,“nak_port”:56634,“buffer_size”:2.5}
05/07 16:02:38 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [7] {“status”:“Buffering”}
05/07 16:02:38 Trace: [zoneplayer/raat] Endpoint HiFiBerry DAC+ State Changed: Prepared => Buffering
05/07 16:02:38 Trace: [raat/audiosource] setting stream bitrate to 1411200 (2469600 with headroom)
05/07 16:02:38 Trace: [zoneplayer/raat] [zoneplayer/raat] selected HiFiBerry DAC+ as clock master
05/07 16:02:38 Trace: [prebuffer] status 220500/441000 (50%) @ 0/258 sec
05/07 16:02:41 Info: [stats] 4864mb Virtual, 754mb Physical, 435mb Managed, 0 Handles, 45 Threads
05/07 16:02:48 Warn: [zoneplayer/raat] Endpoint failed to become ready in 10s. Proceeding in state Buffering
05/07 16:02:48 Trace: [zoneplayer/raat] Endpoint HiFiBerry DAC+ State Changed: Buffering => Ready
05/07 16:02:48 Trace: [zoneplayer/raat] wait for ready in 9999ms
05/07 16:02:48 Trace: [zoneplayer/raat] Adjusting playback start offset from 50ms to 59ms
05/07 16:02:48 Trace: [zoneplayer/raat] Starting at streamsample 0 and time 23324505997609 min_offset=59ms offset=59ms
05/07 16:02:48 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] SENT [8]{“request”:“start”,“time”:23324545723148,“stream_sample”:0}
05/07 16:02:48 Trace: [zoneplayer/raat] Endpoint HiFiBerry DAC+ State Changed: Ready => Playing
05/07 16:02:48 Trace: [prebuffer] status 441000/441000 (100%) @ 2/258 sec
05/07 16:02:49 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [7] {“status”:“Playing”}
05/07 16:02:49 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [8] {“status”:“Success”}
05/07 16:02:49 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [7] {“samples”:12348,“status”:“Dropout”}
05/07 16:02:49 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [7] {“samples”:22050,“status”:“Dropout”}
05/07 16:02:50 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [7] {“samples”:22050,“status”:“Dropout”}
05/07 16:02:50 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [7] {“samples”:22050,“status”:“Dropout”}
05/07 16:02:51 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [7] {“samples”:22050,“status”:“Dropout”}
05/07 16:02:51 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [7] {“samples”:22050,“status”:“Dropout”}
05/07 16:02:52 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [7] {“samples”:22050,“status”:“Dropout”}
05/07 16:02:52 Warn: [zoneplayer/raat] Too many dropouts (>3s dropped out in the last 30s). Killing stream
05/07 16:02:52 Trace: [zoneplayer/raat] too many dropouts. stopping stream
05/07 16:02:52 Info: [audio/env] [zoneplayer -> stream] All streams were disposed
05/07 16:02:52 Trace: [zoneplayer/raat] Endpoint HiFiBerry DAC+ State Changed: Playing => Prepared
05/07 16:02:52 Info: [audio/env] [zoneplayer -> stream -> endpoint] All streams were disposed
05/07 16:02:52 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] SENT [9]{“request”:“end_stream”}
05/07 16:02:52 Warn: Track Stopped Due to Slow Media
05/07 16:02:52 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [7] {“status”:“Ended”}
05/07 16:02:52 Trace: [transport/raatclient] [HiFiBerry DAC+ @ 192.168.43.30:45063] GOT [9] {“status”:“Success”}
05/07 16:02:56 Info: [stats] 4837mb Virtual, 729mb Physical, 360mb Managed, 0 Handles, 48 Threads
05/07 16:02:57 Trace: [zone] no playback for 5s, suspending to release audio device
05/07 16:02:57 Trace: [zone] [Lounge] Suspend
05/07 16:02:57 Trace: [zone] [Lounge] Stop
05/07 16:03:11 Info: [stats] 4848mb Virtual, 740mb Physical, 370mb Managed, 0 Handles, 41 Threads
05/07 16:03:26 Info: [stats] 4848mb Virtual, 739mb Physical, 370mb Managed, 0 Handles, 41 Threads
05/07 16:03:41 Info: [stats] 4848mb Virtual, 739mb Physical, 370mb Managed, 0 Handles, 41 Threads
05/07 16:03:56 Info: [stats] 4848mb Virtual, 739mb Physical, 370mb Managed, 0 Handles, 41 Threads

@support I think someone might be able to say what’s going on in the logs or get you to send the full logs to them

Moved this to the support threads too @marshalleq

I found the problem. Raat on the the Raspberry Pi didn’t like that the server was set to use Jumbo Frames. I set them using DHCP and when the Roon update applied the Raspberry Pi rebooted. Quite possibly I rebooted the server some time after, though I can’t say for sure at this stage which end did what when as it was weeks ago. However, I suspect it was only the Pi that hadn’t been rebooted and checked, I’m liable to forget such a tiny computer!

Jumbo frames has tripped up so many it should be a red flag in the installation notes