UltMusicSnob
100+ Head-Fier
- Joined
- Aug 14, 2013
- Posts
- 177
- Likes
- 11
Congrats, UltMusicSnob, for doing so well on that test. I can't help but notice that you had to "game" the test to achieve your results. That is, you had to "listen" in an unusual way pretty much wholly removed from how one would normally listen to music. With all respect, is this a tacit admission that the "added jitter" track would have been indistinguishable absent the gaming?
Point taken. I altered the protocol for no burn-in listening, just side-by-side comparisons across longer segments. I returned to the first track stv014 made, Range_j.flac, which did not have the jitter jacked up so high, and applied this test, listening to the drum set as a musician would.
All the snare hits are different.
foo_abx 1.3.4 report
foobar2000 v1.2.8
2013/09/22 11:36:16
File A: C:\Users\KiarkAudio\Documents\Ravel Listening Tests\Range.wav
File B: C:\Users\KiarkAudio\Documents\Ravel Listening Tests\Range_j.flac
11:36:16 : Test started.
11:36:48 : 01/01 50.0%
11:36:59 : 02/02 25.0%
11:37:10 : 02/03 50.0%
11:37:43 : 03/04 31.3%
11:38:02 : 04/05 18.8%
11:38:19 : 05/06 10.9%
11:38:41 : 06/07 6.3%
11:40:04 : 07/08 3.5%
11:40:40 : 07/09 9.0%
11:41:18 : 08/10 5.5%
11:42:26 : 09/11 3.3%
11:45:48 : 09/12 7.3%
11:46:10 : 10/13 4.6%
11:46:19 : 11/14 2.9%
11:46:27 : Test finished.
----------
Total: 11/14 (2.9%)
Of course, this time I had the enormous benefit of knowing what to listen for (snare), that I could apply across the track. No hunting around for artifacts.
I hear the jittered drum set as *slightly* less precise. The jittered version thuds instead of snapping tightly. It's a *tiny* difference, but you can find it anyplace that the cymbal-crazy drummer isn't covering it up. If I had to reverse-engineer from the treatment, I would hypothesize that the applied jittering is smearing/obscuring the attacks slightly.