This is essential. Don’t stop.
1 Like
The purpose of this thread is to warn people who think the tempo displayed with decimals is the good one. My English being limited, I’m not sure if I expressed it correctly.
As I already said, wrong tempo can be problematic will long stems wihout timestretch (I wonder if it is problematic with timestretch too, if the estimated tempo is wrong).
Also problematic for looped samples after a few loops, and potentially problematic with slices too.
Slices at 203.2 bpm, original tempo x 2 : clics
Slices at 103.1 bpm, original tempo (original sample recorded in OT) : no clics
Problem : 103.1 and 203.2 bpm displayed are actually 103.125 and 203.2083
2 Amen Break loops, 1 retriggered, the other one looped, 68.5 bpm, original tempo / 2 : drift (3mn recording, listen to the end)
2 Amen Break loops, 1 retriggered, the other one looped, 137 bpm, original tempo (export from DAW), very slight drift (3mn recording, listen to the end)
Problem : 68.5 bpm displayed is actually 68.5416
With a 3mn stem, the above drift example would be the same.
What about being in the same car, listening to the same music? 
6 Likes
Excellent examples. Thanks Sezare
(though there’s a Steve Reich style OT thread somewhere where this could be presented as a strength 
)
1 Like
On the contrary, it works really well. High retrigs like 1/128 seemed not in tune, didn’t check.