Occasional dropouts: Roon to Devialet Air

Core Machine (Operating system/System info/Roon build number)
SonicTransporter with Roon Server
Roon Server 1.7 b667 64 bits
Devialet 400

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Everything connected through Ethernet. In between SonicTransporter and Devialet there is a Netgear S8000 switch

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Devialet 400, Ethernet. Devialet Air protocol

Description Of Issue
I get occasional dropouts. This is an excerpt of the Roon log where I can see reported NAK´s from the Devialet:

11/01 12:43:42 Debug: [easyhttp] [1359] POST to https://metadata.roonlabs.net/1/albums/translate?c=tidal-mx returned after 350 ms, status code: 200 
11/01 12:43:42 Debug: [easyhttp] [1361] POST to https://metadata.roonlabs.net/1/albums/translate?c=tidal-mx returned after 263 ms, status code: 200 
11/01 12:43:42 Debug: [easyhttp] [1362] POST to https://metadata.roonlabs.net/1/works/translate?c=tidal-mx returned after 365 ms, status code: 200 
11/01 12:43:42 Debug: [devialet] NAK[34] 
11/01 12:43:42 Info: [library/albumdetails] found 6 streaming service alternates 
11/01 12:43:42 Info: [library/albumdetails] found 6 streaming service alternates 
11/01 12:43:42 Debug: [devialet] NAK[29] 
11/01 12:43:42 Debug: [devialet] NAK[25] 
11/01 12:43:43 Debug: [devialet] NAK[20] 
11/01 12:43:43 Debug: [easyhttp] [1363] GET to https://discover.roonlabs.net/1/albums/121:0:MW0000312167/recommended/albums?profileId=44dff8dd-7643-4a32-b700-e1e01e4dea12&count=30&c=tidal-mx returned after 573 ms, status code: 200 
11/01 12:43:43 Debug: [devialet] NAK[15] 
11/01 12:43:43 Debug: [devialet] NAK[10] 
11/01 12:43:43 Debug: [devialet] NAK[5] 
11/01 12:43:44 Debug: [devialet] NAK[41] 
11/01 12:43:44 Debug: [devialet] NAK[37] 
11/01 12:43:44 Debug: [devialet] NAK[32] 
11/01 12:43:44 Debug: [devialet] NAK[27] 
11/01 12:43:44 Debug: [devialet] NAK[22] 
11/01 12:43:44 Debug: [devialet] NAK[17] 
11/01 12:43:44 Debug: [devialet] NAK[12] 
11/01 12:43:44 Debug: [devialet] NAK[8] 
11/01 12:43:44 Debug: [devialet] NAK[3] 
11/01 12:43:45 Trace: [Devialet] [Lossless, 24/192 FLAC => 24/192] [100% buf] [PLAYING @ 0:27/2:16] She's Goin' Bald [Stereo] - The Beach Boys 
11/01 12:43:47 Info: [stats] 5023mb Virtual, 2315mb Physical, 995mb Managed, 0 Handles, 81 Threads 
11/01 12:43:50 Trace: [devialet/audiosource] Sent 500000 packets, qdepth=7 
11/01 12:43:50 Trace: [Devialet] [Lossless, 24/192 FLAC => 24/192] [100% buf] [PLAYING @ 0:32/2:16] She's Goin' Bald [Stereo] - The Beach Boys 
11/01 12:43:52 Debug: [devialet] NAK[40] 
11/01 12:43:52 Debug: [devialet] NAK[35] 
11/01 12:43:52 Debug: [devialet] NAK[30] 
11/01 12:43:52 Debug: [devialet] NAK[26] 
11/01 12:43:52 Debug: [devialet] NAK[21] 
11/01 12:43:52 Debug: [devialet] NAK[16] 
11/01 12:43:52 Debug: [devialet] NAK[11] 
11/01 12:43:52 Debug: [devialet] NAK[6] 
11/01 12:43:52 Debug: [devialet] NAK[1] 
11/01 12:43:55 Trace: [Devialet] [Lossless, 24/192 FLAC => 24/192] [100% buf] [PLAYING @ 0:37/2:16] She's Goin' Bald [Stereo] - The Beach Boys 
11/01 12:43:58 Debug: [devialet] NAK[33] 
11/01 12:43:58 Debug: [devialet] NAK[28] 
11/01 12:43:58 Debug: [devialet] NAK[24] 
11/01 12:43:58 Debug: [devialet] NAK[19] 
11/01 12:43:58 Debug: [devialet] NAK[14] 
11/01 12:43:58 Debug: [devialet] NAK[9] 
11/01 12:43:58 Debug: [devialet] NAK[4] 
11/01 12:44:00 Trace: [devialet/audiosource] Sent 510000 packets, qdepth=2 
11/01 12:44:01 Trace: [Devialet] [Lossless, 24/192 FLAC => 24/192] [100% buf] [PLAYING @ 0:42/2:16] She's Goin' Bald [Stereo] - The Beach Boys 
11/01 12:44:02 Info: [stats] 5023mb Virtual, 2315mb Physical, 997mb Managed, 0 Handles, 81 Threads 
11/01 12:44:04 Trace: [rnet/RnetJsonClient] no data received for >10000ms. Killing connection. 
11/01 12:44:04 Trace: [raatserver] [RaatServer gustavogs-iPhone @] lost client connection. Retrying 
11/01 12:44:04 Warn: [rnet/RnetJsonClient] error writing to connection 
11/01 12:44:04 Trace: [raatserver] [RaatServer gustavogs-iPhone @] connecting (attempt 1) 
11/01 12:44:04 Trace: [raatserver] [RaatServer gustavogs-iPhone @] connected 
11/01 12:44:04 Trace: [rnet/RnetJsonClient] SENT {"request":"enumerate_devices","subscription_id":"0"} 
11/01 12:44:06 Trace: [Devialet] [Lossless, 24/192 FLAC => 24/192] [100% buf] [PLAYING @ 0:47/2:16] She's Goin' Bald [Stereo] - The Beach Boys 
11/01 12:44:06 Debug: [devialet] NAK[34] 
11/01 12:44:06 Debug: [devialet] NAK[29] 
11/01 12:44:06 Debug: [devialet] NAK[24] 
11/01 12:44:06 Debug: [devialet] NAK[19] 
11/01 12:44:06 Debug: [devialet] NAK[14] 
11/01 12:44:06 Debug: [devialet] NAK[9] 
11/01 12:44:07 Debug: [devialet] NAK[4] 
11/01 12:44:10 Trace: [devialet/audiosource] Sent 520000 packets, qdepth=7 
11/01 12:44:11 Trace: [Devialet] [Lossless, 24/192 FLAC => 24/192] [100% buf] [PLAYING @ 0:52/2:16] She's Goin' Bald [Stereo] - The Beach Boys 

What is happening here? Is there a way this can be prevented/fixed?


How many dropouts per say per 1hr, I stream Qobuz & Tidal all day long and do not get any dropouts that I can recall, of course I do have an issue every once in a while, but I doubt more than a couple per week. I’ve got the S8000 too and feel my system likes it, I use mostly RAAT over Ethernet.

one interesting item, is I demoed an etherRegen, which downlevels the connection and is supposed to resolve this issue, but in my system I did not like the sound so I went back to my gigabit connections.

Sometimes days with no dropouts. Today, 2-3 an hour. I don´t feel it is the Ethernet connection but …

The cable runs between the SonicTransporter, Netgear S8000 switch and Devialet Expert are short and I am using good CAT 7 cable.

I’ve got a netgear x10 r9000 with my s8000 used to add extra ports, I’ve tried running my NUC and Dev 200 off both, but never experenced any issues no matter which I hooked upto. I’m current,y hooked directly to the x10, using good ole crappy cables, one of these days I’m hoping for an upgrade.

Hi @Gustavo_Gabaldon,

NAK error messages typically mean that there is data not being received by the Devialet, most commonly due to network conditions. The first thing that I notice is that the Netgear switch seems to have managed switch functionality, which we’ve seen interfere with Roon’s communication with devices in the past.

As a starting point, I’d be curious to know if the same behavior occurs when both the Core and Devialet are connected to the router directly, or an unmanaged switch. Does the same issue occur?

What would you consider “managed”. With that switch I have QoS and port prioritization turned on (for the SonicTransporter and Devialet ports). Should I remove those additional configuration setups?

Unfortunately, the audio rack is a bit far from the router. There is a CAT7 run to the audio rack, gets to the switch and from there to the ST, Devialet, and PS Audio Power Plant. When those dropouts occur I power everything down and up and it does not occur for days. Maybe I should cycle power on one device at a time and see what happens.

Hi @Gustavo_Gabaldon,

Managed switches are any type of switch that has a GUI and can be configured through the GUI. We’ve found that often times, managed switches don’t have quite the right settings to work well with Roon from out-of-the-box.

We have a few suggestions regarding managed switches in our Networking Best Practices Guide but the easiest test here would be to replace the managed switch for an unmanaged one and see if the issues go away, then we have pinpointed the cause as the managed switch.

Managed Switches

Managed switches can be very robust, but they are often designed for professional installation, so in many cases the out-of-box configuration is not right. If your switch has a “flow control” setting, please make sure that it is enabled. Also, make sure that the switch is not performing any sort of throttling that might impact communication between cores, storage, remotes, and/or audio endpoints. Finally, ensure that the switch is configured to pass multicast and broadcast traffic. If in doubt about any of this, try temporarily replacing your managed switch with a “dumb” switch to see if things improve.

I’ve got an S8000, all features turned off, just let the data flow, no issues here, but I’m currently tied off the main router, not the attached switch.

My understanding of the managed part of the S8000 is it’s a Gaming switch, with the idea you give top priority to your gaming connection and then slow the other ports down to leave all the bandwidth for your game, so you could treat your music connections like a game, give them full bandwidth and slow the others down.

Also did or have you tried connecting directly to the main router, and by the way what is your main router?

One other thought is some backups or other heavy network traffic hitting your router or switch when you experience the dropouts, again the managed switch could be used to slow all other connections down to prevent any interference from other traffic.

Thanks for the info. I will follow the guidelines and try

I will try that, which is what Roon’s Networking best practices guide recommends (thanks Noris). My current S8000 configuration has Qos and priority only set for the ST, Devialet and uplink port.

That was not an easy option. The audio rack is far from the router. I have a long run of CAT 7 cable from the router to the S8000.

During the dropouts there was nothing special going on. But, in any case the S8000 only services the audio gear, and my music is local to the ST.

1 Like

Thanks for the update! Do let us know how it goes and if you need further assistance here @Gustavo_Gabaldon!

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