Just to provide more information, I have a Holo Cyan 2, which works perfectly as an HQPlayer endpoint over NAA via a RooExtend streamer. However, it won’t appear via ALSA as a normal Roon endpoint. I enclose a series of screenshots below showing that when RooExtend enables both RAAT and NAA (or just RAAT and not NAA, I’ve tried both), it appears in Settings / Audio. When I click on it, there are 3 levels of Holo Spring that appear as possibilities. Whether I click any of those 3 or the “My device isn’t here”, the result is the same - the device appears but says “Device not found” in red. When I click on the gear to change settings, it offers only the choices “Disable” or 'Retry" so there’s no further settings available to change.
I’m fine for now - I can play music via NAA / HQPlayer, which is why I purchased the Holo Audio Spring, but I thought it was strange and would like to resolve because I don’t always have my HQPlayer running.
For what it’s worth, I have many other endpoints - Denon AVR via AirPlay, Sonos, RooExtend → Schiit Yggdrasil, RooExtend → Schiit Bifrost 2, and all work fine. I’m not concerned that my network is not working.
It looks to me like rooExtend is showing in Roon. The device not found is then a message sent by rooExtend. Probably check the settings and configuration on the rooExtend? Also is the DAC connected by USB to rooExtend set to the USB input and turned on?
Hi thanks BlackJack. Yes, you can see above in the screenshot that the RooExtend (which is just acting as a RoonBridge) is passing the Holo Cyan 2 and advertising it as an available device to Roon. If the power of the device is off, or its not plugged in, then nothing appears in Settings / Audio.
Ok, bizarrely, after 10 days of struggling with this, it just resolved. I swear I didn’t do anything different. It just eventually, well, umm worked.
I would love to know if anyone from Team Roon has a clue what happened, that made it break, or what made it resolve. But it’s settled so no need to chase this one unless it recurs.
Thank you!
And… though I bought this DAC to do HQPlayer upsampling, it makes for a lovely NOS R2R DAC with redbook. Have been enjoying it this way all evening.
Hi @Johnny_Ooooops,
Thanks for letting us know you were able to resolve the issue with the Cyan 2. It’s always great to hear things are working again!
It’s tough to pinpoint the exact cause after the fact, but based on what you described, it does sound like a network-related issue—possibly something as simple as an IP address assignment or a temporary network hiccup. If anything similar crops up again, feel free to reach out and we’ll dig in further.