HQPlayer Randomly Stops Seeing Holo Red

I’ve run into an issue a few times. Using Roon, sometimes between tracks HQPlayer won’t play and when I open preferences it no longer shows the Dac 200:Holo Red under device. The Holo Red is running Jussi’s HQ Player image. Sometimes turning the Holo Red off and on fixes it, other times I need try combinations of turning my computer, DAC or Holo Red on and off to get it to see it again. Sometimes I have to reinstall the original image of Holo Red back on it using the micro SD card, reconfigure it, let HQPlayer find it, then turn off the Holo Red and reinstall Jussi’s image onto it.

I never know which combination will work and sometimes it can take hours to get up and running again.

Does anyone know why this keep happening?

Is it possible you have the dac200 defined/active in Roon as well as in Hqplayer?
If so, try to disable dac200 in Roon.

1 Like

No, I never added the DAC 200 in Roon. Only set up HQPlayer.

After a couple of hours of trying various resets it finally all worked again after going back to the standard Holo Red OS, rebooting my computer, and launching HqPlayer. Then it found the Holo Red. Reinstalled HqPlayer OS on the Red and all was good…

Until just now. Was fast forwarding through tracks on Roon and then the system suddenly stopped playing and HQPlayer no longer sees Red.

This is getting annoying. It can take hours to get the system up and running again sometimes.

I am a little bit confused by what (or how) you are saying here.

Why would you change between the original Holo Red image and Jussi’s image.
One should stick with one image, preferably Jussi’s image if you use the Red only as NAA.

Second thing that bothers me: if HQPlayer finds the Holo Red, and you then reinstall a new image, you are losing your configuration again.

Now, this is what I see/need to do if my dac is not seen.

When my dac 200 is power off, this is what the configuration looks like:


so no devices at all

after powering on my dac 200, and ‘refreshing devices’ , configuration looks like this:


which is the wrong dac interface

Selecting the right interface and then Apply to get the right naa interface

From then on, you should be OK, as long as you remember to power on your dac before you play any music. As your Holo RED is a low power device, I advice to leave it powered on all the time (that’s what I do anyway).

Hope this helps?
Dirk

You’re misunderstanding what I’m saying.

I always use the Red with Jussi’s image on the SD card.

If my system locks up, there’s no way to get it all to work again unless I first reinstall the stock Holo Red onto it using the SDcard. Then HQPlayer will see the red and re-establish the connection.

Then I have to reinstall Jussi’s OS again. If I try to get everything working again after the system locks up without first reinstalling the stock Red OS I can’t get HQPlayer to rediscover the Red.

My Dac and Red are always on, so it’s not a USB handshake issue.

Sorry, running out of ideas.
Cannot help you then.
Dirk

What does HQPlayer log file tell about the issue?

One potential reason is that the DHCP lease expires without NAA OS being able to renew it. Or the DHCP server decides to change the IP when the existing lease expires.

But I would recommend to take a look what kind of errors are reported in HQPlayer log file. (please do not post lengthy log files here in messages, either use attachments or email your log to me directly as email attachment)

And if you just need NAA functionality, I recommend to use the NAA OS image instead of HQPlayer OS image.