Usage: java -jar synchotron.jar [--cut] primary_wav secondary_wav primary_wav: original PCM WAVE file (up to 24 bit integer supported)secondary_wav: PCM WAVE file with similar content and possible delay --cut: remove delay from the beginning of secondary_wav --fullscan: scan entire file (very slow)
java -jar Synchrotron.jar --cut tmp1.wav tmp2.wav PCM_SIGNED 44100.0 Hz, 16 bit, stereo, 4 bytes/frame, little-endianSkipped 24598 leading sample(s) to improve accuracy.Delay: 1088 - Cross Correlation: 0.99712723Delay removal successful!
Also, can this do subsample delays? Is that even a concern with lossy encoders?
Quote from: Axon on 06 June, 2009, 12:45:05 PMAlso, can this do subsample delays? Is that even a concern with lossy encoders?No, Synchrotron does not oversample and works at exactly the same precision (sample rate) as the input. For its intended main purpose (WAV file correction) subsample precision would not make a difference, since you can only apply correction in integer steps.
It's no problem to increase these values, but it would considerably hurt performance, that's why they are preset moderately.
Plus, at normal sampling rates of 32 kHz or more, sub-sample delays are inaudible. Actually, delays of one or two samples are probably also inaudible, but for blind listening tests, it is always better to restrict inter-stimulus delay to the microsecond range.
Are you seriously claiming that you can reliably hear a difference between two files that are misaligned by 3 or more samples?My experienced-based rule of thumb says that up to 1 mSec difference is innocious.