I downloaded the new NAA 5.0.2 for Holo Red and flashed it on the microSD card, but couldn’t get it to work. T+A DAC200 can’t see Red with 5.0.2. I tried to flash it twice but no. I flashed 5.0.0 back and DAC200 immediately sees the Red again.
Jussi,
I had the same issue with NAA 5.0.2, with my Holo Red. When HQP Desktop did see the new software it kept crashing, So at the moment I have reloaded the original Holo Audio software.
I also tried it on my PI5 and the same issues with HQP desktop crashing.
You can also use the previous 5.0.0 OS if you encounter problems with the new one.
What kind of crash message do you get?
Looks like I made a mistake with default config.txt regarding Holo Red, I rebuilt the image and it should work now. You can just download it again.
1 Like
When I selected any option with Holo Red / HQP Desktop, the hour-glass cursor appeared and it locked the software.
I will try again now that you have made adjustments. (Does that include the Pi5?)
Many thanks.
what changed with new NAA OS ?
Anything related to USB input, for RPi4 for example ?
Jussi,
Holo Red and Pi5 now working.
Thanks
1 Like
Kernel got updated to 6.6 which is latest LTS kernel. Practically every OS component got updated. RPi5 is now supported. For example previous image for CuBox-i / Rendu was using 5.15 kernel. Updated support for DACs, etc. But the networkaudiod module itself is the same that has been shipping in HQPlayer OS already.
1 Like
I’m using the latest NAA 5.01 Bookworm version under Dietpi because it allows me to remotely start and shut down my Intel NUC. I’ve already tried NAA OS but I couldn’t start it remotely, but it’s ok to shut it down remotely. With NAA 5.02, will I be able to remotely start the NUC or not? Another question: Is there a possible difference in sound rendering between the NAA OS and NAA Bookworm versions?
I think WOL should work, this is not particularly related to the OS.
But I personally leave my NAAs running 24/7/365, or just switch off the power using a remote controlled mains switch or similar.
It depends what you mean by this. The networkaudiod software module is largely the same, apart from couple of minor changes. The OS is different. Kernel largely matches my custom kernel for Jammy.
I started having occasional dropouts after I updated to NAA 5.0.2 with Holo Red. Not sure what caused this but flashing back the 5.0.0 seems to have solved the issue. I changed nothing else in between.
I’ve had history of having occasional dropouts with my streaming configuration, but they were completely solved by changing the HQP buffer setting from Default to 10ms, as recommended by Jussi back then. The reason was that the Holo Red’s buffer was overrun (or is overflown the correct term?) with Default setting and smaller buffer-setting helped with this. This happened like over six months ago and I haven’t had problems since then… until now with 5.0.2. Not sure if it’s about buffer this time but 5.0.0 seems to work normally and 5.0.2 doesn’t.
These same issues have happened with NAA on various revisions of Ropieee on the Holo Red. It seems to be some sort of permutations of the RPi compute module 4 used in the Red and kernels. The NAA OS kernel change has likely caused this. Current version of Ropieee works. Playing with the buffer time seems to mitigate it a bit but does not resolve.
1 Like
NAA OS 5.0.0 used kernel version 6.1 while the NAA OS 5.0.2 switched to 6.6. IIRC, both should have largely the same DAC support, so you can stick to 5.0.0 image if it works better.
What you describe sounds like 802.3x Flow Control (aka Pause Frames) not being active for some reason, typically a smart switch with the feature disabled. So I would first look into the network setup to make sure this Ethernet feature is supported and becomes active. On a smart switch port statistics, you can usually also monitor number of pause frames sent/received on each port. This gives a hint whether the feature is functioning.
I remember that we talked about flow control last time also when troubleshooting the dropout issue. Flow control is enabled for all ports on my managed Netgear GS108E switch, which feeds the Holo Red. It’s also enabled on my server machine’s NIC settings.
@jussi_laako One cool reason for NAA on iOS and Android would be similar use to this (when in the car). Sure you can setup a laptop in the car but not quick/practical for daily use.
iOS is more feasible than Android. CoreAudio on iOS is not much different than macOS. While Android is a strange beast and rather difficult environment.
But where would the HQPlayer be running in such case, if you have NAA on Android? I would rather setup an automotive computer in the car, for example in trunk, running HQPlayer Embedded server.
1 Like
Would have to be via VPN on the phone - not easy for daily drive.
Mmmm yes a fanless one , no moving parts can work
I only need 2ch with PCM and convolution for “room” correction
Have you setup such?
What car do you drive and more important, what sound system inside 
I want to test the impact of room correction inside car. I’ll try it with Roon running on laptop first, with Acourate correction
Same here. I think it’s something to do with the CM4. Maybe @spockfish would be willing to describe the specific change he made to resolve this with Ropieee.
1 Like
And extended temperature range. There are automotive computers rated for example from -40C to +50C.
My previous car, a Volvo, had a spinning HDD in it’s IVI system inside the dashboard and it worked just fine for 8+ years, through Finnish winters and summers and rough roads. There are 2.5" HDD’s manufactured for these conditions. My current car has some SSD though.
In the past for some friends yes. Not for myself.
I turn on the car stereos couple of times a year to listen radio or Spotify. I practically never listen anything in the car. No specific brand stated for the stereos.
1 Like
Summer here often goes over +40C , so the boot/trunk if parked outside could easily go past +50C
And then I would worry about the WiFi router needed in the boot too! At that temperature ?