My feeling is that these corrections improve the time domain. The sound in my case (Holo May) seems more coherent. Jussi, can you shed some light on what exactly is being corrected?
I tried this for my DAC200 but it seems to be so heavy that I canât run it on my server. I also use my own DSP filters through the Matrix pipeline so those in combination with the correction profile, seems to be too much for my server (while oversampling to DSD256). The new correction profile also seems to almost double the power usage of the server.
May I ask, what kind of corrections does this option do?
For Cyan 2 and upsampling to DSD 256 using ASDM7-EC-super and poly sinc gauss long. Processor load of my MacMini M1 is with and without correction at ~230-270%.
@jussi_laako is the new DAC correction feature documented somewhere, as in what does it do etc?
Is anyone experiencing crashes with HQPlayer when offloading with NVidia CUDA? I have been experiencing this since the most recent Nvidia driver update. Nvidia driver is 552.22 and I just updated HQPlayer to 5.7.0. The issue was also present with the previous version of HQPlayer, I think I was on 5.6.
If there is any more detail I can provide, please let me know. It seems there is a CUDA offloading issue with the latest Nvidia drivers.
Spring 2, DSD256, ASDM7EC-super, poly-sinc-gauss-xla, Mac Mini M1: ~490% CPU mapping to ~62% user.
@jussi_laako I got it working easily when I increased the speed for Red to 500/400Mb! A figure thrown out of a hat, but bigger than before.
DSD256 now with correction
Yeah it seems the dac correction is jacking up the resources past my cpu for me too. Enabled with pipeline it goes to 350% and drops out. disabled with pipeline is at 250% and no drops.
Using convolution fir in pipeline with .wavs made in Focus Fidelity.
Gustard A26
dsd256 (44.1x256)
poly-sinc-gauss-xla (a)1x
poly-sinc-gauss-hires-2x
ASDM7EC-light
Hallo.
You did whatÂż
Of course, appears jussi takes off on weekends with no explanation for new feature in new release. lol
Previously, I had limited Redâs internet to 200/50Mb for no reason, as I thought it would be fine with that. I raised that 500/400Mb and it started working. It does eat memory when dsd256 is over 16gb and 512 over 32gb, otherwise a pretty light process for my machineâŚ
Yes, and 1024 requires above 100Mb minimum bandwidth.
Will my T+A DAC8 DSD be supported?
That is normal. It is not possible to detect the DAC over unidirectional connections.
That is one of the aspects yes. Also overall sense of space may get improved as well.
This is not a static thing, but also something that will also develop over time, same way as filters, modulators, etc.
I donât think I have a concept of âtime offâ. There is something said in the manual. But I donât want to get too much into details, and the details are subject to change over time anyway.
It should be fine with full 1 Gbps as long as your have 802.3x properly working. And that is better than trying to limit the bandwidth (no benefit).
Technically it could. I have not decided on particular priority of what is to be supported and when.
Maybe I should arrange a vote on which ones have most demand. So far I focused mostly on set of devices from various different price categories that I see a good fit for HQPlayer use.
DAC8 DSD is a bit Windows focused though, especially with the stock firmware.
Pipeline and the dac correction must be enabled correct?
Just checking the dac correction enable box doesnât do anything without the matrix pipeline enabled?
Getting dropouts now when itâs enabled. Iâm using a left and right convolution filter .wav for room correction in the pipeline as well. No issues when the dac correction is disabled
Is this supposed to be resource heavy?
May I suggest IFI Pro idsd be a candidate for the next upgrade. A number of us have it and it works great with hqplayer!!
Cheers
I removed several restrictions, but on the PC I have to keep 750/450 on if I want to keep A+ in bufferbloatâŚ
Using amanero drive and ultraRendu with T+A DAC8.

