The case is about same temperature(unexpectedly warm) as it was with CM4. Even if there is a difference in thickness, you can bypass that with thinner or thicker thermopads. My RED is running 24/7, average cpu temp is 46-47C
Well, it’s happening again. On the output screen I can’t see DAC 200:Holo Red in device, only NetworkAudioAdapter. When I play from Roon, the indicator next to the track name in Roon shows it’s playing, the track indicator bar at the bottom doesn’t advance and the only message that pops up on HQPlayer Desktop is rersampler=diabled convolution=disabled.
I really don’t want to have to completely reflash the Red back to stock and then re-install HQPlayer OS on it.
Can I use DAC correction in HQPlayer with the standard Holo Red OS?
hallow
yes
dc work
Great, thanks.
I guess my follow up question is… what am I actually gaining by using HQPlayer OS on Red?
naa os or hqp os?
these are different
naa is just like red os minus holo web interface and holo compatibility options such as qobuz and spotify connect
hqp os can use instead of desktop with naa built in and can use with usb stick to boot direct and then manage via web page interface
it also do not support cuda
I was referring to installing the HQPlayer OS image onto Holo Red vs using Holo Red with the stock OS - for use only as a NAA
what do u use for main hqp server?
Mac Studio on the network to Red on network as NAA to T+A DAC 200 via USB.
Roon runs on Roon Nucleus also on the network.
since server is on mac
i advise to use naa os or red os as sole naa endpoint on red
and not hqp os that is server itself and may be cause of conflict
this may be why naa red os as primary naa is no longer seen if u flash or replace with hqp os as u already have server on mac
use this repository
Index of /bins/naa/images choose appropriate naa for rasberrypi holo red
It does work with hqp OS on Red, but every now and then HQPlayer desktop doesn’t recognize it and I have to start all over with reinstalling the OS on Red. I just don’t know why it suddenly stops working after being stable for weeks at a time.
If you want an answer, you have to present some evidence. Hqplayer and NAA logs at least.
I moved shairport-sync from my hqplayerd box to the RED. The RED’s DDC is good one, the interface is acting more adequately than snd_aloop device. The aluminium case is hot
cpu temp is 50C, so I guess heath management with CM5 is of ok.
Usually you would use NAA OS on Red instead of HQPlayer OS. Unless you are actually using HQPlayer Embedded on the Red.
This statement is true, but i couldn’t get it working yet. Received a CM5 lite version without EMMC, still cant boot from microsd, although REDs microsd reader is supported by CM5. If i flash the microsd card with PI imager, bootload / EEPROM utility, it boots and REDs LED starts blinking as it should. But if i flash NAA OS, the led starts red as usual, then blinks green for short period and red again… like kernel crashed during boot. The RED OS doesn’t blink green at all…
Did you flash the RPi5 version?
You will also need to modify config.txt to set the type-C port into host mode.
I did flash 5.1.8, the latest image. And the dr_mode is host by default. Or there is another option for usb-c ?
That should work then…