Holo Audio DACs have relatively decent analog reconstruction filter, but at 192k sampling rate it doesn’t have enough attenuation yet by the Nyquist frequency of 96 kHz. Hence the reconstruction is incomplete and there’s a strong series of images in the output signal. With 705.6/768k oversampling there are some images still left, but at relatively low level having reconstruction accuracy of about 13-bit level. At 1.4112/1.536M oversampling the reconstruction is nearly complete and reconstruction accuracy reaches 16-bit level.
1 Like
I suppose it’s normal to be able to activate DAC correction (Holo Spring 3) only when USB is connected.
When I use my Mutec MC3+ USB, connected via USB to NAA and via coaxial or AES to the Holo, the Holo no longer appears for correction.
I suppose there’s no way to do this if there’s no direct USB connection between NAA and the DAC?
But it’s a shame not to be able to use this DAC correction if you’re not using USB.
1 Like
Thank you, how about all those expensive DACs such as dCs, their reconstruction is incomplete too or they have much better analog reconstruction filters ? How down (Hz) and up (dB) go the images with Holo fed 192 ? does a reconstruction accuracy of about 13-bit level sound like extra compression ? in the same line as circle of confusion about reproduction environment (including in room frequency response, reverb etc) vs creation/mastering environment is it reasonable to think that some mastering are made/controlled and can sound better with a limited reconstruction accuracy ? Ie famed Steve Hoffman lists Audio Note DAC…
Sorry to bother you/ hope to positively distract you while some cry at AS ; I report no issue with my Studio M1 Max and 5.15, just the frustration that 24/96 @ 512 seems to work with Fast but (very short ) interrupts occur after a while. 44/48 to 512 with FAST 512 seem OK even with demanding filters. THank you, kudos. I’m just surprised hb serie scores only 3/5 ; m and s are really my favorite at the moment
There are two reasons in your case…
AES and S/PDIF are unidirectional, so it is impossible to detect the DAC behind such connection, and communicate in more advanced ways.
In addition, the maximum output rate is then limited to 192k PCM or DSD64 over DoP. DAC correction is not supported for such low rates in first place (please check the support table on our website).
dCS performs upsampling 5.6/6.1 MHz SDM to their 24-element array.
Usually a bit harsh and muddy/inaccurate.
Sounds mostly like you are running to thermal throttling.
@jussi_laako has ext3 disappeared? If so, for what reason/s ?
It was renamed to poly-sinc-ext2-xla to align naming with the poly-sinc-gauss group.
As I mentioned earlier, ext2 and gauss are now offered in matching pairs with matching parameters.
3 Likes
And I replaced the series ..gauss .. by poly-sync-ext2-long and poly-sync-ext2-hires-lp with great pleasure.
Of course in DSD 1024 - AHM7EC8B (Holo Spring3 without correction & NAA)
2 Likes
all the same, but with NAA and DAC correction on Spring 3 KTE
Still on V4 running an Ares II in NOS/PCM. Still pretty happy with V4, any good reason to upgrade if I want to continue using NOS/PCM?
Currently using poly-sinc-gauss and ns5 at max PCM rate. Dac bits set to 18. These settings turn my Ares II into an outstanding DAC. I tried all of the filters and switched between ns5 and and lns15 but i prefer ns5 because to my ears i lose a lot of detail with lns15. Bass gets smeared / mushy…
DAC correction for Ares II perhaps?
Thanks for answering Jussi, could you please elaborate. Whats DAC correction?
It is DAC model specific corrections to make the output more accurate. One of the many many new features introduced in v5.
2 Likes
I see I have to download the demo version and have a look at V5. Thanks man.
Since we are on Roon forum, also the “Idle time” feature is very useful when using Roon as source. Since it makes interactions like switching and seeking tracks much faster.
4 Likes
Version: 5.15.2 Embedded
poly-sinc-gauss-short
ASDM7EC-fast 512+fs
Dac Correction: Enabled
44.1k / 16 / 2 → 45.1584M / 1 /2
Amazing, able to do DSD 1024x48 option again with DAC correction enabled!
2 Likes
I went back to 256 with May for awhile myself, but I’m back to 512 now (esp with the addition of ext2 filters)
With my Spring 3 KTE, I tested it with SDM256 (ext2) and I sometimes get tiny music drops even with Shaper ul.
With SDM 512, same settings, big drops.
Finally, I stick with SDM1024 with the same settings except for Shaper AHM7EC8B, and everything’s perfect 
My HQP desktop 5.15.2 setup on a Mac mini M4 and NAA 5.17 on an RPI CM4
Hi all, I’m a bit confused and undecided on how to implement volume control in my sytem. My system is Roon/HQPlayer on a mac mini, SMSL RAW MDA1 DAC (will update to R2R DAC later next year), BAT VK3i tube preamp, Apollon Purifi Power Amp.
Here is how I run everything, since it’s a bedroon setup and Sonus Faber Grand Piano home speakers are large for the bedroom I don’t use much volume. Apollon amp is on lowest gain settings, for the BAT preamp since it’s tubes and I love tubes and want to activate that tube coloring I have it at 40-50. SMSL DAC was running at -20 DB until I read about cons of that and it’s better to use HQPlayer/Roon volume instead. So instead of running Roon/HQPlayer at -3 DB I now run it at -20 DB most of the day and DAC at 0 and -30 DB for quiet listening. How bad are these settings? to run both DAC at 0 and Roon/HQPlayer at -3 DB I need to run the BAT at 16! For my ears I prefer the sound with BAT at 50 and DAC at 0 instead of DAC at -20 or even -10 DB but would like to know if I’m decreasing the dynamic range too much. BTW everything is upsampled to DSD 256. Any advice?