HQPlayer Embedded seeing but not showing NAA [Resolved by fresh install]

Hi @jussi_laako ,

I’m running HQP Embedded on a Linux server under Ubuntu 22.04.4 LTS with your low latency kernel.

I have substituted in a Raspberry Pi 4b running the v5 NAA image replacing a microRendu running a v.4.8 NAA through SonicOrbiter. The Pi boots up and I can see it on the network.

IP6 is enabled on the HQP Config page. The Pi is connected by USB to a Holo Spring 1 which is on and the USB input is selected.

The configuration page doesn’t show any NAA device and I get no sound.

I’ve refreshed device multiple times and swapped in and out of ALSA/NAA and IP6, rebooting each time. Same thing.

The log shows that HQP can see the Pi NAA, but for some reason it keeps trying to discover it and seems to be stuck in a loop.

These are excerpts from the log:


* 2024/06/09 13:49:20 Signalyst HQPlayer Embedded 5.6.2
+ 2024/06/09 13:49:20 Engine starting...
  2024/06/09 13:49:20 asoundlib version: 1.2.6.1
  2024/06/09 13:49:21 Found ALSA device: hw:CARD=PCH,DEV=0 - HDA Intel PCH: ALC897 Analog
  2024/06/09 13:49:21 Found ALSA device: hw:CARD=NVidia,DEV=3 - HDA NVidia: HDMI 0
  2024/06/09 13:49:21 Found ALSA device: hw:CARD=NVidia,DEV=7 - HDA NVidia: HDMI 1
  2024/06/09 13:49:21 Found ALSA device: hw:CARD=NVidia,DEV=8 - HDA NVidia: HDMI 2
  2024/06/09 13:49:21 Found ALSA device: hw:CARD=NVidia,DEV=9 - HDA NVidia: HDMI 3
  2024/06/09 13:49:21  network Audio IPv6 support enabled
  2024/06/09 13:49:21  discovery from 0.0.0.0
& 2024/06/09 13:49:21  discovered network audio: name='naa-00cc1b3d' version='Signalyst Network Audio Daemon 5.0.0'  @192.168.20.92:43210
& 2024/06/09 13:49:21  discovered network audio: name='naa-00cc1b3d' version='Signalyst Network Audio Daemon 5.0.0'  @192.168.20.92:43210
  2024/06/09 13:49:22  discovery from ::
& 2024/06/09 13:49:22  discovered network audio: name='naa-00cc1b3d' version='Signalyst Network Audio Daemon 5.0.0'  @[fe80::da3a:ddff:fe6a:e3ea%enp4s0]:43210
& 2024/06/09 13:49:22  discovered network audio: name='naa-00cc1b3d' version='Signalyst Network Audio Daemon 5.0.0'  @[fe80::da3a:ddff:fe6a:e3ea%enp4s0]:43210
  2024/06/09 13:49:23  connect to [fe80::da3a:ddff:fe6a:e3ea%enp4s0]:43210 [ipv6]
  2024/06/09 13:49:23 CUDA offload requested
...  
2024/06/09 13:49:23 Automatic rate family disabled
  2024/06/09 13:49:23 Full pause processing
& 2024/06/09 13:49:23 NAA output discovered network audio: name='naa-00cc1b3d' version='Signalyst Network Audio Daemon 5.0.0'  @192.168.20.92:43210
& 2024/06/09 13:49:23 NAA output discovered network audio: name='naa-00cc1b3d' version='Signalyst Network Audio Daemon 5.0.0'  @192.168.20.92:43210
  2024/06/09 13:49:23 SDM conversion parameters (8, 12)
  2024/06/09 13:49:23 DSD 6 dB gain enabled
  2024/06/09 13:49:23 Initializing processing for matrix pipeline 0
  2024/06/09 13:49:23 Matrix pipeline 0: 0 -> 0 0/1
  2024/06/09 13:49:23 Initializing processing for matrix pipeline 1
  2024/06/09 13:49:23 Matrix pipeline 1: 1 -> 1 0/1
  2024/06/09 13:49:23 Matrix processing enabled
...

2024/06/09 13:49:23 Server starting...
  2024/06/09 13:49:23 Control active volume range: -60 - -3 dB
  2024/06/09 13:49:23 Listen discovery on ::
  2024/06/09 13:49:23 Listen discovery on 0.0.0.0
  2024/06/09 13:49:23 Enable UPnP Renderer functionality for interface: auto
  2024/06/09 13:49:23 Adding interface 'enp4s0' for UPnP Renderer
  2024/06/09 13:49:24 NAA output discovery from ::
& 2024/06/09 13:49:24 NAA output discovered network audio: name='naa-00cc1b3d' version='Signalyst Network Audio Daemon 5.0.0'  @[fe80::da3a:ddff:fe6a:e3ea%enp4s0]:43210
& 2024/06/09 13:49:24 NAA output discovered network audio: name='naa-00cc1b3d' version='Signalyst Network Audio Daemon 5.0.0'  @[fe80::da3a:ddff:fe6a:e3ea%enp4s0]:43210
  2024/06/09 13:49:25 NAA output discovered 1 Network Audio Adapters
? 2024/06/09 13:49:25 NAA output adapter 'mrendu-00D020' not found
  2024/06/09 13:49:26 NAA output network Audio IPv6 support enabled
  2024/06/09 13:49:26 NAA output discovery from 0.0.0.0
& 2024/06/09 13:49:26 NAA output discovered network audio: name='naa-00cc1b3d' version='Signalyst Network Audio Daemon 5.0.0'  @192.168.20.92:43210
& 2024/06/09 13:49:26 NAA output discovered network audio: name='naa-00cc1b3d' version='Signalyst Network Audio Daemon 5.0.0'  @192.168.20.92:43210

Everything after ‘NAA output discovery from ::’ then seems to repeat until the view of the log runs out.

Any ideas ?

edit /etc/hqplayer/hqplayerd.xml to remove the old mrendu-00D020 NAA: it is still searching for it

i don’t remember if reconfiguring from HQPlayer embedded ‘s web interface will do the trick or not

1 Like

I’ve several times changed the NAA client and in every case I’d to save the new NAA client in the HQPlayer configuration.

1 Like

Thanks guys,

I’ve played around in hqplayerd.xml (taking care to save a copy first as hqplayerd-old.xml) but when I try to comment out or edit the references to NAA output adapter ‘mrendu-00D020’ I either get similar endless searching for whatever I enter (such as 0), or the web interface becomes inaccessible.

In the log the Pi NAA appears to be detected as:

name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @192.168.20.92:43210

Any suggestions about how to edit the following line in the xml file ?

<network address=“mrendu-00D020” any_dsd=“0” dac_bits=“20” device=“hw:CARD=X2,DEV=0” dualwire=“0” friendly_name=“mrendu-00D020: X-SPDIF 2: USB Audio” ipv6=“1” pack_sdm=“0” period_time=“0”/>

Thanks for your thoughts !

There is no need at all to modify the hqplayerd.xml file.
HQPlayer will modify it itself if/when needed.
Are you sure the usb connection to the dac is working? Try to change the usb cable

1 Like

Yes, no need to edit the config file, but open the config tab, select your new NAA (it must available there) and save then the new config.
For to be save: Restart (sudo systemctl restart hqplayerd) HQPlayer.

1 Like

A few advances, but no music !

Stefano, I think you were right. Once I used a new USB cable the DAC started displaying an input of DSD512 so something had changed. The prior USB cable was working fine with the microRendu yesterday so who knows what happened there. Maybe a wire got pulled somewhere.

On the configuration page I could also now see the Network Audio Backend:

naa-00cc1b3d: xCORE USB Audio 2.0: USB Audio

But no music !
The log still shows the poor thing looking for the microRendu.

I tried Burkhardt’s suggestion, but to no avail. The Pi NAA shows up as the backend but no change to the loop in the log.

Another thing I’ve noticed is that no changes I make to the Configuration page get applied. If I try to change the filter or modulator and hit Apply it says Failed and reverts to the old configuration.

These are some relevant entries from the log:

& 2024/06/10 11:40:26 discovered network audio: name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @192.168.20.92:43210
& 2024/06/10 11:40:26 discovered network audio: name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @192.168.20.92:43210
2024/06/10 11:40:27 discovery from ::
& 2024/06/10 11:40:27 discovered network audio: name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @[fe80::da3a:ddff:fe6a:e3ea%enp4s0]:43210
& 2024/06/10 11:40:27 discovered network audio: name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @[fe80::da3a:ddff:fe6a:e3ea%enp4s0]:43210
2024/06/10 11:40:28 connect to [fe80::da3a:ddff:fe6a:e3ea%enp4s0]:43210 [ipv6]
2024/06/10 11:40:28 network endpoint: xCORE USB Audio 2.0: USB Audio (hw:CARD=x20,DEV=0)

The final line wasn’t there before and I think it means HQP can see the DAC through the Pi NAA.

2024/06/10 11:40:29 Server starting…
2024/06/10 11:40:29 Control active volume range: -60 - -3 dB
2024/06/10 11:40:29 Listen discovery on ::
2024/06/10 11:40:29 Listen discovery on 0.0.0.0
2024/06/10 11:40:29 Enable UPnP Renderer functionality for interface: auto
2024/06/10 11:40:29 Adding interface ‘enp4s0’ for UPnP Renderer
2024/06/10 11:40:29 NAA output discovery from ::
& 2024/06/10 11:40:29 NAA output discovered network audio: name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @[fe80::da3a:ddff:fe6a:e3ea%enp4s0]:43210
& 2024/06/10 11:40:29 NAA output discovered network audio: name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @[fe80::da3a:ddff:fe6a:e3ea%enp4s0]:43210
2024/06/10 11:40:30 NAA output discovered 1 Network Audio Adapters
? 2024/06/10 11:40:30 NAA output adapter ‘mrendu-00D020’ not found
2024/06/10 11:40:31 NAA output network Audio IPv6 support enabled
2024/06/10 11:40:31 NAA output discovery from 0.0.0.0
& 2024/06/10 11:40:31 NAA output discovered network audio: name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @192.168.20.92:43210
& 2024/06/10 11:40:31 NAA output discovered network audio: name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @192.168.20.92:43210

And then it starts looping, still hung up about not finding the mrendu.

When I ask Roon to play then I think this happens:

+ 2024/06/10 11:46:13 Control connection from 127.0.0.1:58586
+ 2024/06/10 11:46:13 Control started from 127.0.0.1:58586
2024/06/10 11:46:13 NAA output discovered 1 Network Audio Adapters
? 2024/06/10 11:46:13 NAA output adapter ‘mrendu-00D020’ not found
& 2024/06/10 11:46:13 Stop…
2024/06/10 11:46:14 NAA output network Audio IPv6 support enabled
2024/06/10 11:46:14 NAA output discovery from 0.0.0.0
& 2024/06/10 11:46:14 NAA output discovered network audio: name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @192.168.20.92:43210
& 2024/06/10 11:46:14 NAA output discovered network audio: name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @192.168.20.92:43210
2024/06/10 11:46:15 NAA output discovery from ::
& 2024/06/10 11:46:15 NAA output discovered network audio: name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @[fe80::da3a:ddff:fe6a:e3ea%enp4s0]:43210
& 2024/06/10 11:46:15 NAA output discovered network audio: name=‘naa-00cc1b3d’ version=‘Signalyst Network Audio Daemon 5.0.0’ @[fe80::da3a:ddff:fe6a:e3ea%enp4s0]:43210
& 2024/06/10 11:46:16 Playlist clear
& 2024/06/10 11:46:16 Playlist add URI: http://127.0.0.1:30000/d2c1e0622d7e4e4f8616b3b43bfab2f4/stream.raw
& 2024/06/10 11:46:16 Play
2024/06/10 11:46:16 Offload: resampler=disabled convolution=disabled
+ 2024/06/10 11:46:16 Playback engine running
2024/06/10 11:46:16 IntegratorM: FIR2
2024/06/10 11:46:16 Engine reinit, rate or blocksize change triggered
2024/06/10 11:46:16 Rate: 48000, block size: 10240, frame size: 640
2024/06/10 11:46:16 Block size: 10240 (sample: 8)
2024/06/10 11:46:16 Analysis initialized
2024/06/10 11:46:16 Oversampling: long Gaussian poly
2024/06/10 11:46:16 Modulator: adaptive seventh order m-bit ec
2024/06/10 11:46:16 Integrator: FIR2
2024/06/10 11:46:16 Playback engine ratio: 470.4
2024/06/10 11:46:16 Initializing processing for matrix pipeline 0
2024/06/10 11:46:16 Matrix pipeline 0: 0 → 0 0/1
2024/06/10 11:46:16 Initializing processing for matrix pipeline 1
2024/06/10 11:46:16 Matrix pipeline 1: 1 → 1 0/1
2024/06/10 11:46:16 Matrix processing enabled
2024/06/10 11:46:16 Set volume: -3 +
2024/06/10 11:46:16 Offload: resampler=enabled convolution=disabled
2024/06/10 11:46:16 Initialization complete, starting audio engine
2024/06/10 11:46:16 Teams: 1
2024/06/10 11:46:16 Places: 1
2024/06/10 11:46:16 Parallel threads: 8
2024/06/10 11:46:16 Nested parallelism: 4
2024/06/10 11:46:16 Parallel pipelines: 4
! 2024/06/10 11:46:16 NAA output clNetEngine::PushSDM(): not connected to adapter
! 2024/06/10 11:46:16 clHQPlayerEngine::Execute(): push to FIFO failed
2024/06/10 11:46:16 Stop request (reset)
& 2024/06/10 11:46:16 Stop…
- 2024/06/10 11:46:16 Playback engine stopped
& 2024/06/10 11:46:16 …stopped
2024/06/10 11:46:16 Set volume: -3 +
2024/06/10 11:46:16 NAA output discovered 1 Network Audio Adapters
? 2024/06/10 11:46:16 NAA output adapter ‘mrendu-00D020’ not found

@jussi_laako : Where could HQP be hearing about the mrendu ? The mrendu is not on the network at all and HQP seems to have discovered the Pi NAA fine (after a new cable, thanks Stefano) and is showing it as the Network Backend.

Any help appreciated.

Try this:

  • rename hqplayerd.xml file to something else
  • restart HQPlayer
    In this way HQPlayer should recreate the hqplayerd.xml file from scratch (and any reference to Rendu will be deleted)
1 Like

A good idea, which I tried earlier. What happened was that Roon couldn’t find HQP and the web configuration page wouldn’t open.

Also, at some point I removed my licence (which actually saved) but now it won’t recognise my key so I’m on a trial version.

Tomorrow I think I will uninstall HQP completely and downloadand install it from scratch.

On the bright side, my turntable is sounding great.

In your log, you’ll see, that your DAC is not found:

Do you’ve also restarted your DAC and/or tried another usb output from your NAA client?
Do you’ve also tried to send PCM directly without processing and also (if UPNP isn’t disabled) without Roon through the NAA client to your DAC?
And take care: HQPlayer needs an exclusive use of the DAC.

1 Like

Thanks for the suggestions. I restarted the DAC, then tried another usb output on the Pi, both to no avail. So then I decided to uninstall hqplayer completely and reinstall it.

sudo systemctl stop hqplayerd.service
sudo dkpg --purge --force-all hqplayerd

After that I reinstalled from scratch as follows:

sudo apt update
sudo apt upgrade
sudo wget https://signalyst.com/bins/hqplayerd/jammy/hqplayerd_5.6.2-19intel_amd64.deb
sudo apt install -f
sudo apt autoremove
sudo hqplayerd -s hqplayer hqplayer
sudo systemctl enable hqplayerd
systemctl start hqplayerd
sudo systemctl status hqplayerd

Its not necessary at all to change hqplayer/password to hqplayer/hqplayer as I do above but I always do it because my script above was adapted (slavishly copied would also be accurate) from Chris Connaker’s script on Audiophile Style (thanks Chris !) and I find it sort of comforting that if my hqplayer config gets hacked then so will his …

Anyway the above all worked and I now have music again. My hqplayer embedded finally seems to have forgotten all about the microRendu and so far I have no issues with the Pi running an NAA directly into the USB input of my ancient Spring 1. I even found the right licence key and was able to upload it again.

Now to experiment with DAC correction, which was the whole idea of running NAA 5. Anyone offering odds on my breaking something with that also ?

Thanks very much to everyone who offered suggestions. Always great to feel you are not alone when there is no music.

In hindsight, I should have checked the USB cable, as suggested by Stefano, quicker and I think my mucking about in hqplayerd.xml then caused a whole raft of new problems which prevented me writing to the config page, so I’d suggest not doing that.

1 Like

The issue above was that the NAA name got changed. So the output device needed to be reselected.

If “nano” is used to edit hqplayerd.xml, it will change the ownership and permissions of the file. Which results in HQPlayer not being able to write updated configurations. “vi” / “vim” doesn’t have this issue, these preserve the permissions.

I don’t think anything breaks with the corrections. But I have not yet created corrections for Spring 1. Only for Spring 2, Spring 3 and Cyan 2. I do still have the older Spring 1 and Cyan DSD devices, so from technical perspective I can create corrections for those as well.

1 Like

Thanks Jussi,

Nothing was showing up on the Config page under Output Device because of the bad cable. Once I put in a good USB cable to the DAC the Pi showed up.

By that time I had already used nano on hqplayerd.xml and consequently couldn’t save the Configuration page which is why I found myself in a world of pain.

I used to use vi a little bit way back when, but unlike some it never got hardwired into my fingers. Nice to learn it still has a reason to exist.

When you get enough time (ha ha!) to create corrections for the Spring 1 I would like to try them out and see if they make a difference. There’s probably a few of us out there still using it. I don’t claim to have much of an ear though. Previously I was using a Matrix Audio X-SPDIF2 to turn the USB from the microRendu into an I2S input for the Spring. Now the Pi is just going straight into the Spring’s USB input. I have read about how the USB on the Spring 1 wasn’t the best and got improved in later versions, but to be honest, I can’t remember what the I2S sounded like well enough to notice any difference with the USB.

Ps: Have you written anywhere about what DAC corrections are, what changes the corrections make to the music and how intensive they are on CPU/GPU ?

Have you had any pushback from manufacturers who do not appreciate bein told that their DAC needs correction ?

Not much. Other than the corrections are undoing changes the DAC ends up making.

Nothing at all so far…

1 Like