Comment 7 for bug 1796262

A while back when my library contained a lot of vinyl rips I went through and checked that the BPM values were right to around 1/1,000th of a BPM - ie accurate enough that over a long transition between two tracks I could rely purely on bpm sync. I checked around 400 tracks this way.

From that bit of my library I've extracted about 250 tracks that are currently set to exact BPM values, and re-analyzed the lot, to see if the analyzer agrees.

In about 180 cases the analyzed value matched the one I previously had for that track.

In about 30 cases the analyzed value needed to be changed to 3/4 of what it was, even though the upper limit I set for the BPM Range was below the value it calculated.

In about 35 cases the analyzed value was off by somewhere between 0.0001 and 0.1 bpm

In 6-7 cases the value was basically just wrong.

So I think it's fair to say there's some room for improvement in the analyzer algorithm, but again, isn't it a third-party plugin, in which case how could we make changes to it anyway?

csv attached in case anybody is interested.