BPM not displayed in numerical order

Bug #523774 reported by Korin
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Low
RJ Skerry-Ryan

Bug Description

BPMs are displayed (when set highest-to-lowest) from 99.99.. down to the lowest BPM, then the highest BPM all the way down to 100.0, instead of entirely from highest-to-lowest.

Additionally, I'm sure some of these BPMs should be half/double what they are detected as, but that's another issue (possibly already nearly resolved?)

Attached are some examples.

Tags: bpm library
Revision history for this message
Korin (4chons) wrote :
Revision history for this message
Korin (4chons) wrote :

Sorted by BPM, it starts at the 99.9 mark.

Revision history for this message
Sean M. Pappalardo (pegasus-renegadetech) wrote :

Sounds like it's looking at the BPM field as a string instead of a (float) number.

Revision history for this message
Smashuu (smashuu) wrote :

That's what's happening, I'm getting it too. The 100s come first, then the 70s, 80s, 90s.

RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: New → Confirmed
milestone: none → 1.8.0
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Should be fixed in trunk now -- thanks for reporting this.

Changed in mixxx:
importance: Undecided → Low
assignee: nobody → RJ Ryan (rryan)
status: Confirmed → Fix Committed
tags: added: bpm library
Revision history for this message
Rafael Winter (rafael-winter) wrote :

I am using Mixxx 1.8.0~beta1 and this issue still happens. There is something worth commenting, in my system (Windows Vista, locale PT-BR) the BPM column uses comma instead of dot, i.e 72,465 instead of 72.465 and this may mess the column sorting. I have installed the 1.8.0 beta1 over the 1.7.0 and the library was migrated automatically.

Please take a look at my screenshot: mixxxBPM3.png. If you need more information, please let me know.

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Hi Rafael,

The bug has been fixed in our trunk, which is where we do development on the latest version of Mixxx. Mixxx 1.8.0 beta1 has this issue, but beta2 which is due in the next week will not have the issue.

Thanks,
RJ Ryan

RJ Skerry-Ryan (rryan)
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/5324

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.