Allow ranges over 200 for BPM detection
Bug #1258483 reported by
David Planella
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Fix Released
|
Medium
|
jus | ||
Bug Description
As a swing DJ, generally the BPM range in songs is around 90-240 BPM. However, when trying to set the range for BPM detection under the Preferences dialog, the maximum BPM value allowed is 200, which means when running the analyzer on any song over 200 BPM, it will not get the right value (generally it then guesses half the BPM).
It'd be great if the max allowed value could be increased up to 240 (or preferably higher). Thanks!
| description: | updated |
| Changed in mixxx: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| milestone: | none → 1.12.0 |
| tags: | added: easy |
| Changed in mixxx: | |
| assignee: | nobody → jus (jus) |
| status: | Confirmed → Fix Committed |
| Changed in mixxx: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #3 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
@Daniel
txtMaxBpm in dlgprefbeatsdlg.ui is limited to 200.
Any reason for that?