HQPlayer NAA thread

These components typically use the same specifications as the electronics built inside car’s dashboard. You can get WiFi routers for this category as well, and you could also use WiFi routers designed for outside use that can withstand wide temperature range, rain, etc.

Here’s my 5G WiFi/Ethernet router at the boat, powered over PoE from 12 VDC electrical system:

For computers, take a look for example here:
https://www.onlogic.com/eu/store/computers/rugged/karbon-800/
Which they specify to have “Operating Temperature: -40°C to 70°C”

2 Likes

If you need even more rugged machine, you can also get military grade ones, but it also means it becomes more expensive.

1 Like

Hello, I want to use a RPi (4 or 5, depending on the answer) to stream DSD512 upsampled music from my Windows PC (Roon → HQ Player Desktop → Network → Rpi w/ HQP NAA OS → Usb Rpi → DAC).

My DAC supports DSD512 just fine and my RTX 3080 can upsampled too, so, my question is, the USB port on the Rpi4 is capable of sending DSD512 to my DAC ? If not, what about Rpi5?

Thanks in avance !
(I never had a streamer before and want to start with the Rpi + HQP NAA OS option to see :grinning:)

What DAC? Do you have.

RPi4 will have no problem - depends if your DAC supports DSD512 with Linux.

We don’t know your DAC, but you can check to see its Linux support.

1 Like

DAART Yulong Aurora, but I plan to get a Holo Cyan 2.

My question is more regarding the capabilities of the USB port on the RPi than a DAC or even a HQP NAA question itself.

Reading through the thread it seems possible (DSD512 outputting to the RPi4 USB port running HQP NAA OS).
But I would like confirmation from someone who has already done it.

Rpi4 works without issues and according to this post it’s better than rpi5

1 Like

Everything I’ve experienced (I own May and Spring 2) and read (about Cyan 2) suggests that DSD256 with the right HQPlayer filters, modulators, and DAC correction is the sweet spot for Holo.

2 Likes

Thank you guys, I will pickup a RPi 4 and see how it goes…

May I ask, which OS are you using on the RPi 4 nowadays to use with HQP NAA (with wired network) ?

I read through the thread some suggestions like the NAA OS, Ropieee\RopieeeXL, DietPi and Gentoo.
Which one do you guys think is best ?
(I will manly use for HQPlayer, but AirPlay could be nice, I heard that RopieeeXL has AirPlay, is there any disadvantage on using RopieeeXL over the NAA OS ?)

RoPieeeXL works fine

2 Likes

Depends what you prefer. If you’d like NAA with absolutely minimal bloat and my latest software and drivers, then NAA OS is good choice. If you’d like most OS flexibility, then Raspberry Pi OS Lite with the networkaudiod “bookworm” package is a good choice.

I have not used the other ones, and those are not supported by me, but instead their respective authors. So I cannot comment much about those.

1 Like

Yes, works up to DSD1024 with Holo Cyan 2 / Spring 2/3, or Denafrips for example.

1 Like
  • 2024/10/02 21:38:06 Signalyst HQPlayer Embedded 5.7.1
  • 2024/10/02 21:38:06 Engine starting…
    2024/10/02 21:38:06 asoundlib version: 1.2.11
    2024/10/02 21:38:06 Found ALSA device: hw:CARD=NVidia,DEV=3 - HDA NVidia: HDMI 0
    2024/10/02 21:38:06 Found ALSA device: hw:CARD=NVidia,DEV=7 - HDA NVidia: HDMI 1
    2024/10/02 21:38:06 Found ALSA device: hw:CARD=NVidia,DEV=8 - HDA NVidia: HDMI 2
    2024/10/02 21:38:06 Found ALSA device: hw:CARD=NVidia,DEV=9 - HDA NVidia: HDMI 3
    2024/10/02 21:38:06 network Audio IPv6 support enabled
    2024/10/02 21:38:06 discovery from 0.0.0.0
    & 2024/10/02 21:38:06 discovered network audio: name=‘naa’ version=‘Signalyst Network Audio Daemon 5.0.2’ @192.168.0.66:43210
    & 2024/10/02 21:38:06 discovered network audio: name=‘naa’ version=‘Signalyst Network Audio Daemon 5.0.2’ @192.168.0.66:43210
    2024/10/02 21:38:07 discovery from ::
    2024/10/02 21:38:08 connect to 192.168.0.66:43210 [ipv4]
    2024/10/02 21:38:08 network endpoint: DST-0_CC0A:LVDS: LVDS (hw:CARD=DirettaA3AA,DEV=0)

IPv6 is enabled.
However, the connection is made with IPv4.
What is the cause?

Endpoint (NAA) is not responding back to discovery over IPv6.

Does this log mean that I am correctly connected over IPv6?

In rare cases, I get “connect to fe80::xxxxxxxxxxxxx [ipv6]”.

Yes, that’s correct.

You can try to help the case by letting NAA run for some time before starting HQPlayer. In case there’s a delay in auto-configuring the IPv6 there. IPv4 and IPv6 may take somewhat different time to get configured. It is also possible that due to this, networkaudiod service gets started before the IPv6 address is configured and as result IPv6 is not available. To check this, wait a while after NAA boot, and then issue “systemctl restart networkaudiod”.

Thank you very much.
I understand very well.

So, bought myself a Raspberry Pi 5 to play about with. Installed latest HQ Player OS Embedded for the Pi 5. Installed in a passive cooling Akasa case.
Achieved PCM 1.536 MHz no sweat but amazingly, but also DSD upsampling to 512, although the case gets a little hot. No dropouts.
Also, installed the NAA 502 image for the pi holored and it works with the Pi 5.
DAC’s fed: Holo Audio May and Cyan 2. HQ Desktop player run from both performance desktop and 2012 mac mini.
Comparing the performance (audio) of my Holo Audio Red and the Pi 5, I can’t detect any difference.