My output device logo & icon are displayed twice at the bottom of the signal path info. Everything else is working fine, so this is just a minor cosmetic issue.
Disabling & re-enabling the device make no difference. Likewise for quitting & re-starting Roon with the device enabled or disabled.
The following user seems to have a similar problem, albeit with a different output device:
Signal path displays device twice in Roon (ref#6E9WEQ)
Describe your network setup
Amazon eero router TP-Link Ethernet-over-mains adapters NetGear Ethernet switches (I have no network or connectivity issues)
I’ve emptied the specified folder in both the Roon & RoonServer paths and restarted Roon. This has reset all my endpoints back to their default configurations, but hasn’t solved the issue with the NOVAFiDELITY N25AMP showing up twice in the signal path info after it is re-enabled.
Just in case it’s relevant, this duplicate logo anomaly does not occur when I re-enable my other Roon Ready device (a miniDSP SHD).
Thank you for providing additional context here. We are working on the original issue with the partners team and will update here as soon as more information is available.
The hardware team is asking you to kindly confirm - do you have the Holo Red and N25AMP enabled in Roon as both a USB and Network device? If you try to temporarily disable one of the options (USB or Roon Ready) in Roon Settings → Audio and play to it, does it still show up duplicated in the signal path?
Thanks for letting us know! I see you also have a second instance of Roon Server available on a different machine. Does this issue happen no matter which machine you use to run Roon Server?
Our team is still investigating things internally as well - we hope to have more information to share soon.
We have raised your problem as internal ticket to R&D.
In the meanwhile, can you please clarify what did you mean under the quote ?
Is the issue going away when you reboot miniDSP even for N25AMP and Audio RED ? Or it’s just going away for miniDSP only (which you did not seem to report regarding this device) ?
Thank you for the update. We’ve brought this back to the attention of our Partners team so they can replicate the issue internally on the affected devices and report it to our R&D team.
We’ll keep you posted with any results or updates.