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.
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:
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).
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.
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)
I get random disconnects on holo red also, looks like a network problem I can’t figure out. It fails to push FIFO sometimes.
Also, I have seen many questions on different forums without an answer. Can holo red be upgraded with CM5 module? No, not directly… while both CM4 and CM5 use same board layout, they are not drop in replacements. CM5 won’t boot from microsd on holo red. I will try to flash RedOS and NAA OS to the emmc, let’s see if it will boot and work.
Edit
Yeah, CM5 works fine on Holo Audio Red, its just the booting procedure defers from CM4 so if you want to swap OS, you have to dismantle the device, plug CM5 out, plug it into I/O board and flash emmc. RedOS was designed for CM4 and has compatibility issues with CM5. NAA OS works fine, i chose to stick with DietPi atm… lets see if these FIFO fails are gone.
Does NAA OS support other outputs ? With Red OS, I was using Red’s shairport-sync with output to tosslink. HQPlayer OS then, was using SB card with tosslink in, up sample and outputting via NAA back to Red.
RedOS shaiport-sync by default is ignoring volume control and no way to ssh login to change that
you did extract drivers/device trees from original RedOS image and embedd into NAA OS ? Since other Linux distributions do not seem to detect any audio interfaces. Only after i enable DWC2, USB interfaces were detected…
If you don’t use only NAA, then I would give Ropieee (in here you’ve a much newer version from the NAA client integrated than in RedOS and a modern kernel, which supports a lot of DACs in DSD native) a try.
Ropieee is a GUI only Linux distribution, it is sealed from logging into console. I could probably edit the image before flashing it to enable SSH… but dietpi is awesome, i wish someday they will release for Mac Studio…
No, the DDC is essentially same USB interface you can find inside Holo Audio DACs. It just outputs to S/PDIF, AES and I2S, instead of the DAC.
You can also use it separately from the RPi CM4 inside by connecting to the Red’s USB input. This will disconnect the DDC from the CM4.
NAA OS is plug-and-play on Holo Red. So it works correctly there out of the box.
P.S. Regarding device trees, Linux source code is under GPL v2 license and hence also device tree sources fall under GPL license and source code must be published.
If for some reason one would choose to upgrade holo RED with CM5, then the version without EMMC must be bought. The microsd reader controller is hardware disabled if the EMMC is present. Also wifi/bt module is of no use with REDs thick aluminum case and will only produce interference. CM5 works fine with RED and having a better CPU and more LPDDR is always good, you can even run HQPd on it, pcm or low freq sdm output.
How is the cooling fit? Since the CM is cooled through Red’s case. IIRC, the cooling contact points and thickness is slightly different between CM4 and CM5.
you did extract drivers/device trees from original RedOS image and embedd into NAA OS ? Since other Linux distributions do not seem to detect any audio interfaces. Only after i enable DWC2, USB interfaces were detected…