Jump to content
4est

HQPlayer's Network Audio Adapter

Rate this topic

Recommended Posts

I can't get my pi2 to work as a NAA.

I tried the images at https://www.signalyst.eu/bins/naa/     

for pi2, and it doesn't seem to run on my pi2.  Ethernet isn't working and display shows a bunch of colors.

I tried both pi2 images.

 

I tried dietpi, loading naa from within dietpi, but systemctl status always shows errors.  And Hqplayer log says hqplayer cant' find a naa.

 

So then I setup buster lite, installed naa, and basically get same results as dietpi.

 

So I tried this, and get "Segmentation fault"

[email protected]:~ $ sudo systemctl stop networkaudiod

[email protected]:~ $ /usr/sbin/networkaudiod

Segmentation fault

 

So can anybody tell me what's going wrong?

Can I use pi and buster?

I thought the precanned images would be easy, but for whatever reason they aren't working for me.

 

Thanks

Randy

Share this post


Link to post
Share on other sites

I tried loading stretch lite, and have the same problem

 

I see this at the end of the pi syslog

Aug 30 05:32:49 raspberrypi systemd[1]: Started Network Audio Adapter daemon.

Aug 30 05:32:49 raspberrypi systemd[1]: networkaudiod.service: Main process exited, code=killed, status=11/SEGV

Aug 30 05:32:49 raspberrypi systemd[1]: networkaudiod.service: Unit entered failed state.

Aug 30 05:32:49 raspberrypi systemd[1]: networkaudiod.service: Failed with result 'signal'.

Aug 30 05:32:51 raspberrypi systemd[1]: networkaudiod.service: Service hold-off time over, scheduling restart.

Share this post


Link to post
Share on other sites
1 hour ago, Miska said:

I recommend upgrading to Pi3 for many reasons. Or soon to Pi4. I dropped support for Pi2 since newer models are better.

 

Ok, thanks for the response

I had decided to try a pi3.  Loaded it with the 64bit pi3 image, and it boots up, and networkaudiod is running now.

Hqplayer still doesn't see a NAA, but I ran out of time to try things this morning so that's for after work.

Share this post


Link to post
Share on other sites

To follow up my last post, I'm using DietPi on a Pi3, and its working fine as an NAA.

Also playing with an Allo Sparky SBC, also running DietPi, and it is also working as an NAA.

I'm using a cheap USB dac for testing, next step is to get a better DAC in there.

Share this post


Link to post
Share on other sites

I am running the HQPlayer OS image on an Innous Statement with the HQplayerd service disabled. (i.e. Statement is functioning as an NAA endpoint) I am streaming to it via a windows based HQplayer Desktop (v4). Everything works great but after every 2-3 songs it pauses playback for approx 5 seconds and then continues. 

 

Could it be a buffering issue? Would appreciate any advise.

Share this post


Link to post
Share on other sites
On 9/4/2019 at 9:34 PM, baconbrain said:

I am running the HQPlayer OS image on an Innous Statement with the HQplayerd service disabled. (i.e. Statement is functioning as an NAA endpoint) I am streaming to it via a windows based HQplayer Desktop (v4). Everything works great but after every 2-3 songs it pauses playback for approx 5 seconds and then continues. 

 

Could it be a buffering issue? Would appreciate any advise.

 

That's quite long pause. It would be good to check if HQPlayer log has any indication about this, or NAA side after that happens (with "systemctl status networkaudiod").

 


Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Share this post


Link to post
Share on other sites

Hi All,

 

I wanted to ask for any tips in regards to HQPlayer and keeping the connection with NAA on my Allo USBridge.

 

Before I explain a bit more, here is some detail on my set up. I have a NUC running my Roon Core and HQPlayer, it connects to a Netgear 16 port unmanaged switch (GS116UK), before going off around my house via Ethernet cable. The music is stored on a Synology DS918+ NAS, connected to the same switch (both NUC and NAS in a cupboard, squirrelled away). In my main lounge set-up, the Ethernet cable connects into another GS116UK before connecting to my USBridge. The USBridge feeds a Mytek Liberty DAC, and I usually upscale to DSD 256, it sounds great. The USBridge is on the latest version, 6.23.3. I only have Roon Bridge and NAA enabled via the Allo webpage. I am in the UK and have a BT Smart Hub 2, I believe this is a DHCP only router and this connects to the same switch my USBridge connects too.

 

Anyway, I have discussed this issue before across on the Roon forums (including discussing it with Jussi/Miska) but I have not been able to solve it. Basically, if I start my equipment up in a particular order (I have tried all the combinations), then occasionally HQPlayer with 'see' the NAA on the USBridge. When this happens I generally leave well alone and don't turn anything off, however all my kit (NUC, NAS etc) is in a cupboard in the spare bedroom and can be noisy overnight and so when we have guests I have to turn it off. Whenever this happens its a right pain trying to get HQPlayer to 'see' the NAA on the USBridge again, and to get that connection back I have to turn equipment off and on and I am yet to hit on the right combination which is repeatable. Sometimes, I have got it to work after a power-cut where everything is turned off, sometimes when I turn on the DAC, then Bridge, then the NUC, but nothing works every time.

 

So, I think the problem is somewhere in my network infrastructure, rather than with HQPlayer, but I am not sure how to solve the problem. Has anyone had a similar issue that they have been able to solve?

 

Any thoughts welcome? I tried posting across on the USBridge thread, but no luck unfortunately.

Thanks.

Share this post


Link to post
Share on other sites

Based on your description, there shouldn't be a problem if you power down/up the NUC that has HQPlayer and Roon.

 

When you power up everything from cold, I'd recommend to start from the DAC towards the HQPlayer machine. So first DAC, then NAA, and then HQPlayer NUC.

 

NUC is running Windows? If that's the case, please check that it doesn't have any extra network interfaces enabled, apart from the one connecting to the home network switch.

 


Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Share this post


Link to post
Share on other sites

Thanks @Miska. Yes the machine is windows 10. I usually try to boot up in the order you suggest. The most reliable methodology in this particular case, is to switch off, then on, the DAC, streamer, local switch and home router at the same time and then to power up the NUC (i don't touch the switch it is on). I have tried lots of other combinations, but this seems to be the most repeatable. 

 

I will double-check the NUC network interface.

Share this post


Link to post
Share on other sites
1 minute ago, rossco said:

Thanks @Miska. Yes the machine is windows 10. I usually try to boot up in the order you suggest. The most reliable methodology in this particular case, is to switch off, then on, the DAC, streamer, local switch and home router at the same time and then to power up the NUC (i don't touch the switch it is on). I have tried lots of other combinations, but this seems to be the most repeatable. 

 

I will double-check the NUC network interface.

 

I'm assuming switches and routers are never turned off. These always need to be powered up before anything else. If the router ever becomes powered off and you have dynamic IP's through DHCP assigned by the router, it's lease table is probably reset. In such case it is best to reboot everything on the network. Otherwise there is potential problem of some device's IP changing on the fly through lease renewal and that will likely cause various problems for applications that have longer persistent connections.

 


Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Share this post


Link to post
Share on other sites
On 9/7/2019 at 2:31 PM, Miska said:

 

That's quite long pause. It would be good to check if HQPlayer log has any indication about this, or NAA side after that happens (with "systemctl status networkaudiod").

 

Thx, but where do I fing the HQPlayer Log file on a Windows 10 Machine? I looked through the Signalyst Folder (in Program Files) but couldn‘t find anything which resembled a log file ... ☺️

Share this post


Link to post
Share on other sites
6 minutes ago, baconbrain said:

Thx, but where do I fing the HQPlayer Log file on a Windows 10 Machine? I looked through the Signalyst Folder (in Program Files) but couldn‘t find anything which resembled a log file ... ☺️

 

This is documented in the manual's "Troubleshooting" section. On Windows you can find the same log file in "%LOCALAPPDATA%\HQPlayer" folder. On Unix systems like macOS and Linux it is in the same place at "~/.hqplayer".

 


Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Share this post


Link to post
Share on other sites

Hi @Miska

 

I am running naa-355-cubox-i on a Cubox i2 which is wired to the network switch.

Is it possible to enable wi-fi in your NAA image and make it "discoverable" to HQP Desktop?

 

Thanks,

Ricardo


"Science draws the wave, poetry fills it with water" Teixeira Pascoaes

Share this post


Link to post
Share on other sites
1 hour ago, Miska said:

 

My images are supposed to be configuration free, and that's why they generally don't support WiFi. If you want WiFi or other things not found on the images, it is better to install Debian and the Debian package instead. This way NAA image stays minimal and you get maximum flexibility if needed through Debian.

 

 

I see. I thought it might just requiring adding a few lines or something, like when enabling the HiFiBerry.

 

Thanks


"Science draws the wave, poetry fills it with water" Teixeira Pascoaes

Share this post


Link to post
Share on other sites
3 hours ago, semente said:

I see. I thought it might just requiring adding a few lines or something, like when enabling the HiFiBerry.

 

It needs additional software and you need to configure SSID and passphrase... That means using text editor on a console in this kind of minimal image. HQPlayer OS has WiFi support included, but I'm not sure if anybody has ever used it.

 


Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Share this post


Link to post
Share on other sites
23 hours ago, Miska said:

 

This is documented in the manual's "Troubleshooting" section. On Windows you can find the same log file in "%LOCALAPPDATA%\HQPlayer" folder. On Unix systems like macOS and Linux it is in the same place at "~/.hqplayer".

 

Thx for the guidance, will take a look at the log file and let you know.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...