Re: Binary Comparator version 2.0
Reply #19 –
The following makes me curious. Comparing two pressings, and most tracks have different length, non-zero offset and end with "the tracks became identical after applying offset and truncating first/last samples."
But then there is one track-pair that does not. It still ends up with an identical subset, but is reported different. I see the catch, but I wonder what the issue is.
Differences found: length mismatch - 6:55.533333 vs 6:55.040000, 18325020 vs 18303264 samples.
Compared 18303264 samples, discarded last 21756 samples from the longer file.
[...]
Compared 18303264 samples, with offset of -10677 discarding last/first samples from total of 18313941, discarded samples were not silent in either file, discarded last 11079 samples from the longer file.
No differences in decoded data found within the compared range.
Yet the heading says "Differences found in compared tracks." Of course there are differences, but not in the subset.
Which brings me to the issue:
- Is it so that it truncates, calculates offset, truncates again if it has to, and then compares?
- Shouldn't it rather, after calculating offset, "start anew"? Otherwise it may "have already discarded the wrong samles", wouldn't it?
And is that what happened, and the reason why it reports "Differences found" despite having discarded itself down to a bit-identical intersection?