BPM range fix workaround

[Pegasus]

If you have tracks outside of the default 70-130 BPM range, here's how to get Mixxx to detect them correctly until we fix the underlying problem:

• Open Options->Preferences->BPM Detection
• Create or edit a BPM scheme with the range you want & click OK.
• Highlight that scheme in the list.
• Click the "Default" button. (It's only by doing this that the selected BPM scheme is activated.)
• Go analyze a new track and see if the BPM is correct.

We hope to make this automatic and more intuitive in a future version of Mixxx.

[al2cand]

hi, I just started getting familiar with the different tools mixxx offers but can't succeed to listen my tracks with the correct rate (always way too slow, as if the program wasn't figuring out the bpm correctly) (tried for many mp3s) I used the trick you just posted and it raised my maximum bpm to 242 but still my song plays on morphine even if my rate bar is topped + the 90%...

[Pegasus]

What OS and sound API are you using? Let me guess: Windows and DirectSound? If so, switch to ASIO and it should be much better.

[Tj-Shredder]

I have the same problem and the guess could not be further away from reality.
I am on OS X and core audio on a Macbook Air running Lion...
I don't know how the BPM detection is supposed to work. Does it average and assumes a constant beat for the complete track? (would be a wrong assumption...
I have no idea why, but the beat bars are 0% on the spot, no matter what track or style also on tracks with very constant beats...
I guess it isn't at all a trivial task to analyze it correctly, if I could match it by hand in the wave form display that would be better for all cases...

keep going the good work, I can live with wrong BPM values, but correct ones would be certainly better...

Stefan

[jus]

@Tj-Shredder
Try Mixxx 1.11 beta which has has a totally revamped beat detection. Please notice that Mixxx will not over-write old beatgrids from Mixxx 1.10.0 by default, make sure to read the beta release announcements.