BPM detection

G3rsiu

Oct 3, 2026, 07:25 UTC

I have many old tracks that live outside the fixed BPM era we sort of live in today. My go to software was always Traktor ever since it came out in the early 2000s. Long story short, Traktor has no problems detecting a 137.65 bpm or 144.78 out of the gate while AutoPilot sets it at 138 or 145 - hence, drift. When i play, i like to just drag stuff from my files to my decks also - while having to do the extra step to add to playlist and analyze is not a deal breaker in itself, the sub .00 accuracy is in initial track detection is - it may also be that the tracks are detected correctly, but rounded up - maybe we can have a option to select the result ?

5 replies

G3rsiu

Oct 3, 2026, 07:27 UTC

oh, and i forgot to add - may features are sort of built on the premises that grid detection is point on - deff not a casual dj experience/solution

li0r

Oct 3, 2026, 20:08 UTC

In EDIT mode you can set your own BPM (on the left side). If after setting the correct BPM the grid is still not tight than you should use the "TEMPO MARKERS" section by pressing the "GRID/CUES" on left-top side of EDIT mode.

Deckgeneral

Oct 5, 2026, 22:17 UTC

when you use tempo markers, it pushes the grid out, they need to be draggable, rather than typing the bpm alone

G3rsiu

Oct 7, 2026, 09:33 UTC

Yeah OFC you can correct the BPM in edit mode - the problem is the detect rounding up the reported BPM - if it would also adjust the track tempo (detect 144.78 and pitch-set the tempo to 148 because it likes rounded numbers ?) that wouldn't be a issue - still, like i said, i have many tracks that live outside the fixed bpm range and if you try to freestyle a set and rely on the detection being on-point, its a no-no.

li0r

Oct 7, 2026, 15:20 UTC

Deckgeneral, In A/P Temp markers are not draggable and it's not required in order to make it work. Just add markers throughout the track and it should just work.