Lately Roon does not recognize my Auralic Aries G1. I turn the Auralic, it boots, shows Roon logo and correct Static IP address. However on Roon it does not show up on a list of available end points. Only when I unplug Auralic power cable for about a minute, plug it back in let it boot it is recognized on Roon as end point device. Both Roon and Auralic have latest stable versions. Conection is ethernet, no Wi-Fi involved. Has anyone experienced anything similar?
This is likely your DAC acting up, if you are using USB to connect it?
If you look into Aries âAdditional Operationsâ, youâll likely see that it is not seeing the DAC.
Roon will only âseeâ the Aries if it is set to âdigital outputsâ or if it is set to an (active and responsive) USB-DAC.
Are you using a phone to control Roon ? If so , turn on airplane mode for about 7-8 seconds and turn off . See if you can connect now .
Aries is setup to Digital Output, not using USB, but coaxial cable to connect to DAC.
1 Like
Iâm using Wi-Fi only tablet, dedicated only to be a Roon control app, nothinh else is running.
I will check Additional Operations on Aries, thank you for the hint.
1 Like
Good, i think this is likely an Auralic issue, rather than Roon.
And if your Aries is set to digital outputs, it should be seen by Roon at all times, as long as itâs actually seen on the network.
Make sure the Aries is reachable (with Additional Operations, as an example) when it disappears from Roon.
A couple of settings to maintain on the router for these devices to play nice are:
Multicast routing ~ Active
IGMP Snooping ~ Active
Other than that, i can only recommend to âerase all settingsâ on the Auralic, thats not a particularly big effort to restore afterwards but might solve some erratic behaviour.
Good luck! 
If the Auralic is set to USB output and the dac is switched to Digital ouputs , the G1 wont show in Roon.
I had a G1 and it stumped me a couple of times by not showing in Roon.
Im pretty sure this is a Aurlaic G1 output issue.
Thank you Mikael
2 Likes
Hi @Predrag_Kos,
Diagnostics indicate a RoonReady instance of an Aries G1 associated with your RoonServer.
Do you require any assistance with the Roon side of this issue, or can we move this to Audio Gear Talk for further suggestions on what appears to be a specific issue affecting digital output settings on the G1?
Itâs not an Auralic Issue. Roon are to blame for making unrealistic demands.
I suppose you refer to the ability for multi room sync. Thatâs a core feature of Roon Ready and if some manufacturer canât achieve it when everybody else can, then I donât see how itâs an unrealistic demand
You can look at it like that.
You can also question the value of 5x stricter limits for Ethernet devices compared to wifi devices. Does that mean this core feature of Roon Ready doesnât really work on wifi-only devices?
Maybe thereâs a technical reason for it, but we can only guess.
We donât need to guess whether losing device manufacturers from the ecosystem is good for Roon though.
We already know that itâs necessarily more prone to errors, depending on the wifi quality and the number of devices in synced zones.
I can agree to that, but this is the opposite of what the post I replied to had stated.
Sure, but itâs also not good for Roon to continually make exceptions for the requirements of Roon Ready (and if Auralic gets one, Iâm sure there are others who want one too)
All good points. Note that I am not suggesting an exception for Auralic, but rather a revision of the Roon Ready spec on this part. It seems like the optimal experience is already only available in an all-Ethernet environment.
Besides, devices with both technologies appear to get tested over wifi by default / chance. Shouldnât they all be re-certified to ensure that if the consumer plugs in the Ethernet cable, the device is up to spec?
And finally, it sounds like the latency is due to Auralic buffering/DSP. Wouldnât that also impact Roon/Muse with different endpoints with different DSP experiencing different latency? Even if Muse somehow guards against this and scales back DSP to remain within latency bounds, I wouldnât say this is a better consumer experience.
Finally - how about Roon letting tweak individual latency expectations for endpoints? It could then time streams accordingly to make sure all devices create audible output in sync. Roon could even provide defaults per device / manufacturer so customers wouldnât have to adjust them. Sure the synchronized audio would then play with the latency of the slowest device but I feel like weâre getting to a pretty decent solution here.
I am sure there are ways for Roon to support finding a mutually beneficial solution here, and I really hope they are doing that. This âif a $99 device can do it, why can Auralic notâ is not useful - devices are built differently and Auralic devices also sound different from $99 devices.
Iâm only writing this but my reply applies to most of your post:
All good points, too. I donât want to argue either way as I donât have the facts nor the expertise. I was only prompted to reply to the other post (not yours) saying that itâs all Roonâs fault and they are being unreasonable, with the same lack of facts.
This seems a nightmare for Roon in the best case and in the worst case may be impossible as manufacturers might make changes in firmware updates that might affect the latency.
[edit: maybe RAAT could have a parameter for this that the manufacturerâs code supplies (and could change). Iâm not sure how much we can rely on manufacturers getting it right, but if itâs feasible it might be a good thing)
I didnât say that. I said others manage, which includes multi-10K devices.
Good call, the latency tweak might not be feasible. Either way I am sure the folks at Roon have considered it and if it never ships thereâs probably a good reason for it.
Also, did not mean to put words in your mouth wrt $99 device comment. Was meant to be just an illustration but I see how it reads now.
Seems it is time to go listen to some music and let this certification matter sort itself out 
1 Like