Sorting numbers in comments... (everywhere?)

Bug #1692206 reported by mevsme
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Invalid
Undecided
Unassigned

Bug Description

I don't know who, god damn, invented this sorting method:
1 - name...
10 - name...
101 - name...
2 - name...
20 - name...

But it's stupid and pissing me off anywhere I meet it.

Here's my situation: to be software-independent I am keeping tracks BPM in comments.
But mixxx sorts numbers in comments in this counter intuitive way? Can\will it be fixed?

Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

Comments are sorted lexicographically. Mixxx is not able to deduce the sort order from the contents of individual fields. In your case Mixxx would even need to know how to parse the number it should use for sorting from the remaining text.

Sorry, not possible.

PS: And it is not "stupid", by the way.

Revision history for this message
Be (be.ing) wrote :

Yeah, string fields are sorted as strings; this is the normal way to sort strings that have numbers in them. If you want numeric sorting, use a numeric field. I think the solution to having software independent BPM data is for Mixxx to write the BPM to the files' tags, not to use the comments field for something it isn't meant for. Refer to https://github.com/mixxxdj/mixxx/pull/728

Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

Writing BPM values into the corresponding tag works like a charm for various formats and is portable. Please note that BPM in ID3v2 tags (MP3) are rounded to integers according to the specification.

Unfortunately this feature will not available in the official Mixxx version until the mentioned PR is accepted.

Revision history for this message
mevsme (mevsme) wrote :

I see. Sorry, but I didn't get where I can store the BPM. Separate tag? I saw some mp3 have custom fields, like "encoder". Integer means 103, not 103.5, right?

Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

Please refer to http://id3.org/id3v2.4.0-frames "4.2.3 TBPM BPM (beats per minute)". Integer = no fractional digits.

Internally Mixxx uses double precision floating-point for BPM values.

Revision history for this message
mevsme (mevsme) wrote :

Integer for BPM, what a facepalm %)

Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

Please test the new version 2.1.0 that supports storing the BPM in file tags. Fractional digits for MP3 files should be preserved when re-importing tags.

Do you agree to close this bug report as Invalid? We do not plan and are not able to change the sorting of comments.

Changed in mixxx:
status: New → Incomplete
assignee: nobody → Uwe Klotz (uklotzde)
Revision history for this message
Daniel Schürmann (daschuer) wrote :

No responds, I am closing it now.

Changed in mixxx:
status: Incomplete → Invalid
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/8866

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.

Other bug subscribers

Remote bug watches

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