Audio file loading slowly since Devialet RAAT

Thank you @John! I think what I struggled with most on this is trying to figure out what I could do to circumvent the problem since many others were not experiencing it. It’s good to see the Devialet problem acknowledged and looking forward to hearing the response from them on this (whenever that may be).

I get the same message ‘slow…” with wifi, wifi router is 1m away and signal is very strong and speed is high (ac pro hd wifi). It may not happen as often as with an ethernet connection, but it happens.

I just made the same additional tests as per my previous posts, also direct cable connection, but this time using another network card (3rd one - an USB card): LINKSYS USB3GIG.
I tested multiple scenarios:

  • Using network card with USB 2 port, and with USB 3. On both USB 2+3, the network connection speed is set to 1000 Mbps. This is the “technical” connection speed.
  • Using auto negotiated speed 1000 Mbps, manual speeds 1000 Mbps, 100 Mbps and 10 Mbps.
    The bug is occurring on USB 3, but it is not occurring on USB 2. On USB 2 everything works fine: no “Audio file loading slowly” error, and no network traffic fluctuations. This is for RAAT protocol. AIR protocol is working fine in any circumstances, configurations and settings.
    Even “technical” connection speed is 1000 Mbps for both USB 2+3, USB 2 is limiting the “actual” connection speed (data traffic) to less than 1000 Mbps. This is the only network card that allows me to test different actual connection speeds over the same “technical” connection speed.

As per my limited networking knowledge, and results of all tests that I performed, my deduction is that RAAT protocol over Ethernet is generating communication errors (and package resend). This is happening at any network connection speed (including 10 + 100 + 1000 Mbps). Still, this has a user perceivable effect only when large amount of data is involved (e.g. 192kHz audio files).

Yes, I get the same error message “an audio file is loading slowly” regardless of ethernet or WiFi connection. Otherwise, WiFi works without problems.

By the way - Spotify connect is working without any problems by ethernet oder wifi. I am using Spotify now, I am tired about the ROON/RAAT (Tidal) problems. Any ROON/RAAT problems are worse than the Spotify sound quality difference.

I can’t imagine why this would be. Anything applicable here: Networking Best Practices ?

Hello everyone, I’m rather new on this forum.

I’ve got the same issue with Devialet and RAAT. My Devialet loses all connection when it its fed by Roon. Before we used Orange (provider) that maximize the speed only at 100 mbps. We now have a faster provider that goes on 240 mbps.

All problems started when fastened the internet and Devialet crashes. The only way to get it back activate is to unplug the device from the powers.

We have formation products from B&W and they work perfect with Roon!

Devialet is a lovely device with lovely sound but they have a CRAP customer service when you have issues with the device.

I hope they address this problem asap and work on a solution.

Jan, the issue with Devialet Expert and Roon RAAT via Ethernet is well documented, though you may be unaware of it. The ball is in Devialet’s court and perhaps when their people return from the August holidays we might see some progress. But, as you point out, the company’s customer service leaves something to be desired.

Now I have switched to a new router and a 1000 Mbit cable internet connection. First try Devialet by WLAN: Track loading slowly…

You can force that message, when skipping fast between the tracks.

So definitely not only an 1 GB Ethernet problem.

Exactly the same problem I have, as long as music just runs, one song at a time I rarely have problems, as soon as I skip 4-5 tracks this error occurs. Most of the time I have to restart Roon ROCK for it to work again.

Same problem for me, indeed especially when skipping songs rapidly. Restarting Roon-server solves the problem. Switched back to AIR-ETH for now.

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