HQPlayer's Network Audio Adapter

[Miska]

I closed all other players and rebooted the NAA machine.

 

"aplay -l" shows "no soundcards found".

 

If "aplay -l" doesn't show the card, you have problem with ALSA or someone is keeping the device busy. When "aplay -l" begins to show it, it should also start appearing through networkaudiod.

 

However, the OS system page shows PCH as card 0 and the Amanero as card 1/usb device 0. Also, "cat \proc\asound\cards" does show the Amanero.

 

This sounds like you have a GUI in your NAA machine. You shouldn't have any GUI, only text console. If you have a GUI, you also likely have "pulseaudio" installed and running and that is a big steaming pile of **** similar to CoreAudio and Windows mixer/rate converter audio engines. You need to make sure pulseaudio doesn't mess with the device, at least by modifying it's configuration or preferably removing it from the system altogether.

[bodiebill]

If "aplay -l" doesn't show the card, you have problem with ALSA or someone is keeping the device busy. When "aplay -l" begins to show it, it should also start appearing through networkaudiod.

 

This sounds like you have a GUI in your NAA machine. You shouldn't have any GUI, only text console. If you have a GUI, you also likely have "pulseaudio" installed and running and that is a big steaming pile of **** similar to CoreAudio and Windows mixer/rate converter audio engines. You need to make sure pulseaudio doesn't mess with the device, at least by modifying it's configuration or preferably removing it from the system altogether.

 

Today I made a fresh start and it worked: HQP now connects to NAA (after applying the IP6 tweak) and recognizes the DAC. Thanks, Miska!

 

My NAA machine runs on snake oil – and no I am not joking:

 

Snakeoil OS - Linux OS For The Audiophile

 

It is a very minimal ubuntu distribution. I think I like it, and have asked the developer to react to your comment on pulseaudio.

[juliocat]

Today I made a fresh start and it worked: HQP now connects to NAA (after applying the IP6 tweak) and recognizes the DAC. Thanks, Miska!

 

My NAA machine runs on snake oil – and no I am not joking:

 

Snakeoil OS - Linux OS For The Audiophile

 

It is a very minimal ubuntu distribution. I think I like it, and have asked the developer to react to your comment on pulseaudio.

 

Hello bodiebill

I'm using snake oil too, and HQPlayer can't see my NAA, what is the IP& tweak you mention??

[bodiebill]

Hello bodiebill

I'm using snake oil too, and HQPlayer can't see my NAA, what is the IP& tweak you mention??

 

Hi juliocat, see Miska's post #1972 in this thread. The Snakeoil developer will solve this in his next release.

[bibo01]

What is the command to make NAD 3.4 start without IP6?

[bibo01]

What is the command to make NAD 3.4 start without IP6?

 

I got it - Thank you.

[scan80269]

I installed the newly available HQPlayer 3.14.0 today, and tried both Raspberry Pi3 and Beaglebone Black as NAA with the pre-built images, and did not encounter the above issue, so it looks like it's fixed.

 

The issue of HQP not detecting a BBB NAA after stopping playback has hit me today a total of 4 times. Not sure why I did not encounter this previously, but it's now very repeatable.

 

With this, I'll likely keep using my Pi2 or Pi3 as NAA along with my favorite: microRendu, and leave my BBB to be something other than NAA.

[bodiebill]

This sounds like you have a GUI in your NAA machine. You shouldn't have any GUI, only text console. If you have a GUI, you also likely have "pulseaudio" installed and running and that is a big steaming pile of **** similar to CoreAudio and Windows mixer/rate converter audio engines. You need to make sure pulseaudio doesn't mess with the device, at least by modifying it's configuration or preferably removing it from the system altogether.

 

Reply from Snakeoil developer:

 

Snakeoil by default runs only in console mode. There is only one console (tty1) and you can even disable that in the Snakeoil tab.

The only exception is when one needs to run a GUI music player (e.g. JRiver), where a virtual desktop is used.

 

PCH could well be the on board sound card on your motherboard. You should be able to disable Intel HD audio or Azalia codec (PCH may call this something else now though) in your system's BIOS and. Once disabled this audio and that audio card will not show up in the list.

 

Pulseaudio is not included in the Snakeoil distro for precisely the reasons Laako stated. By default most players will access the audio using direct hardware access (i.e. something like hw:0,0). Of course expert users can always tweak the OS to route the audio via something else.

[Miska]

Reply from Snakeoil developer:

 

OK, in that case, if the device doesn't show up in "aplay -l" then some other running process is keeping it reserved.

[Jud]

The issue of HQP not detecting a BBB NAA after stopping playback has hit me today a total of 4 times. Not sure why I did not encounter this previously, but it's now very repeatable.

 

With this, I'll likely keep using my Pi2 or Pi3 as NAA along with my favorite: microRendu, and leave my BBB to be something other than NAA.

 

I experienced this with BBxM. Perhaps there's something about the Beagle hardware or the Debian installation on them that causes it.

 

Miska had asked me a while back for the NAA info from Linux and the HQPlayer log so he could look into this, but I went on vacation and since I came back I've been using the Cubox that doesn't have the problem.

[Jud]

By the way, I had wanted to mention:

 

I had been able to run HQPlayer on my desktop to upsample to DSD256, though with occasional stuttering. At some point during the betas DSD256 became impossible (constant stuttering), but I was able to play DSD128 with occasional stuttering. Then a couple of weeks ago (around betas 7 and 8), the ability to play DSD256 came back.

 

I wanted to see what was causing the stuttering, so I connected my main system DAC to the desktop and got the same result as with the NAA, so it wasn't the network.

 

I then remembered "de-overclocking" my desktop a year or so ago to try to get the best sound from the desktop system. Of course with an NAA this isn't a consideration. So I re-overclocked the 2009 vintage i7-950 CPU (from 3.07 to 3.7GHz), and now I'm able to upsample to DSD 256 and listen to music with almost no stuttering - two occasions in over an hour of listening last night. (I imagine this may be caused by something the OS is automatically running from time to time - perhaps I'll get around to looking into it.) The music is sounding very nice indeed.

 

So if you have gone the fairly popular route of making sure your system is very quiet, remember this is not quite such a consideration when an NAA is used. Consider the possibility of maximizing your CPU speed for best capability of running HQPlayer.

[semente]

I am using a 1 Ampere LPSU to feed the Raspberry Pi 3 and the HifiBerry DAC Pro +.

Is this too short?

 

R

[juliocat]

I am using a 1 Ampere LPSU to feed the Raspberry Pi 3 and the HifiBerry DAC Pro +.

Is this too short?

 

R

 

5 Volt 2.5 Amps is recommended

[Miska]

I experienced this with BBxM. Perhaps there's something about the Beagle hardware or the Debian installation on them that causes it.

 

Miska had asked me a while back for the NAA info from Linux and the HQPlayer log so he could look into this, but I went on vacation and since I came back I've been using the Cubox that doesn't have the problem.

 

Debian Stretch is pretty much moving target (since it's Debian's testing-branch), getting lot of updates all the time. So it makes sense to check again every now and then.

 

What I've tested, also the plain NAA image I provide seem to work fine for me. It is not using Debian.

[juliocat]

I just installed debian stretch in my Brix Celeron mini PC with NAA and works and sounds great, but i guest if i can install a low latency kernel, but i can't find one for debian stretch, did somebody knows of one??

[tboooe]

I just installed debian stretch in my Brix Celeron mini PC with NAA and works and sounds great, but i guest if i can install a low latency kernel, but i can't find one for debian stretch, did somebody knows of one??

Not sure if this would work with NAA but what about AudioLinux? Its supposed to be based on a real time kernel. I've been thinking about using this on my main audio pc running HQP. It would be great AudioLinux would also work with NAA.

[Miska]

I just installed debian stretch in my Brix Celeron mini PC with NAA and works and sounds great, but i guest if i can install a low latency kernel, but i can't find one for debian stretch, did somebody knows of one??

 

Debian has realtime kernel instead of lowlatency kernel. Occasionally it disappears from the repository and then comes back later. And it may crash or not work on some machines, at least recently. So it is sort of work-in-progress. But as long as you keep the default kernel installed too, you can choose the one you want to boot in bootloader menu.

[lmitche]

Yes, Audiolinux supports the NAA with the realtime kernel.

 

 

Sent from my iPad using Computer Audiophile

[ds2k]

The issue of HQP not detecting a BBB NAA after stopping playback has hit me today a total of 4 times. Not sure why I did not encounter this previously, but it's now very repeatable.

 

With this, I'll likely keep using my Pi2 or Pi3 as NAA along with my favorite: microRendu, and leave my BBB to be something other than NAA.

 

I experienced same issue with NAA image for BBB, with newest released of HQPlayer Desktop, and previous version too.

 

 

Sent from my iPhone using Tapatalk

[bodiebill]

HQP discovers my NAA without a problem: the IP address of the NAA machine shows up and I can select NAA in the settings. Both HQP and NAA are on Windows PC's.

 

However, the only option to choose from is JPLAY. MY Combo384 Amanero DAC which is active on the NAA PC is not recognized by HQP.

 

When I connect my DAC directly to the HQP PC, there is no problem: it is recognized.

And when startup my NAA machine with Linux (Ubuntu) instead of Windows, the DAC is recognized also.

 

Any idea why HQP refuses to see my DAC when it is on the Windows NAA PC?

[tboooe]

HQP discovers my NAA without a problem: the IP address of the NAA machine shows up and I can select NAA in the settings. Both HQP and NAA are on Windows PC's.

 

However, the only option to choose from is JPLAY. MY Combo384 Amanero DAC which is active on the NAA PC is not recognized by HQP.

 

When I connect my DAC directly to the HQP PC, there is no problem: it is recognized.

And when startup my NAA machine with Linux (Ubuntu) instead of Windows, the DAC is recognized also.

 

Any idea why HQP refuses to see my DAC when it is on the Windows NAA PC?

 

I had the same issue. What worked for me was to simply unplug and replug the usb cable. Also, you may want to uninstall JPLAY. BTW, can you select JPLAY in HQP, then in JPLAY select your DAC?

[bodiebill]

BTW, can you select JPLAY in HQP, then in JPLAY select your DAC?

 

Thanks, yes I can.

 

And when I uninstall JPLAY on the NAA PC, the DAC is still not recognized: nothing to choose from.

 

This is the NAA log:

 

[C:\Program Files\NAAx64\networkaudiod.exe] (2044): networkaudiod Copyright © 2011-2016 Jus

ights reserved.

[C:\Program Files\NAAx64\networkaudiod.exe] (2044): ASIO Technology by Steinberg Media Techno

[C:\Program Files\NAAx64\networkaudiod.exe] (2044): discovery from [::ffff:192.168.1.201]:516

[C:\Program Files\NAAx64\networkaudiod.exe] (2044): connection from [::ffff:192.168.1.201]:55

[C:\Program Files\NAAx64\networkaudiod.exe] (2044): protocol error: clASIOMiniEngine:: DeviceLookup(): lDrivs < 0

[C:\Program Files\NAAx64\networkaudiod.exe] (2044): begin disconnection

[C:\Program Files\NAAx64\networkaudiod.exe] (2044): disconnected [::ffff:192.168.1.201]:55704

[Miska]

And when I uninstall JPLAY on the NAA PC, the DAC is still not recognized: nothing to choose from.

 

Does your DAC come with an ASIO driver?

 

[C:\Program Files\NAAx64\networkaudiod.exe] (2044): protocol error: clASIOMiniEngine:: DeviceLookup(): lDrivs < 0

 

Means there are no ASIO drivers found in the system.

[Miska]

Any idea why HQP refuses to see my DAC when it is on the Windows NAA PC?

 

You need to make sure you have Amanero ASIO driver installed, and that other applications are not running and keeping the device reserved.

[bodiebill]

You need to make sure you have Amanero ASIO driver installed, and that other applications are not running and keeping the device reserved.

 

Thanks Miska (also for your patience): I un- and re-installed the Amanero drivers on the NAA PC and they are now visible in HQP!