RubenV

After being mailed by Roon stating they will drop the support for HQplayer 3 in the upcoming update, I bought HQPlayer 4 today. Installation was a breeze. I postponed to update to version 4 because I was under the impression that I could not run any EC modulation with my i7 6700K cpu in the control pc. I am currently listening to poly-sinc-short-mp-2s, ASDM7ECv2, SDM, DSD256x48. Even with half the lower DSD rate (256 instead of 512 I used previously) the increase in SQ is nothing short of stunning!

Interesting, I always had the feeling that windows server sounded more clean and purist then the regular windows versions.

Do you rate WS10 above WS2019?

Hi @Rovo Why not going with WS2019 on your control pc? I have a similar setup with Roon and Tidal, but with ws2019 on both the audio pc as control/streamer pc. Ws2019 > WS10

Just got Fidelizer Pro working on my audio pc (NAA only). I am flabbergasted, never could have wish for such a huge upgrade in SQ. Can't wait to " fidelize" my control pc :P

Hi Phil, Thanks for replying I really enjoy the sound of AO3.0 together with ws2019, just fantastic. I only ran audiohpile optimizer and did not change anything in Hqplayer. After running AO and could not select the backend in HQplayer on IPv6 anymore, I enabled this through the registry. I don't know something else could have changed in the meantime while I did not alter any settings? After this edit I could select the proper back end in HQplayer and had sound with AO applied. Never had this kind of SQ in my system, so happy with it Edit: And I was able to compare it with both streamers connected to the switch, and the audio pc connected to the control pc (which has an extra intel gigabit nic) directly obtains a much better sound with my system.

Problem solved, it appears you need to manually enable IPv6 again after running AO. Thanks @tboooe for pointing it out to me.

Hi! After buying AO3.0 I decided to upgrade my audio and control pc from ws2016 to ws2019. After installing the OS on both systems, update all the drivers and install HQPlayer together with NAA, I verified that everything worked properly, sound is coming out of the speakers. (Audio and control pc do not have a direct connection and use the same switch) However, after running AO on the audio pc to start with, HQPlayer can't see NAA so I can't select a device as backend under settings of HQPlayer. I tried to restore all settings and services, but still no sound. I have tried the ultimate mode with as less services disabled as possible but still no sound. I did a new windows installation, without AO and I had sound right away. After this I tried AO but this time on with the expert setting, and again no sound. I have done a lot of AO installations on my systems over the past year (WS2012, 2016 and now 2019) and never encountered any problems with AO. What am I missing?

I have a question regarding the naa setup with dual pc's and a straight connection between the nic of control pc and the nic of the audio pc. When I detach the ethernet cable from the control pc (and leave the direct connection between the control(2nd nic) and audio pc, I am able to select the right NAA backend under IP4. However, as soon as I reconnect the internet cable on the first nic of the control pc, I loose the NAA backend. When I connect both machines only to the switch it does not work at all. Any suggestions I could try?

Does fidelizer 8.4 work with WS2019 in core mode and/or GUI mode?

Hi tbooe, No need to apologize since I just came back from a long holiday. Right now I purchased AO 3.00 and am ready to run ws2019 on both pc's. Could I run the audio pc still in core mode just like ws2016? And before this migration I had no direct ethernet connection between the machines because I could not set it up. However, it did work in the past so I am missing something...

Hi Tboooe, After rearming my license for ws2016 I could not directly connect the HQP to the NAA. I just did a complete new install of the HQP machine with ws2019, and enabled IPv6 on both machines. Unfortunately I can't get this to work. Once I detach the direct cable and connect the NAA to my router, I can select my dac in HQP. I have double checked that IPv6 is working on the NAA and rebooting this not sort it out. Could you please recommend other stept I could take or things I could try?

Hi Miska, Thanks for your reply. Both ethernet controllers that I use for in between the control and audio pc have their own IP-range and subnet mask, and I can ping between both machines without the loss of packages. How can I check if the multicasts are routed to the NAA? Or is there something else I could try?

After re-arming the WS2016 on my control pc and rebooting, somehow HQPlayer can't find the NAA no more. On the "backend" Network AudioAdapter is selected, however the dropdown box of "device" in the option menu remains empty. Normally this will display "default:Combo384" (I use a Lampizator Golden Gate). The connection between the control pc (with dual ethernet ports) is hardwired, directly to the ethernet input of the NAA. How could I check wether the connection is okay or not? Thanks in advance!

Thanks Ted! I will try the instructions when I get home. Would this scenario also work with ws2016 on both machines, taking into account tboooe’s reaction regarding nic’s not being bridgeable in core mode on both systems.