Does anyone know what "Unable to read data from the transport connection" means?

Hi,

I’ve been suffering with dropouts for some time now. I’ve made lots of improvements to the system and its getting better. Dropouts occur a few seconds after a track change when listening to either internet radio or Qobus.

Now whenever it drops out there is a report like this in the RoonServer_log

11/05 17:31:28 Trace: [Adrian's Office] [LowQuality, 24/44 AAC => 24/44] [100% buf] [PLAYING @ 18:39] These Dreams - Heart
11/05 17:31:28 Trace: [Lounge NUC Douk] [LowQuality, 24/44 AAC => 24/44] [100% buf] [PLAYING @ 18:39] These Dreams - Heart
11/05 17:31:30 Trace: [Kitchen + Adrian's Office + Lounge NUC Douk] [zoneplayer/raat] sync XMOS USB Audio 2.0 ST 3004 -> Built-in Output result: Success
11/05 17:31:30 Trace: [Kitchen + Adrian's Office + Lounge NUC Douk] [zoneplayer/raat] sync Built-in Digital Output -> Built-in Output result: Success
11/05 17:31:32 Trace: [zone Kitchen + Built-in Digital Output + Lounge NUC Douk] PlayPause
11/05 17:31:32 Info: [zone Kitchen + Built-in Digital Output + Lounge NUC Douk] OnPlayFeedback Stopped
11/05 17:31:32 Info: [zone Kitchen + Built-in Digital Output + Lounge NUC Douk] Canceling Pending Sleep
11/05 17:31:32 Info: [zone Kitchen + Built-in Digital Output + Lounge NUC Douk] Canceling Pending Sleep
11/05 17:31:32 Trace: [Kitchen + Adrian's Office + Lounge NUC Douk] [zoneplayer/raat] Endpoint Built-in Output State Changed: Playing => Prepared
11/05 17:31:32 Trace: [Built-in Output] [raatclient] SENT [8974]{"request":"end_stream"}
11/05 17:31:32 Info: [audio/env] [zoneplayer -> stream] All streams were disposed
11/05 17:31:32 Info: [audio/env] [zoneplayer -> stream -> endpoint] All streams were disposed
11/05 17:31:32 Info: [audio/env] [zoneplayer -> stream -> endpoint] All streams were disposed
11/05 17:31:32 Info: [audio/env] [zoneplayer -> stream -> endpoint] All streams were disposed
11/05 17:31:32 Trace: [Kitchen] [LowQuality, 24/44 AAC => 24/44] [100% buf] [STOPPED @ 0:00] These Dreams - Heart
11/05 17:31:32 Trace: [Adrian's Office] [LowQuality, 24/44 AAC => 24/44] [100% buf] [STOPPED @ 0:00] These Dreams - Heart
11/05 17:31:32 Trace: [Lounge NUC Douk] [LowQuality, 24/44 AAC => 24/44] [100% buf] [STOPPED @ 0:00] These Dreams - Heart
11/05 17:31:32 Warn: [streammediafile] error reading stream: Unable to read data from the transport connection: Software caused connection abort.
11/05 17:31:32 Trace: [Built-in Output] [raatclient] GOT [8972] {"status":"Ended"}
11/05 17:31:32 Info: [audio/env] [zoneplayer] All streams were disposed
11/05 17:31:32 Trace: [Built-in Out

The problem seems to be “Unable to read data from the transport connection” and the system’s response is “Software caused connection abort”

But what exactly is “the transport connection”?

Thanks for any help with this
Adrian

Roon uses the so-called RAAT server to transport all data. This transport software is like Airplay, Bluetooth or other transports.

RAAT is specialized in very much transmission information and very high quality audio. This is not possible with Bluetooth or Airplay.

The Roon server works hand in hand with RAAT, the Roon.exe and/or the Roon appliance.

If everything is set up correctly, there should be no more transport losses.

Let me show my system log where they all work.

If I read it correctly, it was set to run 3 zones simultaneously?

That would be a higher requirement than just running the kitchen or another room.

Should run the same everywhere, do I see it right, or can the desired setting be improved here?

just found:

Hi Uwe,
Yes the system is running a group of 3 endpoints; kitchen, lounge and office.
So is my Core underpowered?
My Core at present is ROCK running on an Intel NUC D54250WYKH. My understanding is that this an i5 processor with about 2/3rds of the capability of the present Roon Nucleus.

I think it runs OK with just 2 endpoints.

The grouping of many zones is probably actually originator here. Have you already tested without grouping or only two zones?

Ok, I’ve tested it with a single endpoint and 2 endpoints. In both cases the system ran for 24+ hours without falling over.
When I tried a 3rd endpoint in the group then I started getting dropouts again.
At first I was using a 2009 Mac Mini for the 3rd endpoint. It always seemed to be that mac mini’s particular IP address that was causing the problems, so I changed it for an Intel NUC D54250WYK. This should be about 2x more capable.
Now the dropouts seem to be related to the message “Unable to read data from the transport connection”.
If the “transport connection” is part of the Roon Core, then it looks like the Core is not good enough. In my case the Core is ROCK running on a different D54250WYKH. Looks like I will have to find a better NUC!

1 Like

I think that the transport connection is your network and it might be that it is your network (topology, bandwidth, …) that is not good enough to run 3 or more concurrent audio streams to your grouped devices. Sure, the Core might also be not good enough. Looks like you need to do more testing to figure this out before you start spending money on solutions that probably won’t solve your issue.

1 Like

Hi BlackJack,
The Roon devices are all hard wired direct to a 1GB bandwidth network via a Netgear GS234 Gigabit Switch or into the BT Home Hub 2 connected to it that provides the broadband connection. No WiFi anywhere.

I’ve just transferred the Roon Core from the Intel NUC D54250 to the most powerful machine in the house; a 2019 iMac with a 3Ghz 6-core Intel i5 processor and 40gb of RAM. It is presently serving the same group of 3 endpoints with my favourite internet radio station (Planet Rock) and has been running Ok for 1hr 28 mins.

I’ll see what happens overnight

1 Like

Ok, further update.
After I transferred the Roon Core to the 2019 iMac, the system happily ran internet radio with 3 endpoints for over 24 hours. The endpoints were an Intel NUC DW54250, a 2013 Mac Pro and a mid 2011 mac mini 2.3GHz dual core i5.
I tried reverting the Intel NUC DW54250 back to the 2009 mac mini. The system fell over quite quickly. I put the Intel NUC DW54250 back in instead of the 2009 mac mini and the system ran smoothly again.
So I’ve tried increasing the loading by adding the built in output on the 2019 iMac into the group. So now running with 4 endpoints. At the time of this post the system has been running internet radio happily with no dropouts for 14hrs.

Conclusion; I had 2 bits of kit that were not capable for the system I was running. 1) The Intel NUC DW54250 running the ROCK Core is not capable of supporting more than 2 endpoints in a group.
2) The 2009 mac mini is just not capable of being a reliable endpoint.

Just for reference the whole system is hardwired with CAT5e cable. There are 3 hubs/switches involved; the 2013 mac Pro is wired to my BT Home Hub 2 router. That is hard wired to a Netgear GS234 Gigabit Switch. The Intel NUC DW54250 endpoint is hard wired into the GS234 switch. The 2011 mac mini is hardwired to the GS234 through an Apple Time Capsule (effectively just an AirportExtreme with a hard disk built in). The 2019 iMac running the Roon Core is also hardwired into the GS234.

2 Likes