The graph above cuts off before the last big chord, so it's missing some of the high-frequency energy from strings struck hard.

This is Voxengo's static plot of the few quiet seconds at the end, derived from the difference file after it has been boosted (so never mind the scale at the right, it overstates the difference).   The main thing I was wondering about for this analysis was the mids, and it looks like that is...

Replication. This is just path30jr versus path30n again, to establish the reliability and consistency over more rounds. Back to the Beyerdynamic 770 Pros for these. I'm listening in the mids, if that helps any. The notes are "shaped" differently not in the bass extension or treble extension...

Is there some function of the jittering algorithms in the software used that could be providing other artifacts? Another possibility (I think): Is there some interaction of the jittered file with my particular system which could somehow be highlighting or amplifying the jitter artifacts of the...

Replication.   foo_abx 1.3.4 report foobar2000 v1.2.8 2013/09/27 16:48:19 File A: C:\Users\jhughes1\Downloads\path30n.flac File B: C:\Users\jhughes1\Downloads\path30jr.flac 16:48:19 : Test started. 16:48:45 : 01/01  50.0% 16:48:53 : 02/02  25.0% 16:49:06 : 03/03  12.5% 16:49:49 ...

Yes, these are normal listening levels, it interferes with identification if I crank levels. The cue is the moment of attack, as the hammers strike the strings on quiet chord. The loud chord at the beginning is too complex, at least with what I'm able to do so far. I'm still cuing on "focus"...

Okay, I'm going to just leave Crane Song alone for now, until I understand what's up with their files.   In the meantime, path30n versus the latest, path30jr:   foo_abx 1.3.4 report foobar2000 v1.2.8 2013/09/26 20:14:38 File A: C:\Users\KiarkAudio\Documents\Ravel Listening...

Very quick and dirty test, cheap earphones, from the Crane Song website, this is the reference file B versus the A version.   foo_abx 1.3.4 report foobar2000 v1.2.8 2013/09/26 13:52:13 File A: C:\Users\jhughes1\Downloads\Crane_B.wav File B: C:\Users\jhughes1\Downloads\Crane_A.wav 13:52:13...

  i dont know if this is true or not, you are saying someone whos not into audio when listening to music dont pay as much attention to whats going on? or is it simply that they cant tell the difference between how something sounds on one system compares to another?   No, I'm saying something...

This note is just to check that I haven't missed a follow-up file or recommendation. I think it would be useful to nail down how a real 2-3ns jittered file compares to a non-jittered one. I think I do need to leave it to the experts what sort of reference file to use. Something really recent...

The OP seems like a simpler question than it is. One could pull a random 18-year-old (one not already over-exposed to loud volumes) out of the population and get "better ears" than mine every time, on clinical measures.   But we listen to music with our ears, with our minds, and an even...

I say this purely as an outside possibility. SoundForge has had clipping repair for awhile now as a Tool. I've never had occasion to use it, so I can't say how it does. Audacity has "Repair" in its "Effect" menu list. I generated a clip just now and sure enough if fixed it.   If it's your...

And, 20ns is about an order of magnitude of jitter greater than we'd actually expect to see in any device that's not absolute junk, if I read the previous material correctly. And I would expect that it's the signal correlated components that are contributing to the piano sound.

    I've got plenty of space, so I don't rip to any lossy formats. If you go to WAV first and the bass is OK, then you can try first reducing it by 1db (use open source Audacity, or equivalent), THEN converting to your favorite flavor of MP3. Not all encoders are the same. I would recommend a...

SoundForge Statistics says peak difference is in the -77db range, which doesn't seem like much.   However, when I boost it and listen, it doesn't sound like a pure noise signal. The difference file retains a shadow of the original sounds, with lots of distortion, of course.

Are we highly confident that there is no other possible source of differences in these tracks?   The tests below are for path30n versus path30jl. I have learned what these clips sound like, and I am learning (maybe) what jitter sounds like. But even discounting for some sort of learning...

It's going to heat up fast, yes? The magnet will be pushing against the physical resistance of the driver material itself continuously.

In the future we'll get fitted with bionic cochlear implants that have effective response from 0.001 Hz (elephants, pigeons) to 200 kHz (bats, dolphins). Then we can start having these arguments all over again.

An unbroken sequence of zeroes in the samples would be 0 Hz at 0 voltage. How about an unbroken sequence of, say, 0xc7f1's? That would also be 0 Hz, but at some non-zero voltage (what would the physical driver do, shift forward a millimeter and hang there???).

    Actually I was going to a purely theoretical point, that *if* a record company cared to do so, they could tailor mixes to the intended platforms. Didn't mean to imply that it's an actual practice, which actually kind of strikes me as wishful thinking. Anyway, that's a possible reason to...

I haven't done updated range yet, thanks for path30jl.   How close are we to realistic jitter yet, as a function of actual clocks in hardware? I've assumed (because of gigantic clock rates all over normal PC motherboards) that jitter was never an issue at all, but I don't know what sort of...

This is two tests of the same two files, pathn versus pathj, so there's replication of the result.   I did previous tests listening for any kind of noise or breakup effect on the sustained chords. Those are all null, failure to positively ABX. So if there's some sort of calculable noise...

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.  ...

Exactly, that's the kind of thing I mean.

On the OP, there is an MP3 encoder I would recommend, because of the effect it has on Redbook audio. The LAME 3100l  (that's a lower-case letter "L" at the end) is available here. It is a command-line program, but the commands are very short and easy to understand.   To my ears, this algorithm...