Third Floor: The Roon Nucleus is connected by CAT6 Ethernet cable to a Luxul 12-port/8 PoE+ Gigabit Managed Switch model AMS-1208P. The switch is connect by Ethernet cable.
Ground Floor: The switch is plugged by CAT6 cable to a Luxul Epic 5 Router. The router connects by Ethernet to the Xfinity xFI Gateway Modem model name CGM4331COM by vendor Technicolor.
Connected Audio Devices
dCS Rossini Apex DA converter connect by Ethernet to the third floor switch. Balanced cables to an integrated amplifier. iPhone and iPads used as remotes.
Number of Tracks in Library
Description of Issue
Each time I use Roon, I receive an intermittent warning message on my remote that the Roon core is disconnected. The screen changes to the Roon icon for a couple minutes. Then, the artist and track I was previously listening to will spontaneously repopulate the screen. I then press play to start the music again.
A second problem occurs when I intermittently receive the message that Qobuz or Tidal are loading too slowly. Roon skips the song and move to the next track.
Both problems occurred even after changing the switch to a TP link unmanaged network switch.
I have no other streaming problems gear other than the Nucleus. When I use the Mosaic app with the dCS DAC, I can stream Tidal and Qobuz without any problems.
The unit is running out of memory. From your completed support template, I can safely say it’s not your number of tracks since I’d expect your Nucleus to handle up to 100k tracks. I discussed this with my fellow techs and we will need to escalate the issue to our developers to figure out why this is happening.
I will get back to you as soon as I can. Likely tomorrow.
Rename the “RoonServer” folder to “RoonServer_old”
Restart the RoonServer in the WebUI to generate a new Database
On the Roon Remotes, press “Use another Core” and connect to the new database
As far as #2 goes, we should be able to handle this many devices. The only factor here could be how many of these devices you have grouped into each zone and how many zones you’re attempting to play to at any given time. We didn’t see evidence that this was the cause but I can’t help but keep coming back to this as a potential cause. I did hardware testing for Roon for some time and at the peak of this testing I had 34 devices associated with my core. I will list steps for refreshing RAAT. Please note, if you do this you will need to re-enable all of your devices and set up any zones again. You will also lose any and all DSP settings so please be advised:
It’s hard to say but entirely possible. To my knowledge, there was no downtime with Roon account servers or any other service.
If you do happen to notice interruptions in sound going forward, please note the date/time/track played and let me know. I can further isolate the problem in diagnostics with that information and will be able to offer additional guidance.
Did you happen to note the information above? I’d like to take a look at the diagnostics logging but can’t comb through all of the logging to find the problem. Please let me know. I would like to see this issue disappear altogether!
So it looks like it’s not really a core disconnect problem but a network latency-related one. As you can see in the next log (same timeframes as above), the Chord seems to be losing its network connection. This is reflected in the "bw limit:0kb
I only have one idea before I can point to a network issue. If this doesn’t change the situation we’ll need to look at simplifying some elements of the network and testing. One thing I might suggest right away is ensuring the Xfinity gateway is indeed in bridge mode. I see at least one instance of the Mac having an Xfinity address and that implies it might not be in bridge mode.
This will clear your core’s cache and I am hoping this will prevent us from having to go any further!
I am still seeing network timeouts. Was this what you were listening to today when it happened?
“Album of the year J. Cole”?
02/08 18:12:37 Trace: [Naim Audio Uniti Atom HE] [Lossless, 24/44 MQA TIDAL FLAC => 24/44 MQA] [100% buf] [PLAYING @ 1:56/2:19] Album of the Year (Freestyle) - J. Cole
02/08 18:12:37 Info: [stats] 23185mb Virtual, 1169mb Physical, 489mb Managed, 544 Handles, 89 Threads
02/08 18:12:42 Trace: [Naim Audio Uniti Atom HE] [zoneplayer/raat] sync Naim Audio Uniti Atom HE: realtime=65439427733287 rtt=500us offset=65310084733us delta=-385us drift=-3864us in 121.7955s (-31.726ppm, -114.212ms/hr)
02/08 18:12:42 Trace: [Naim Audio Uniti Atom HE] [Lossless 99.8x, 24/44 MQA TIDAL FLAC => 24/44 MQA] [100% buf] [PLAYING @ 2:01/2:19] Album of the Year (Freestyle) - J. Cole
02/08 18:12:43 Debug: FTMSI-B-OE ti/EE05680A exit thread signalled
02/08 18:12:43 Debug: FTMSI-B ti/EE05680A download status: AllBlocksDownloaded accessTimeout:True openFiles:1 prev:(FirstBlockRetrieved,True,1)
02/08 18:12:43 Info: FTMSI-B ti/EE05680A: allocated bw changed from 51200 to 0 kbps
02/08 18:12:43 Info: FTMSI-B 1 FileCache ti/80FFC500 dwStatus:AllBlocksDownloaded files:1 accessTimeOut:False priorities: ('zoneplayer:40':1) ('zoneplayer:50':1) --> bw limit:0kbps
02/08 18:12:43 Info: FTMSI-B 2 FileCache ti/EE05680A dwStatus:AllBlocksDownloaded files:1 accessTimeOut:True priorities: ('zoneplayer:50':2) --> bw limit:0kbps
This time it was the Naim but these network issues aren’t the source of your issues, it’s the out of memory messages we’re seeing in diagnostics.
We might want to see if the issues happen on a fresh database. I would like to have you try this if we could. Make sure you back up your DB to a safe location before embarking on this and once done, refrain from re-importing the DB to test the situation. If you would, please run Roon for 24 hours or until you duplicate the issue before re-importing.