JSmith
Master Contributor
Yeah... I just thought it can be handy for other readers to have links to the other past threads present.But it seems that the OP was aware of these...
JSmith
Yeah... I just thought it can be handy for other readers to have links to the other past threads present.But it seems that the OP was aware of these...
Who's audibility? At what conditions?Yes! Audibility is EVERYTHING!
How did you confirm this? My test results show that reducing the volume can avoid ISP clipping. I tested with 11025Hz +3dB ISP at 44100Hz, there is no clipping if the volume is lower than -3dB.ES9219 (w/ Hyperstream III):
View attachment 487663
Volume Control is AFTER the reconstruction filter. I also confirmed this with the volume control of Neutron DAC V1.
Lets say we have both.I suppose limiters used in the production process are a bigger audible issue than the ISO (when not handled correctly).
I suppose it also depends on how 'big' the ISO over is, the duration and how often it occurs.
When that is often and substantial the recorded music is poorly produced (loudness wars and clipping) that it would be more of a source sound quality issue that is audible than the actual IS over ?
clipped.How it would look like at signal level?
Yep, agree.When that is often and substantial the recorded music is poorly produced (loudness wars and clipping) that it would be more of a source sound quality issue that is audible than the actual IS over ?
My NAD M33 has this issue when certain settings are on and a subwoofer is used. It requires playing specific songs that trigger intersample overs. If I’m not looking for the distortion, it’s hard to notice it.I know what they are - I know how they happen.
I've never knowingly heard distortion coming from intersample overs. When I first got my MiniDSP flex, I set the input gain to -3dB to avoid any risk. I recently set it back to 0dB and:
1 - Have not noticed any difference
2 - Have not ever heard anything I could attribute to intersample overs.
Is it not the case that only badly mastered music (basically clipping in any case) will cause them. And even then - if it only happens for an extremely brief period in the music it is going to be almost impossible to detect audibly in any case.
Yet there seems to be all sorts of FUD talked about it in conjunction with DACs. We even have a whole thread discussing how to test DACs for it. It feels to me like it is the "new jitter" Something that people can hang their hat of audble differences on - without it being an actual problem in reality.
What am I missing?
Has anyone else heard the effect of inter-sample overs - if so, which track, at what time? And what does it sound like?
Agree, what I'm asking is how would clip² works, the mechanism behind it.clipped.
Point taken. IME IS-overs typically happen with tracks that are already "broken by design" and the perceived advantage of those IS-overs being faithfully reproduced or not is nil, probably even with extreme cases.When that is often and substantial the recorded music is poorly produced (loudness wars and clipping) that it would be more of a source sound quality issue that is audible than the actual IS over ?
My NAD M33 has this issue when certain settings are on and a subwoofer is used. It requires playing specific songs that trigger intersample overs. If I’m not looking for the distortion, it’s hard to notice it.
Example songs would be nice .I can't find it at the moment but I once posted a track here for A/B testing of IS-overs being faithfully reproduced vs clipped. With that knowledge and thorough ABX testing I remember only one person could detect the difference.
My conclusion is that with DACs that handle IS-overs gracefully by simply (soft-)clipping them as most of today's DACs do, IS-overs are non-issue, practically. A few DACs are not well-behaved and the moment digital pre-processing of any kind is involved, starting with simple EQ, we are subject to the competence of the programmers to avoid nasty IS-over effects happening upstream of the DAC.
Resampling is one of the typical offenders, and sadly even otherwise excellent software suffers from problems here (the Linux SoX utility/library for example, where they made the fatal decision to use integer math only, internally).
Would you provide more specifics on how you tested it? The Neutron HiFi DAC V1 on the current FW definitely does not include software volume control in its DSP,How did you confirm this? My test results show that reducing the volume can avoid ISP clipping. I tested with 11025Hz +3dB ISP at 44100Hz, there is no clipping if the volume is lower than -3dB.
I connected Neutron HiFi DAC V1 to my Windows 11 PC, and played the 11025 +3dB file in WASAPI Exclude mode. The DAC output is connected to Babyface Pro FS IN3/4. Neutron HiFi DAC V1 is in 2Vrms mode, DSP off, THD compensation off. Ignore the grassy noise floor because of ground loop, I don't think this affects the conclusion.Would you provide more specifics on how you tested it? The Neutron HiFi DAC V1 on the current FW definitely does not include software volume control in its DSP, and the ES9219 in it controls volume after oversampling as shown in the chip's datasheet.
Here is my test result. Used the same 11025 Hz ISO test signal at full scale but this time I even lowered the device volume to -6 dB:
View attachment 487802
Certainly overloaded.
Where did you get the test signal? What player did you use? How did you lower the device volume?I connected Neutron HiFi DAC V1 to my Windows 11 PC, and played the 11025 +3dB file in WASAPI Exclude mode. The DAC output is connected to Babyface Pro FS IN3/4. Neutron HiFi DAC V1 is in 2Vrms mode, DSP off, THD compensation off. Ignore the grassy noise floor because of ground loop, I don't think this affects the conclusion.