Help with setting up HQPlayer for Merging Technologies NADAC+Player

13 hours ago, pt999 said:

I have disabled all devices in Roon Settings Audio except for HQPlayer.  Both Roon and NADAC are showing DSD256, but still no sound.  My Roon server PC is currently in a different room from the music room with NADAC.  Tomorrow night I will move the Roon PC, monitor/keyboard to connect directly to the NADAC as suggested.  Thank you everyone.

Phuong

 

I highly recommend simplifying the test. 

First: View the log in ANEMAN, so you can see more info about what's going on. 

Second: Click the red exclamation in aneman, it will tell you specifics.

Third: Try to send only from HQPlayer's interface to the NADAC. This will rule out an issue with Roon and HQP. 

Fourth: If the above works, then move to Roon sending to HQP. 

Thank you for the suggestions. Since I have now disabled ALSA (NADAC Player), I will reload the latest Aneman. I don't see the red exclamation button on the older Aneman. I'll play something from HQPlayer directly to ASIO and read the logs. I will also move the Roon PC into the music room to connect directly to the NADAC.

15 hours ago, pt999 said:

I have disabled all devices in Roon Settings Audio except for HQPlayer.  Both Roon and NADAC are showing DSD256, but still no sound.  My Roon server PC is currently in a different room from the music room with NADAC.  Tomorrow night I will move the Roon PC, monitor/keyboard to connect directly to the NADAC as suggested.  Thank you everyone.

Phuong

 

Red there in ANEMAN indicates some error situation. You should be able to see the error from ANEMAN. I guess there is sone sync issue going on between the devices. If you are on your home network, with WiFi, and you are trying to use multicast instead of unicast link, it is likely not going to work. Typically entire network would get jammed. So if you are on regular home network, only use unicast bindings in ANEMAN.

The older version of Aneman (used to disable ALSA NADAC Player internal Roon server) didn't give me a choice for Unicast, so tonight I'll load back the newest version to enable Unicast and check the logs. My whole house is hard wired with Ethernet so I don't use WiFi except for phones and tablets.

25 minutes ago, pt999 said:

The older version of Aneman (used to disable ALSA NADAC Player internal Roon server) didn't give me a choice for Unicast, so tonight I'll load back the newest version to enable Unicast and check the logs. My whole house is hard wired with Ethernet so I don't use WiFi except for phones and tablets.

You don't need to be using WiFi for audio, but if you have WiFi available on the same network, then that is covered by the multicast as well. And it could be banging the WiFi network with multicast as well. So just existence of WiFi in the same network segment is enough to have things messed up.

I moved the Roon PC next to the NADAC+Player.  The connection is:  Google 1G Fiber modem -> Trendnet unmanaged switch -> Cat6 -> Roon PC -> Cat7 -> NADAC+Player.

I reinstalled latest Aneman 1.6.0, reset NADAC to factory default, did MAD restart server in ASIO settings.  Set up ASIO & NADAC to same sampling rate 352.8Khz.  When I use Aneman to establish connection, it doesn't give me the option to choose Unicast, only Multicast. Aneman reports 1 error on ASIO: Wrong latency setting, and 1 error on NADAC: 48v power error.  May be something is wrong with my NADAC.  I've been playing music with internal NADAC Roon server/client for a long time and didn't notice anything wrong.

I connect using multicast and use HQPlayer client to play something, but play back would not start. I closed HQPlayer, started Roon client and play something, play back would not start. 

Using multicast, input, output, streaming seems to be going. The Nadac 48v error may be the issue.

8 hours ago, pt999 said:

I reinstalled latest Aneman 1.6.0, reset NADAC to factory default, did MAD restart server in ASIO settings.

You need the older version of ANEMAN to disconnect ALSA LKM and NADAC first then connect your NADAC to MAD.

8 hours ago, pt999 said:

Wrong latency setting

Please verify you’ve selected 64 frames on MAD and NADAC.

I did use the older version of Aneman to disconnect and clear all connections before installing the new version. I could see all 3 devices without any lines connecting them. Once the newer version is loaded, I only see 2 devices. But I don't see the option to select Unicast even in the newest Aneman. I also went into the ALSA webpage to clear all Sources/sinks to make sure ALSA is not connected to anything.

I have not checked the 64 frame delay, I didn't know which variable to adjust latency. I'll check again tonight after work. Thanks again.

5 hours ago, pt999 said:

But I don't see the option to select Unicast even in the newest Aneman.

Pelase forget about the unicast / multicast now. Make sound first.😉 Although I suggest to use unicast mode but in fact both can work for this kind of situation. In advance page you can change multicast to unicast just a checkbox thereafter. So just stay with older version of ANEMAN.

It also may not hurt to just get 24/44.1 working, to rule out other possible issues. 

I rolled back Aneman to an older version.  Set Roon to output 24/44.1. Select 64 frames for MAD and NADAC.  There's only 1 error in Aneman:  ASIO Clock: wrong latency setting Error.

Still no sound yet; it feels so close.

4 hours ago, pt999 said:

ASIO Clock: wrong latency setting

On MAD, switch mode to NADAC and see how's going.

I switched to NADAC on MAD panel, tried all 3 settings for ASIO: default, Merging Audio Device, HQPlayer5Desktop, still got the "Device ASIO (on Desktop-R0NTM7T) ASIO Clock: wrong latency setting Error." I set HQPlayer PCM to 44.1, matched all sample rates at 44.1, but on ASIO web page, the Session Sources Frame size (samples) changed to 1536 and it's grey out so I couldn't change it to 64. There's only one error left on Aneman: wrong latency setting error. I couldn't figure out how to match the latency.

2 hours ago, pt999 said:

the Session Sources Frame size (samples) changed to 1536 and it's grey out so I couldn't change it to 64.

The latency set to 64 is on MAD, not Advanced page.