BPM accuracy
I really appreciate all efforts you are putting into this project... however, to be brief - getting 70,7 BPM for "Prodigy's Firestarter" and 139,5 for "Sade's Is it a Crime" makes the whole BPM feature USELES (!). Thats my 50 cents.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Leo on 11 Apr, 2010 08:59 PM
And I have used recommended "rayshoot" 70-140 with max accuracy... Lame
Support Staff 2 Posted by hendrik on 11 Apr, 2010 09:26 PM
Well, no algorithm is always right - unfortunately.
3 Posted by phil on 11 Feb, 2011 10:21 PM
At least i can solve the "Firestarter" bpm mystery...... despite official bpm (140) it "seems" to be slightly faster......(self tapping 141-142, Mixmeisters algorithm 141,7, Traktor 70,7*2= 141,4 (100%))
.... using preset 70-140 sadly (i WISH there would be custom values) does NOT cover this.
as always with bpm.detection, either it's completely WRONG (happens), or you just have to DOULBE or HALF the calculated bpm (most common scenario)
The best way, despite looping and calculating bpm on sample-base yourself,.... make selective! analyses. E.g. one run with 70-140 for Hiphop, next run with 90-180bpm for electronic stuff...... still errors, but less.