HQPlayer's Network Audio Adapter

[Miska]

3 hours ago, ASRMichael said:

Jussi, question?

 

Does HQ player use more CPU processing when upscaling from wave 96khz 24bit to DSD128, compared to upscaling wave 44.1khz to DSD 128?

 

Both are upscaling to DSD128. Just the original source format is different?

 

Why am I asking this? All my wave 44.1khz work on setting I like, but when I go to 96khz 24bit with same settings it skips. So I thought HQplayer has more processing to do on 96khz files?

 

There is no simple or straightforward answer, other than "it depends". Effectively, the amount of processing power needed may be higher though. Overall, impact when using -2s filter variants is different from using single stage variants.

 

[gixxer]

Hello,

 

Having issue discovering NAA device on Windows 10 Pro.  Log file snippet below.  

 

This symptom can be recreated with both version 3 and 4 of HQPlayer Desktop from the same Windows 10 Pro machine.

 

The relevant part is discovering 0 NAA.

* 2019/10/14 09:14:36 Starting...
  2019/10/14 09:14:36 Signalyst HQPlayer Desktop v3.25.4
  2019/10/14 09:14:36 Engine selected: 
  2019/10/14 09:14:41 Restore GUI state
  2019/10/14 09:14:41 libDSP version 20.7.3
  2019/10/14 09:14:41 CUDA convolution offload requested
  2019/10/14 09:14:41 Number of processor cores: 6
  2019/10/14 09:14:41 DSP thread pools enabled (2)
  2019/10/14 09:14:41 Pipelined DSP enabled
  2019/10/14 09:14:41 Audio engine: network
  2019/10/14 09:14:41 Network Audio IPv6 support disabled
  2019/10/14 09:14:41 Discovery from 0.0.0.0
  2019/10/14 09:14:42 Discovered 0 Network Audio Adapters
  2019/10/14 09:14:42 Set channels: 2 (2)
! 2019/10/14 09:14:42 createEngine(): clHQPlayerEngine::Initialize(): clNetMiniEngine::Initialize(): adapter not found

 

I have disabled all firewall settings from Windows Security, domain/private/public network firewall are all off.

 

I have recreated with different Windows 10 Pro machine in the same network, much more bear-bone configuration. 

 

Is there something i'm missing from my setup with HQP versions 3 and 4 with regards to using them in Windows 10 system?

 

Basic communication tests between Windows 10 Pro network interface and microrendu IP address, show reachable.  And firewall has been disabled at Windows 10 Pro side.

 

C:\Users\georg>tracert 192.168.90.128

Tracing route to RENDU-010268 [192.168.90.128]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  RENDU-010268 [192.168.90.128]

Trace complete.

C:\Users\georg>

    C:\Users\georg>ping 192.168.90.128

Pinging 192.168.90.128 with 32 bytes of data:
Reply from 192.168.90.128: bytes=32 time<1ms TTL=64
Reply from 192.168.90.128: bytes=32 time<1ms TTL=64
Reply from 192.168.90.128: bytes=32 time<1ms TTL=64
Reply from 192.168.90.128: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.90.128:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\georg>

 

 

 

As a comparison, the same NAA device however can be seen from Windows 7 Pro machine.  It's log snippet here.  And there is only one NAA device in the local network.

 

* 2019/10/14 08:58:07 Starting...
  2019/10/14 08:58:07 Signalyst HQPlayer Desktop v3.25.4
  2019/10/14 08:58:07 Engine selected: 
  2019/10/14 08:58:12 Restore GUI state
  2019/10/14 08:58:12 libDSP version 20.7.3
  2019/10/14 08:58:12 CUDA convolution offload requested
  2019/10/14 08:58:12 Number of processor cores: 8
  2019/10/14 08:58:12 DSP thread pools enabled (3)
  2019/10/14 08:58:12 Pipelined DSP enabled
  2019/10/14 08:58:12 Audio engine: network
  2019/10/14 08:58:12 Network Audio IPv6 support disabled
  2019/10/14 08:58:12 Discovery from 0.0.0.0
& 2019/10/14 08:58:12 Discovered network audio: name='rendu-010268' version='Signalyst Network Audio Daemon 3.5.5'  @192.168.90.128:43210
  2019/10/14 08:58:13  Network endpoint: Brooklyn DAC: USB Audio (hw:CARD=DAC,DEV=0)
  2019/10/14 08:58:13 Discovered 1 Network Audio Adapters
  2019/10/14 08:58:13 Set channels: 2 (2)
+ 2019/10/14 08:58:13 Connect to 192.168.90.128:43210
  2019/10/14 08:58:13 Network format: 44100/32/2 [pcm]

 

 

Thanks much.

 

[Miska]

6 hours ago, gixxer said:

Hello,

 

Having issue discovering NAA device on Windows 10 Pro.  Log file snippet below.  

 

This symptom can be recreated with both version 3 and 4 of HQPlayer Desktop from the same Windows 10 Pro machine.

 

The relevant part is discovering 0 NAA.

* 2019/10/14 09:14:36 Starting...
  2019/10/14 09:14:36 Signalyst HQPlayer Desktop v3.25.4
  2019/10/14 09:14:36 Engine selected: 
  2019/10/14 09:14:41 Restore GUI state
  2019/10/14 09:14:41 libDSP version 20.7.3
  2019/10/14 09:14:41 CUDA convolution offload requested
  2019/10/14 09:14:41 Number of processor cores: 6
  2019/10/14 09:14:41 DSP thread pools enabled (2)
  2019/10/14 09:14:41 Pipelined DSP enabled
  2019/10/14 09:14:41 Audio engine: network
  2019/10/14 09:14:41 Network Audio IPv6 support disabled
  2019/10/14 09:14:41 Discovery from 0.0.0.0
  2019/10/14 09:14:42 Discovered 0 Network Audio Adapters
  2019/10/14 09:14:42 Set channels: 2 (2)
! 2019/10/14 09:14:42 createEngine(): clHQPlayerEngine::Initialize(): clNetMiniEngine::Initialize(): adapter not found

 

 

Please check from Windows 10 network adapter settings window that all other network adapters are disabled. Typically this problem appears when there are multiple active network interfaces.

 

[gixxer]

14 minutes ago, Miska said:

Please check from Windows 10 network adapter settings window that all other network adapters are disabled. Typically this problem appears when there are multiple active network interfaces.

 

Indeed.

 

Been searching through this forum, and found following post,

 

HQPlayer windows NAA

 

, where you had mentioned the same, i.e.

 

Quote

Relevant part is here. No NAA's found on the network. Please check that on both machines you have only one network interface enabled.

 

For me, consistency is discovering the microrendu after disabling the VirtualBox network interface.

 

Understood the workaround.

 

 

 

My "primary" main Windows box runs Windows 7 Pro and HQPlayer, with only a single network interface. 

 

I needed different box to run some test around HQPlayer + NAA = playback stutters/staggers at different spots in the music playback, and has always been this way.  I've been living with it to a a point where today wanted to try to root cause it.  I knew that there are lot of variables so narrowed down eventually to network/communication between PC and microrendu, which is on the same LAN segment/switch.

 

After trial and errors, found following page that discusses the network interface priority,

 

 

Looked at my setting in the same area, and found this, that "wrong" network interface is at the top,

 

 

Moved the correct connection to the top,

 

 

Keeping everything else the same, had the playback ran for >7 hours.  No drop.  Knock on wood.

 

Test format that previously, consistently shown drops, even with poly-sinc-xtr-2s + ASDM7 + Auto + DSD now plays without drop,

 

44.1k / 224 / 2 --> 11.2896M

 

 

Just banging my head that the fix was this simple.

 

 

 

 

 

 

[Outlaw]

IS IT BETTER TO ASSIGN A STATIC IP ADDRESS FOR NAA DEVICE AND HQPLAYER PC ?

[Miska]

6 hours ago, Outlaw said:

IS IT BETTER TO ASSIGN A STATIC IP ADDRESS FOR NAA DEVICE AND HQPLAYER PC ?

 

For NAA it doesn't really matter, but doesn't harm either. For HQPlayer it makes life easier with Roon, because you don't need to keep changing Roon's configuration every time DHCP server decides to assign different IP to the HQPlayer machine. Because unfortunately Roon doesn't support HQPlayer auto-discovery the HQPlayer Client is using. Adding support for such is probably not priority for them. If you use HQPlayer Client or UPnP, then it doesn't matter, because both use auto-discovery.

 

[madman73]

HI all, hi @Miska.

 

I'm trying to test an AMD E350 APU Mainboard (SAPPHIRE Pure White Fusion E350M1W) as a Linux based NAA.

i've used the last naa-360-x64 image, and i've got the attached error.

Can you help me to understand what is wrong?

 

Thanks in advance.

[Miska]

4 hours ago, madman73 said:

HI all, hi @Miska.

 

I'm trying to test an AMD E350 APU Mainboard (SAPPHIRE Pure White Fusion E350M1W) as a Linux based NAA.

i've used the last naa-360-x64 image, and i've got the attached error.

Can you help me to understand what is wrong?

 

Thanks in advance.

 

Looks like the instruction set supported by the APU (from 2011) is not enough to run this image. Solution would be to install for example minimal Ubuntu, Debian or Fedora and the networkaudiod package there. To make maximize compatibility, you could use 32-bit version instead.

 

[madman73]

On 10/28/2019 at 9:10 PM, Miska said:

 

Looks like the instruction set supported by the APU (from 2011) is not enough to run this image. Solution would be to install for example minimal Ubuntu, Debian or Fedora and the networkaudiod package there. To make maximize compatibility, you could use 32-bit version instead.

 

Can you build a 32 bit version of your 64 bit NAA iso? 

[Miska]

6 hours ago, madman73 said:

Can you build a 32 bit version of your 64 bit NAA iso? 

 

It is now available on the server, hopefully it works for you.

 

[madman73]

22 hours ago, Miska said:

 

It is now available on the server, hopefully it works for you.

 

Great @Miska !

 

I'll try it as soon as possible, and i'll report here.

Thak you!

[madman73]

Hi @Miska, the 32 bit image doesn't  boot. I've fixed this using the 64bit iso and changing the loader folder and the core iso file (can you check this??). i'm booting from an USB 8 GB pen drive.

 

Now i can load the 32bit image, i get the naa login prompt, but my hqplayer doesn't recognize the NAA. i use the JLSounds USB Interface on my dac that is working fine if directly connected to my hqplayaer PC.

 

I also think that the NAA recognize the dac as if i unplug/plug the USB cable, i get the attached message.

 

What is wrong?

Thank you.

 

 

[Miska]

3 hours ago, madman73 said:

Now i can load the 32bit image, i get the naa login prompt, but my hqplayer doesn't recognize the NAA. i use the JLSounds USB Interface on my dac that is working fine if directly connected to my hqplayaer PC.

 

Sounds like potential network problem. I assume NAA is connected to your regular home network so it can get IP from DHCP server? And that you have only single network interface active on the HQPlayer machine.

 

3 hours ago, madman73 said:

I also think that the NAA recognize the dac as if i unplug/plug the USB cable, i get the attached message.

 

Looks correct. You can login as "root" (no password) and run "aplay -l" and it should list your DAC.

 

You can check if the network interface is getting IP address properly by running "ifconfig". If all the interfaces don't come up properly, systemd is holding back starting the NAA service (it has dependency to have all network interfaces online).

 

[madman73]

Yes, on the same machine NAA works fine on Win Server 2019. My lan range 192.168.1.1/255 Subnet 255.255.255.0 with DHCP

 

this is the result of the command ifconfing:

[Miska]

2 hours ago, madman73 said:

Yes, on the same machine NAA works fine on Win Server 2019. My lan range 192.168.1.1/255 Subnet 255.255.255.0 with DHCP

 

this is the result of the command ifconfing:

 

Looks like the ethernet is not up at all. Either network interface is not detected or configuration is not succeeding. Totally lacking interface from the list is usually indication of former.

 

[madman73]

14 hours ago, Miska said:

 

Looks like the ethernet is not up at all. Either network interface is not detected or configuration is not succeeding. Totally lacking interface from the list is usually indication of former.

 

Maybe i need some driver? The adpater is a Marvell Yukon 88E8059, i found a package for Kernel Linux 2.6.x here https://www.marvell.com/support/downloads/driverSearchResults.do# . Can i use it? and how i install it?

[madman73]

@Miska i've tried to install the driver as in the driver's readme file, without success. I always get the message "No such file or directory", trying the tar command. 

 

But also i've unpacked the tar file using 7zip on windows and copied the folder DriverInstall trying to launch directly the file install.sh, with the same result.

 

Probably you'll have to include the driver in the 32bit image....

 

[Miska]

1 hour ago, madman73 said:

@Miska i've tried to install the driver as in the driver's readme file, without success. I always get the message "No such file or directory", trying the tar command. 

 

But also i've unpacked the tar file using 7zip on windows and copied the folder DriverInstall trying to launch directly the file install.sh, with the same result.

 

Probably you'll have to include the driver in the 32bit image....

 

I think it is better that you move over to some standard Linux distribution like Debian or Fedora. You can install either one as minimal installation.

 

[madman73]

On 11/2/2019 at 2:51 PM, Miska said:

 

I think it is better that you move over to some standard Linux distribution like Debian or Fedora. You can install either one as minimal installation.

 

i've solved using this image. Thank you for the support.

[Miska]

There are now new bootable NAA images for both RasPi3 and RasPi4.

 

[sjg]

Thank you for the new Raspberry Pi images.  I have the NAA installed on my RPi4 and am trying out HQPlayer in my main audio system.  Is there any documentation for the NAA beyond what is in the manual for HQPlayer?

 

How do you control the NAA for simple functions like shutting it off?  It asks for login - I could not find user/password.  I did a shutdown from root but that requires having the NAA connected to a keyboard and screen.  Is there any way to do this headless?  Also, I have installed on my RPi4 a nifty "Remote Pi" board - on/off switch and remote interface - connects to the GPIO by MSLdigital.  Is there a way I can modify the NAA system to incorporate one of the scripts MSL provides for incorporating their hardware?

https://www.msldigital.com/collections/all-products/products/remotepi-board-for-pi-4-b

https://www.msldigital.com/pages/support-for-remotepi-board-plus-2015 (scroll down for examples of scripts)

 

I am not at all proficient in linux but can follow instructions.

 

thanks again!

 

[Miska]

12 hours ago, sjg said:

How do you control the NAA for simple functions like shutting it off?  It asks for login - I could not find user/password.

 

You can just turn it off. If it goes bad at some point (unlikely), you can just reflash the microSD again.

 

On PC hardware you can initiate proper shutdown by short press of a power button. On ARM, there's no standard for such. Alternatively you can login as root and run shutdown.

 

12 hours ago, sjg said:

Also, I have installed on my RPi4 a nifty "Remote Pi" board - on/off switch and remote interface - connects to the GPIO by MSLdigital.  Is there a way I can modify the NAA system to incorporate one of the scripts MSL provides for incorporating their hardware?

 

Unfortunately there's no standard for such on ARM, so either you can modify my image, or alternatively build NAA out of Debian Buster.

 

I have my RasPi's in HifiBerry steel case, no power button, I've been just pulling the power cord...

 

 

P.S. Note that my OS images are 64-bit, while many run 32-bit OS on RasPi. So they are quite different.

 

[randytsuch]

I shut off my hqplayer pc because I figure its kind of a power hog, but pi's only take a little power so I normally let them run 24/7, unless I'm gone for a while.

 

You have a couple other options for an NAA on a pi.

The instructions below should work, if you start with buster lite, to make a buster based naa.

 

Or you can run dietpi.  It supports NAA, and is pretty easy to setup for an NAA.

Then add a shutdown switch to either one.

 

 

1) Install latest OS updates

sudo apt-get update

sudo apt-get -y dist-upgrade

2) Install necessary dependencies (alsa-utils is optional, but the utilities are helpful sometimes). I'm not sure you need to do this, seems like they were already there

sudo apt-get install libasound2 alsa-utils

3) Download the latest networkaudiod deb package for armhf architecture using “wget”. You should go to https://www.signalyst.eu/bins/naa/linux/stretch/

and see if there is a new version. As of Oct 20,2019, this is latest.

wget  https://www.signalyst.eu/bins/naa/linux/stretch/networkaudiod_3.6.0-42_armhf.deb

4) Install the package (correct the version number to what ever is latest at the time)

sudo dpkg -i networkaudiod_3.6.0-42_armhf.deb

[sjg]

Thank you Miska and randytsuch for the guidance and suggestions! 

 

@Miska FYI NAA works on RPi4 - USB Audio In to Oppo 105 universal player.

 

BTW - Is it possible to run the HQPlayer Client on a second Raspberry Pi? 

 

 

[Miska]

11 minutes ago, sjg said:

BTW - Is it possible to run the HQPlayer Client on a second Raspberry Pi? 

 

I have not made any ARM build of the HQPlayer Client yet. I just haven't expected anybody needing such...

 

Technically should be possible to build it for Debian Buster, armhf and arm64 architectures.