I have not tested recently the ALSA feature, mainly because it is not fully compatible with HQPlayer.
it should create an usual multichannel device, supposedly HQPlayer should notice its software and not a hardware device.
HQPlayer expects to operate on “hw” devices, while such would be a software device. It may, or may not work. But software devices are not really officially supported.
If we have a DAC with
I2C-PROGRAMMABLE ANY-FREQUENCY CMOS CLOCK GENERATOR
Is it possible for NAA OS on RPi5 to pass rate family via GPIO over i2c ? Or additional coding is required?
I think you could script it from the ALSA parameters.
Testing Naa V6 on a Raspberry Pi (Spring 3 KTE DAC): significant bugs, occurring randomly, hissing instead of music (everything seems normal when playing back audio in HPQ Desktop or HQP Client), sometimes the DAC wasn’t recognized… Switching back to Naa V5 solved the problem!
Running HQP embedded 5.16.1 on Ubuntu and NAA OS 6.1.0 on rpi4 and all is working fine here
Using a 64 bit OS?
NAA 6.1.0 networkaudiod_6.1.0-68_armhf.deb is failing on my 32 bit ARMv7 cpu running Debian Trixie. Reverting back to NAA 5.1.5 is my current fix.
Which one? If NAA OS not sure, anyway it’s the only one available
Ok, we are running different setups you are on naa 64 bit.
Mine is a 32bit CPU on Audalyic AH90 with networkaudiod_6.1.0-68_armhf.deb.
What does NAA v6 bring? Any significant new feature/s?
The audio streaming part itself has no changes yet, but the DAC detection is improved and the new protocol version better enables third parties to implement NAA as well, like Eversolo already did. That Eversolo project was major driver for this new version.
1 Like
A fix has been issued for the armhf devices (naa/linux/trixie/networkaudiod_6.1.1-69_armhf.deb).
The Audalyic AH90 using Debian Trixie OS with the new NAA v6 is running smoothly. Thanks very much Jussi.
2 Likes
My HQPlayer Desktop (5.16.2) can’t find the NAA on my UP Board (using naa-611-x64.7z bootable image). This happend after I installed naa-611-x64 on my UP Board.
I am using Windows 11 Pro (10.0.26200 version 26200)
I have rebooted my computer, UP Board, DAC (Topping DX9), switch, router, wrote a new naa image on the USB-stick (03-Jan-2026 01:09) with no result.
Any suggestion for a solution.
From the log:
2026/01/03 14:51:00 1c: [0:0] 0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000111111000000
2026/01/03 14:51:00 DSP thread pools enabled (2 / 3)
2026/01/03 14:51:00 DSP pipelines enabled
2026/01/03 14:51:00 Pipelined engine enabled
2026/01/03 14:51:00 Pre-process after metering
2026/01/03 14:51:00 DirectSDM disabled
2026/01/03 14:51:00 Audio engine: network
2026/01/03 14:51:00 NAA output set channels: 2 (2)
2026/01/03 14:51:00 NAA output supports DSD with any base rate
2026/01/03 14:51:00 Null output set channels: 2 (2)
2026/01/03 14:51:00 Normal buffers
2026/01/03 14:51:00 Playlist uses track gain
2026/01/03 14:51:00 Optimal ISO fixed volume
2026/01/03 14:51:00 PCM gain compensation: 0.623735 (-4.0999999999999996 dB)
2026/01/03 14:51:00 Set volume: -3.010300 +
2026/01/03 14:51:00 Automatic rate family disabled
2026/01/03 14:51:00 Full pause processing
2026/01/03 14:51:00 NAA output network Audio IPv6 support disabled
2026/01/03 14:51:00 NAA output discovery from 0.0.0.0
2026/01/03 14:51:00 SDM conversion parameters (5, 0)
2026/01/03 14:51:00 DSD 6 dB gain enabled
2026/01/03 14:51:00 Control active volume range: -12 - 0 dB
2026/01/03 14:51:00 Listen discovery on ::
2026/01/03 14:51:00 Listen discovery on 0.0.0.0
2026/01/03 14:51:00 Set filter: 30 / 30
2026/01/03 14:51:00 Set oversampling: 40 / 43
2026/01/03 14:51:00 Set dither: 9
2026/01/03 14:51:00 Set modulator: 20
2026/01/03 14:51:00 AutoSDM disabled
2026/01/03 14:51:00 Audio engine is normal
2026/01/03 14:51:00 IntegratorM: IIR
2026/01/03 14:51:00 Audio engine SDM mode enabled
2026/01/03 14:51:00 Automatic output rate switching enabled
* 2026/01/03 14:51:00 Control server allow remote control
2026/01/03 14:51:01 NAA output discovered 0 Network Audio Adapters
2026/01/03 14:51:02 NAA output network Audio IPv6 support disabled
2026/01/03 14:51:02 NAA output discovery from 0.0.0.0
2026/01/03 14:51:03 NAA output discovered 0 Network Audio Adapters
2026/01/03 14:51:04 NAA output network Audio IPv6 support disabled
2026/01/03 14:51:04 NAA output discovery from 0.0.0.0
2026/01/03 14:51:05 NAA output discovered 0 Network Audio Adapters
2026/01/03 14:51:06 NAA output network Audio IPv6 support disabled
2026/01/03 14:51:06 NAA output discovery from 0.0.0.0
2026/01/03 14:51:07 NAA output discovered 0 Network Audio Adapters
2026/01/03 14:51:08 NAA output network Audio IPv6 support disabled
2026/01/03 14:51:08 NAA output discovery from 0.0.0.0
2026/01/03 14:51:09 NAA output discovered 0 Network Audio Adapters
2026/01/03 14:51:10 NAA output network Audio IPv6 support disabled
2026/01/03 14:51:10 NAA output discovery from 0.0.0.0
2026/01/03 14:51:11 NAA output discovered 0 Network Audio Adapters
2026/01/03 14:51:12 NAA output network Audio IPv6 support disabled
2026/01/03 14:51:12 NAA output discovery from 0.0.0.0
2026/01/03 14:51:13 NAA output discovered 0 Network Audio Adapters
2026/01/03 14:51:14 NAA output network Audio IPv6 support disabled
2026/01/03 14:51:14 NAA output discovery from 0.0.0.0
2026/01/03 14:51:15 NAA output discovered 0 Network Audio Adapters
2026/01/03 14:51:16 NAA output network Audio IPv6 support disabled
2026/01/03 14:51:16 NAA output discovery from 0.0.0.0Does the image boot up properly there? IOW, it should end up in login prompt. You can also login as “root” (no password) and check what “systemctl status networkaudiod” says.
Based on your log, no NAA’s are found in the network.
UP Board’s BIOS has sometimes habit of changing the boot device selection by itself if it recognises changes to the USB boot media. In such case it falls back to trying to boot from the internal eMMC.
I don’t have a keyboard and monitor to connect to the UP Board. Any other way to not make it boot from the internal eMMC?
Does the Raspberry Pi 4/5 have the same problem when changing the naa image?
No, if it decides to forget about the USB boot device, only way is to connect display and keyboard to it and fix the BIOS setting… For example if the USB stick gets changed to different brand and model, this will happen. If you always use the same stick and make sure the device is disconnected from power when unplugging and plugging the USB stick, then it won’t usually happen.
No, those will always boot from the microSD card when it is inserted. This “feature” is specific to how certain PC BIOS implementations behave.
Strange. I tried to go back to naa-515-x64 and now HQPlayer finds my NAA and DAC again. I have used the same stick all the time. So the problem must be related to naa-611-x64.
I will of course try the naa-611-x64 image again to verify it is image related.
Ok, forget the whole thing. Now HQPlayer finds my NAA and DAC with naa-611-x64 image installed on the same stick as I always have used. Sometimes you can go crazy when it doesn’t work even if you are doing it the same way as always.
After upgrading all my RopieeXL devices to 2026.01 HQPlayer 4 does not recognize any of my RPI connected USB DACs anymore.
Apparently and unfortunately the included NAA 6.0.1 upgrade does not work with HQplayer v4 anymore.
Does anyone have the same experience ?
NAA 6.x is not compatible with HQPlayer versions prior to 5.16. While HQPlayer works with NAA versions up at least from NAA 3.x.
I think NAA 5.x still works with HQPlayer v4, but I have not checked.