ROCK on NUC 8i3BEH with 8GB RAM. Roon build 1.7.571.
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Netgear Orbi system, one base router, one satellite router. ROCK is hard-wired (CAT-6) to the satellite. Music is stored on a Synology DS-418play, also hard-wired to the Orbi satellite. No apparent problems with any other devices connected to the Orbi. No Qobuz or Tidal. DSP is OFF.
Audio Devices (Specify what device youāre using and its connection type - USB/HDMI/etc.)
Devialet D-250 Expert (not Pro), also hard-wired to the Orbi satellite.
Description Of Issue
Dropouts and static, intermittent, not easily reproducible, but continual, maybe 3-4 times per hour, lasting a few seconds each. ROCK has been rebooted, with no apparent changes.
It worked for me too. I stuck a TrendNet unmanaged switch down stream of the Orbi router and my sonicTransporter-AP server (Roon Core) and Auaralic Aries G1 streamer have run more or less flawlessly ever since.
Worked for me - I had an issue list as long as my arm with my new orbiās - sticking a switch in between core and router (internet to switch, the connect core machine and Orbi router to switch) resolved almost all issues. Netgear is unresponsive on thisā¦
Sean: The Orbi Satellite router connects to the Orbi Base wirelessly, by design. So did you insert the switch between the Orbi and the Roon Core machine? It seemed like you were saying two different things there, but Iām probably misunderstanding and I want to be clear. Thanks!
From my troubles, I figure that Netgear Orbiās are not handling multicast traffic properly, hence the issues. Netgear wonāt give me a proper explanation for this. I am also running my Orbiās in AP mode so do not have access to all the fun stuff.
My setup is the main Orbi router and 3 satellites using wireless backhaul. My Roon core is in same room as my Orbi router so the connection is wired. I simply dropped a switch in between the core and the Orbi router, as opposed to having the Roon core plugged into the ethernet port on the back of the router directly. This eliminated almost all problems.
I still have some issues when Roon remotes are connected to an Orbi sattelite - zones disappearing, album art not available etc. - hence my hypothesis that the Orbiās firmware is just not ready for prime-time as far as multicast traffic is concerned. Have not yet tried using wireless backhaul (which I will bet will resolve the final issues)
Perfect ā thanks, fellas! My Orbi and core are not in the same room, but thereās a cable between them so Iām confident I can put a switch at one end of it! Will report tomorrow or the day after, when Iāve had a chance to get at it. Thanks again!
Thanks again to you fellas for the replies. The verdict is: Partial success. Completely unscientific estimate is dropouts reduced by 50%. Anybody have any success with other interventions? (I have plenty of Scotch whisky, but I think thatās a tree-forest-sound question.)
Is there any reason to believe that the NUC is underpowered? Specifically, if I were to upgrade to an i5 or i7, is there any reason to think processor capability would make a difference in this situation? Thanks for any insights.
Now that youāre getting better performance, can you check to see if playing to system output of one of your remotes shows the same symptoms as the Devialet? Letās see if weāve narrowed the issue down a bit. Let me know!
Just looked that upā¦ thanks! The Nucleus is a 7i3 and the Nucleus+ is a 7i7ā¦ so should be fine. Also, do you think it should have been typeset as a āNUCleusā?