Skip to main content
Topic: Binary comparer chokes on two particular offsetted tracks (Read 250 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Binary comparer chokes on two particular offsetted tracks

While comparing a 4-disc album offsetted by 30 samples, offset detection failed on two particular tracks.
Doing an inversion and mix procedure in Audacity doesn't seem to reveal any appreciable differences, even after maximizing gain and using a spectrum print view, so it seems it's just the offset detection in foobar dropping the ball.
All the other tracks were detected properly and compared fine, including longer and shorter ones.

When I order the whole album by number of samples, I get this:
489.804 - offset detected, compares OK
499.800 - offset not detected
506.856 - offset not detected
552.720 - offset detected, compares OK
Both offending files cluster together arround the 500k sample mark, avobe 490k and under 510k.
It seems there is something in there.

Re: Binary comparer chokes on two particular offsetted tracks

Reply #1
Fixed for the next version, thanks for reporting.

 

Re: Binary comparer chokes on two particular offsetted tracks

Reply #2
Updated and confirmed to work with these and also others I found in the meanwhile.
Much appreciated. Thank you.

 
SimplePortal 1.0.0 RC1 © 2008-2020