Why is Live so unreliable at beatmatching?
Posted: Sun Apr 28, 2013 1:08 pm
I am starting my quarterly amateur DJ prep again, and as always, I am baffled by this:
Why is live so very unreliable at correctly guessing the bpm *and* the beats of most dance tracks?
Usually, Live decides on some kind of weird decimal fraction (135.99 BPM) when the real BPM is a whole number. The result: a track that floats out of time as it plays. By the end of the song, the beats *plainly* don't match up to the grid markers.
Why does the algorithm get it so wrong?
I mean, one massive clue should be that 217 bar song warped at the wrong bpm will show up as having a different length from start to finish as the unwarped track. Surely these are things that Live's warping and analysis routines should be able to get right?
And other packages (traktor, for example) routinely get the beats right with ease.
So why does Lipe, supposedly the software that pioneered warping, get it so wrong?
I am just wondering
Why is live so very unreliable at correctly guessing the bpm *and* the beats of most dance tracks?
Usually, Live decides on some kind of weird decimal fraction (135.99 BPM) when the real BPM is a whole number. The result: a track that floats out of time as it plays. By the end of the song, the beats *plainly* don't match up to the grid markers.
Why does the algorithm get it so wrong?
I mean, one massive clue should be that 217 bar song warped at the wrong bpm will show up as having a different length from start to finish as the unwarped track. Surely these are things that Live's warping and analysis routines should be able to get right?
And other packages (traktor, for example) routinely get the beats right with ease.
So why does Lipe, supposedly the software that pioneered warping, get it so wrong?
I am just wondering