Jump to content
IGNORED

HQPlayer-desktop.exe has stopped working


Recommended Posts

Here are the content of my log file:

 

 


* 2017/04/26 14:17:55 Starting...
  2017/04/26 14:17:55 Signalyst HQPlayer Desktop v3.16.1
  2017/04/26 14:17:55 Engine selected: 
* 2017/04/26 14:17:55 Control server started
  2017/04/26 14:17:59 Restore GUI state
  2017/04/26 14:17:59 libDSP version 18.4.2
  2017/04/26 14:17:59 Number of processor cores: 4
  2017/04/26 14:17:59 DSP thread pools disabled
  2017/04/26 14:17:59 Pipelined DSP enabled
  2017/04/26 14:17:59 Audio engine: network
  2017/04/26 14:17:59 Network Audio IPv6 support disabled
  2017/04/26 14:17:59 Discovery from 0.0.0.0
  2017/04/26 14:18:00 Discovered 0 Network Audio Adapters
  2017/04/26 14:18:00 Set channels: 2 (2)
! 2017/04/26 14:18:00 createEngine(): clHQPlayerEngine::Initialize(): clNetMiniEngine::Initialize(): adapter not found
& 2017/04/26 14:18:02 Playlist save: C:\Users\chris\AppData\Local\HQPlayer\current.m3u8
- 2017/04/26 14:18:02 Network engine stopping...
  2017/04/26 14:18:02 Network Audio IPv6 support disabled
  2017/04/26 14:18:02 Discovery from 0.0.0.0
- 2017/04/26 14:18:08 Network engine stopping...
  2017/04/26 14:18:08 libDSP version 18.4.2
  2017/04/26 14:18:08 Number of processor cores: 4
  2017/04/26 14:18:08 DSP thread pools disabled
  2017/04/26 14:18:08 Pipelined DSP enabled
  2017/04/26 14:18:08 Audio engine: network
  2017/04/26 14:18:08 Network Audio IPv6 support disabled
  2017/04/26 14:18:08 Discovery from 0.0.0.0
  2017/04/26 14:18:09 Discovered 0 Network Audio Adapters
  2017/04/26 14:18:09 Set channels: 2 (2)
- 2017/04/26 14:18:09 Network engine stopping...
! 2017/04/26 14:18:09 clMainWindow::settingsTriggered(): clMainWindow::reinitEngine(): clHQPlayerEngine::Initialize(): clNetMiniEngine::Initialize(): adapter not found
 

Founder of Audiophile Style | My Audio Systems AudiophileStyleStickerWhite2.0.png AudiophileStyleStickerWhite7.1.4.png

Link to comment

Sometimes I've heard about this but never before managed to reproduce it. But now I figured out that if the forced settings dialog is canceled without selecting device and then the network naming dialog (for changing NAA's name when it's running on Linux) is opened it crashes due to null pointer. Unexpected situation... But I added a check for this case and it won't crash anymore in next release.

 

The problem you have is that no NAA's can be found...

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
Just now, Miska said:

Sometimes I've heard about this but never before managed to reproduce it. But now I figured out that if the forced settings dialog is canceled without selecting device and then the network naming dialog (for changing NAA's name when it's running on Linux) is opened it crashes due to null pointer. Unexpected situation... But I added a check for this case and it won't crash anymore in next release.

 

The problem you have is that no NAA's can be found...

 

 

Yes. This is indeed the issue. 

 

Now to figure out why both of my NAAs can't be found :~(

Founder of Audiophile Style | My Audio Systems AudiophileStyleStickerWhite2.0.png AudiophileStyleStickerWhite7.1.4.png

Link to comment

Usually either firewall blocking the traffic, or something in the network blocking multicast traffic (switch/router/accesspoint).

 

Depending on type of your NAA, you can check if it sees the HQPlayer's discovery message, it will print out reports of such... If it reports receiving the discovery, then just the response is lost on the way back (incoming traffic back to HQPlayer).

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment

This is strange. 

 

UPnP, Ravenna, and RoonReady devices work fine. When I switch to NAA on both the microRendu and the sMS-200, the devices can't be discovered by HQP. 

 

I checked the firewall because that's what I thought as well. HQP is listed as Allow. 

 

I haven't changed anything on the network. In fact I'm using a really good network from Access Networks and I don't even have the passwords to get in. It used to work, now it doesn't. Hmmm.

 

One thing that changed was this Windows update - https://support.microsoft.com/en-us/help/3150513/latest-compatibility-definition-update-for-windows

Founder of Audiophile Style | My Audio Systems AudiophileStyleStickerWhite2.0.png AudiophileStyleStickerWhite7.1.4.png

Link to comment
17 minutes ago, Miska said:

Usually either firewall blocking the traffic, or something in the network blocking multicast traffic (switch/router/accesspoint).

 

Depending on type of your NAA, you can check if it sees the HQPlayer's discovery message, it will print out reports of such... If it reports receiving the discovery, then just the response is lost on the way back (incoming traffic back to HQPlayer).

 

Is there a command line utility on the NAA that will show me the messages?

Founder of Audiophile Style | My Audio Systems AudiophileStyleStickerWhite2.0.png AudiophileStyleStickerWhite7.1.4.png

Link to comment
21 minutes ago, The Computer Audiophile said:

 

Is there a command line utility on the NAA that will show me the messages?

 

If it is Ubuntu or Debian based with my packaging, first check if the service is running using "sudo systemctl status networkaudiod". You can enable/disable the service with "sudo systemctl enable networkaudiod" or "sudo systemctl disable networkaudiod". This controls whether it is started at boot time. Note that if GUI desktop is installed, by default network configuration is managed by NetworkManager and thus it is not up at boot time so starting the service will fail. Configuring network through /etc/network/interfaces file helps on this front - this is the default way on GUI-less Ubuntu Server or Debian. You can start networkaudiod manually with "sudo systemctl start networkaudiod" and stop with "sudo systemctl stop networkaudiod".

 

To see log output, first stop the background service and then start it manually with just "networkaudiod" command on console/terminal.

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment
  • 2 weeks later...

Hello Miska, love HQPlayer but I'm running into a similar problem as our founder here. Today (5/10/17) as I try to open HQPlayer I am getting the same "HQPlayer-desktop.exe has stopped working" dialogue box, only in my case the program is not opening at all. I am running Win10 x64 and connect via USB to a Marantz HD-Dac1. Everything has been running great for months, however Windows did update for me last night (5/9/17). I'm guessing something in this update broke me. Any chance you can help me out?

Link to comment
1 hour ago, Stoneleaf said:

Hello Miska, love HQPlayer but I'm running into a similar problem as our founder here. Today (5/10/17) as I try to open HQPlayer I am getting the same "HQPlayer-desktop.exe has stopped working" dialogue box, only in my case the program is not opening at all. I am running Win10 x64 and connect via USB to a Marantz HD-Dac1. Everything has been running great for months, however Windows did update for me last night (5/9/17). I'm guessing something in this update broke me. Any chance you can help me out?

 

Please see here:

 

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment

Hello,

Windows 10 Pro (x64) with KB4019472 installed: Please install the 32 bit version of HQPlayer 3.16.1 and you may have no trouble.

This solves also the problem on Windows 10 Build 16188 (latest Insider build).

Best regards

Wolft

Link to comment

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...