Since it has just one ethernet interface, the regular x64 NAA OS image should work.
Thanks, will give it a go.
Dirk
Hello HQP gurus.
One of my RPi being used as NAA is not being seen by HQP since the power got turned off this morning.
Was fine last night.
So far I’ve unplugged Pi and DAC and re-started both. Made sure usb was selected on DAC, before trying to connect HQP again.
HQP is working fine on my other music system in another room.
Sometimes IP addresses change? Could that be it?
Wipe the SD card and rewrite NAA OS image to the SD card.
If that fails, then the SD card maybe corrupted after the power off, so try a different SD card.
If that fails, the RPi damaged?
Are the SD cards so fragile.
If I am starting re-writing cards, maybe this is the right time to go HQP 5….unless 6 is imminent?
1 Like
If the re-write doesn’t work, it’s either the SD card or RPi.
I guess you could reboot your router in case it is the IP address thing you suspected.
Proceed with HQP 5. Too early for HQP 6 ! 
Note that if there is any IGMP enabled network equipment, the network infrastructure must be up before NAA and HQPlayer are started. Otherwise the multicast subscription from NAA is not held by the IGMP enabled devices.
But as usual, important part is to check that the HQPlayer host doesn’t have multiple network interfaces enabled (such as VPN virtual interface), otherwise the discovery multicast may end up on wrong interface.
2 Likes
Without a better place to ask…
Is there a feature request somewhere to hold HQPlayer configs per NAA endpoint. I’m about to add a second DAC I will front-end with a new NAA endpoint and the 2 DACs are diametrically opposed when it comes to config.
Also, do you have any recommendations for the Borderpatrol DAC which has the TDA1543 chip in it? I know I need to set to 16 bits and 96 resolution. You previously recommended using TPDF or Gauss1 dither. Thank you!
It already does that - individual profile settings for each dac connected by NAA.
I have 3 dacs connected to my fitlet3 NAA through different usb ports. I created 3 dac profile settings 1) ifi pro idsd; 2) dsc2; 3) dsc3
Each profile will have dac specific settings, I just need to go to hqp settings to load up the dac profile for the dac and choose NAA output for the dac
1 Like
Is that a desktop thing? I forgot to mention I run embedded. I am unfamiliar with DAC profiles. I will look deeper.
I do use desktop but I did recall embedded allows something similar. Miska can confirm
At the moment there’s nothing fancy to swap configurations. This has been on my TODO-list for a while, but not implemented yet. So at the moment you can just swap hqplayerd.xml files and then restart hqplayerd service. You could write this into two simple scripts you can run over ssh. Not necessarily super convenient, but it works.
Since I don’t have measurement data for that DAC, that’s the best bet for it. Either of those dithers are fine.
1 Like
Hi @jussi_laako with this new update , does it mean 4 x 2-channel DACs (assume identical model DACs, same DAC settings/filters) can be used with 8-channel DSP crossover inside HQPlayer?
Most interesting with multiple Holo DACs for example
Theoretically yes, but the synchronization is a challenge if you want to use it for cross-overs, as they are still independent devices. At least it would be good to have all clock synchronized to the same word clock.
Since Holo DACs don’t have unique USB identifiers, you would need as many NAAs as you have DACs. Unlike with something like ADI-2… So you likely see why RME chose to have the serial number encoded as part of the device USB id…
1 Like
Yes but the cost of 5V fanless NAA’s is minimal compared with these DSD Direct DACs.
But if the synchronisation is not gurarantted for crossovers, probably is not the right solution.
If you had 1 x NAA with a powered USB hub on one of its USB ports, right now could you have 4 x ADI-2’s (AKM) and properly use for 8-channel DSP crossover at DSD256 ?
No need for the USB hub either if you just have four spare USB ports.
You would still need to chain the four ADI-2’s with S/PDIF, set one as master clock and the rest as slaves. And then hope for the best that they manage to start in sync, which is not guaranteed.
For musicians playing together their own instruments, few samples off doesn’t matter. But for loudspeaker cross-over that will have some varying phase difference between frequency band is something you’d likely rather not have.
So for L/R split, or multichannel split it may work out. But for one speaker, the output should really be from a single DAC running from a common clock. Same applies for something like Ravenna as well.
1 Like
Unfortunately, NAA 5.1.0 no longer allows playback.
The number of channels is incorrectly determined.
This DAC has 2 channels available, but it is judged as 1 channel.
Please correct.
ALSA output PCM format: S32_LE
ALSA output PCM bits: 32
ALSA output PCM physical width: 32
ALSA output PCM rates: 44100 - 1536000
ALSA output PCM channels: 1 - 2
ALSA output active PCM channels: 1
How is your number of channels set in HQPlayer?
Channels = 2
ALSA output set channels: 2 (2)
OK, I found and fixed this. Interesting that your DAC is advertising single channel format. I don’t recall seeing such with any of mine.