Qwave.dll Windows 10
Kat Guinnip
One thing that just came to my mind... If you are on Windows or Linux, you could try to enable IPv6 only on the interface where you have NAA (unless you need it elsewhere). HQPlayer tries to use IPv6 primarily (remember to enable it in HQPlayer settings) and falls back to IPv4 if it is not available. IPv6 has also nice autoconfiguration, so one doesn't need to have DHCP server on network blocks that use IPv6. However, IPv6 support is disabled on macOS due to the annoying way macOS deals with IPv6 multicast.
@Miska I just want to say I finally got this working!!! I got rid of the Allo Sparky and put back in my Server 2012 R2 based NAA. I enabled IPv6 in the registry (enabling IPv6 using Powershell or netsh didnt work) on both Server PCs, connected the NAA to the HQP PC, restarted, and now I am able to play directly, allowing me to get rid a switch in my system! Fantastic!!! Thank you. Now I am going to compare to see how it sounds compared to having my SG300 Cisco SFP switch in the music chain.
UpTone Audio LPS1.2/IsoRegen, Fiber Switch and FMC, Windows Server 2016 OS, Audiophile Optimizer 3.0, Fidelizer Pro 6, HQ Player, Roonserver, PS Audio P3 AC regenerator, HDPlex 400W ATX & 200W Linear PSU, Light Harmonic Lightspeed Split USB cable, Synergistic Research Tungsten AC power cords, Tara Labs The One speaker cables, Tara Labs The Two Extended with HFX Station IC, Oyaide R1 outlets, Stillpoints Ultra Mini footers, Hi-Fi Tuning fuses, Vicoustic/RealTraps/GIK room treatments
Just graphics driver is enough. The Vision 3D Controller is not needed nor the control center / Nvidia Experience. You can also let it update the Audio Driver, because it is stacked with the graphics driver so non-matching versions could have some trouble co-operating (audio driver is used for HDMI audio output).
Thank you for this post. I was about to upgrade HQP. I am using Server 2016 as well. Were you able to downgrade to the previous version of HQP to resolve the qwave.dll problem? Or can you just copy the dll file into the right location in Windows/system32?
I had no problem of going back to previous version of HQP. I was checking if it's easy way of adding Quality Windows Audio Video Experience feature from powershell. But from what I was reading it's not an easy task in core version. I didn't tried yet to push only dll file but from my previous experience with HQP that will not do because it probably ask for some other files. I will give it a try and report feedback.
I am also in Core mode in Server 2016. Of course, your original question is the important one...why was qwave introduced into the latest version of HQP in the first place? I try to keep my music PCs as lean as possible without too many processes running. I hope there is a good reason for this new requirement in HQP.
It is part of Windows since Vista and Server 2008. Although Windows Server versions have never been supported by HQPlayer (if it just happens to run on such, I don't mind, but performance may suffer). Desktop versions of Windows are optimized for multimedia use. Server versions are optimized for I/O bandwidth which is in direct conflict with requirements of multimedia use.
was playing with convolution filters when a piano track (Beethoven, SACD rip) started overloading with loud "cracks" and amps flashing red ; always occurred at same timing (not even a forte) with whatever filter, including good old one in service for a year, and up to - 16 dB attenuation
None of my Windows installations (8.1 and 10) have complained about that. According to Microsoft's documentation is officially available on desktop since Windows Vista and on server since Windows Server 2008.
There are no code changes around any of the convolution stuff (in a long time). Are you using CUDA? If you are, you could try without because the CUDA framework was updated to latest 9.2 so that could have some unexpected side-effects (unlikely though).
Thank you Miska. dll issue solved. I don't know what you did but simply installing the dll and not what it might trigger did not sound right : I very simply run ServerManager from my Minimum Server state and installed Quality etc feature
As of the berserk track then I'll investigate a corrupted file and redo the rip (I can't run CUDA). it happened with 3.204 & 3.21. it's very stressful since I fear it might damage speakers if it starts to happen here and there...
btw, there doesn't seem to be a correlation between filter gain and how loud music plays (and is measured ie with pink noise to calibrate the filters). With about 8.5 gain I chose -9 dB attenuation instead of the -3 recommended to avoid clipping ; any comment ? thanks
Filter gain printout is estimate, another estimate is written to the log file. But it doesn't easily correlate with loudness. Reason is that a room correction filter of "filter gain 6 dB" may have only very narrow 6 dB boost at for example 123 Hz frequency and much lower level on all other frequencies. You won't notice this until something in the music content happens to have that particular frequency. And you may not notice even then.
But for all these kind of cases HQPlayer as extra safety - soft limiter in case processing output goes above 0 dBFS level (the internal processing pipeline has practically unlimited headroom). You will notice this when "Limited" counter in HQPlayer main window increments and the volume knob goes red to indicate output level has been limited. But there's a caveat in this, if you have set volume in HQPlayer quite a bit lower, then even the peak may still be below 0 dBFS but quite a bit louder than anything else. For this reason I recommend designing room correction filters without large gains (more than about 6 dB). This is usually quite generic recommendation from other people too, because one cannot fill nulls and it will only increase output power a lot.
d3342ee215