Solution for Nucleus One Audio Dropouts

I discovered an unexpected cause (I assume) to a dropout problem on my Nucleus One. I never saw it in any Help articles or Community chat, so thought I’d share.

I was having dropout problems with my new Nucleus One that was hardwired to my network and connected via network (Wi-Fi) to my Pre Amp.

The problem did not happen with my old Roon core on a Mac Book Air (Wi-Fi connected).

I ran some trials and he data indicated a few things:

It had something to do with sampling and bit rate:

192kHz/24 bit always dropped

96 kHz/24 bit often dropped

48 kHz/24 bit sometimes dropped

44.1 kHz/16 bit never dropped

It also seemed to happen more frequently later in the day and in the evening

Since the problem did not happen on the old Roon core, I ruled out a network performance issue.

I looked for issues related to time of day and did some speed tests to see if network speed could be a factor. Speed was generally slower later in the day but was more than enough (350-570 Mbps) to stream big files.

On a whim, I did two speed tests: one with the phone sitting on the Pre Amp, and another with the phone sitting on the Nucleus One which was inside a cabinet directly under the Pre Amp that sat on top of the cabinet.

The Pre Amp network speed was about 125 Mbps faster than the Nucleus speed. I moved the Nucleus on top of the cabinet next to the Pre Amp to equalize network speed.

The fix seemed to work. Been playing for about 3 days - and evenings - no problem.

I am guessing that the cabinet slowed the Wi-Fi signal enough that the two components, because of different network speeds, weren’t synced up enough for the higher data tracks? I’m not an IT or network guy, so I could have it all wrong. I’d appreciate any thoughts on root cause based on this write-up.

Thanks!

WIFI travels between device and router, not device to device. Also, larger files will obviously be more prone to drop outs than smaller files.

Thanks for the comment. Helped a lot and made me look harder.

I put the Nucleus back in the cabinet to see if the problem happened again. I did not.

While doing this I realized that after moving the Nucleus out of the cabinet the first time, I had moved the origin end of its ethernet cable from my whole home system switch directly into the back of the router. I’d made two changes and only focused on one.

Does it make sense that it could have been an issue with the switch? Regardless, I’m glad it finally works.

Thanks for the help.

1 Like

The Nuc One was delivered last week! Delivery and shipping with notification were perfect. Installation (without installing an SSD) was quick. But then during operation, Music stutters and Roon stops. Without making any changes to the network or anything else, the error message “slow data transfer, hardware problems!” came up without any changes to the network or anything else. This problem occurred because I only swapped the One for the Nucleus+! Put the Nucleus+ back into operation and everything was working as normal! At the same time, I noticed that ARC was interrupting every download and reporting connection problems. So I searched and found the error! On the Melco Switch S100, the Melco N1Z (music storage) was on a 100MB port! I plugged the N1Z into the 1GB port. Activated the Nucleus One again and hey presto, it plays without any problems! The same goes for ARC, downloads are now very fast! Apparently the hardware of the One is more demanding than that of the 5 year old Nucleus+!
You never stop learning :smile:

Hi @Scott_Simmons,

Thank you for your post.

Interference in the WiFi signal can introduce packet loss to Roon’s lossless, uncompressed audio protocol. Roon will re-send any packets reported missing by the endpoint, but if enough of them go missing, playback will eventually break down.

The fact that physically moving the Nucleus One has improved playback at higher sample rates suggests that interference was a component here. Hardwiring the Nucleus to the endpoint via ethernet in question would be the immediate remedy, but requires longer cable runs.

If you rely on a mesh network with multiple nodes or access points, you’ll also need to take into account the line-of-sight and relative arrangement of those. Please ensure that any settings related to multicast forwarding are enabled.

You mentioned the problem has improved, but if you provide a set of manual logs from your Nucleus, we can pinpoint precisely what the machine logged as the problem previously. You’ll need to use the directions found here and send over a set of logs to our File Uploader at your convenience. Thank you!