This is the diagnostics data for Roon Support: { "ipv4_connectivity": {"status":"NetworkTimeout","status_code":998,"error":""}, "ipv6_connectivity": {"status":"NetworkTimeout","status_code":998,"error":""}, "external_ip": {"actual_external_ip":"45.aaa.bbb.ccc","actual_external_ipv6":"2600:ddd:eee:fff:ggg:hhh:iii:jjj","router_external_ip":"null"}, "natpmp_autoconfig": {"status":"NotFound"}, "upnp_autoconfig": {"status":"NotFound"}, "multinat_autoconfig": {"status":"Failed","error":"No uPnP Routers found on LAN"} }
Thank you for your post. You’ll need to specify the target IP (the RoonServer IP address listed in your Roon Settings → ARC page) in your manual rule for port forwarding.
If you select “edit” or “change” in your screenshot, you should see an option for a dropdown menu under Needed by Device. Look for an option to enter IP address and then paste the IP address from Roon Settings → ARC.
Restart RoonServer after you’ve saved the rule and let us know if this helps.
Do you have any second routers in this setup, by the way, or only the AT&T gateway?
Thanks for the tip. I seem to have gotten the Roon ARC problem solved (instead of entering the IP address of the target device, I was able to select “Nucleus Titan” which is the name that I gave the server in the Roon software. That seems to have fixed the problem.
I am having another problem. Roon Ready devices (in particular, my DAC (which is also a streamer) keeps getting dropped by Roon.
So I’ve had this system for a couple of years and it’s worked perfectly until Friday morning. AT&T pushed some updates to my router which reset a lot of the settings; but now the Nucleus Titan just isn’t performing correctly. It won’t allow me to search for artists or music, it lags for 10 - 30 seconds or more before it starts to play music; when it does play music, after about a minute it stops playing. And finally, as I mentioned, the Roon Ready devices intermittently appear and disappear from the list of available audio sources.
I have restarted the Nucleus Titan and power cycled it a few times today, but not help.
I am wondering if it’s time to do a factory reset and start the entire process all over again. My music files are on a NAS drive, and I’ll be able to reconnect to my Tidal and Qobuz subscriptions.
The only concern wondering whether my existing playlists will be recoverable. I do have backups run every few days; but I don’t know how reliable that is.
Is it possible that a factory reset / reinstallation of the Nuclues Titan may resolve the issues?
I can confirm that Roon appears to be the only thing in the house that isn’t working properly after resetting my router.
I think the next step here is to enable some diagnostics on your account so our technical staff can get some more insight into what’s going on here.
However, before I enable this feature, I’d like to ask for your help ensuring we gather the right information.
First, can you please reproduce the issue once more and note the time at which the error occurs. Then respond here with that time, and I’ll make sure we review the diagnostics related to that timestamp.
Well, my very positive news is that this morning so far, I have NOT been able to reproduce the failures. I’ve been playing music for more than 15 minutes and I haven’t had a single failure.
In contrast, yesterday, every single piece of music that I played was being disrupted (usually within less than 45 seconds after the song had started).
My Roon ARC test also shows “READY” this morning, which is positive. When I go for a drive later this morning, I will verify that the connection works through my Android phone and car interface.
I really don’t know why the network / Roon has “stabilized” this morning; but I am grateful. Here’s hoping that it lasts.
I will reply to this topic again if I encounter any more issues (including the time that I encounter any problem.
I was playing music from a playlist. After about 8 - 10 minutes or so, at 8:19 am Pacific time, the player stopped. I waited for about 30 seconds and then hit the “play” button again and it resumed; but I don’t know what caused it to stop.
So the failure (albeit brief) happened at 8:19 am Pacific time.
We’ve taken a closer look at logs. Here’s what we see happening around the time that music drops out:
RoonServer is playing DSD64 DSF → 24/352. Then three things happen:
RoonServer loses sight of networked endpoints over multiple protocols - both RAAT and Cast
Roon reconnects to the Roon Ready networked endpoints and the audio stream begins
Dropouts of precisely 176400 bits per second begin to accumulate. This is equivalent to one half of the total data at the MQA sample rate you’re playing
Number three above strongly suggests that RAAT is dropping half-frames to stay in sync with the MA-3i DAC when you’re outputting DSD64 DSF → 24-bit/352KHz.
This sample rate is incredibly vulnerable to clock drift. If you can provide a little more detail about your network setup, we can likely help pin this down. Worst case, you’ll need to apply a lower sample rate.
Can you please share a screenshot of the Device Setup screen for this Zone?
Does this occur with local and streamed DSD files? What about if you lower the sample rate to something else, like 196KHz?
Lastly, do you have a mesh network, managed switches, or any other network equipment sitting in between RoonServer and this endpoint? This appears to be a USB DAC - is it connected directly to RoonServer?
