fuzzy BPM search

[Be]

It would be convenient to have a fuzzy BPM search operation rather than manually typing in a BPM range. For example "~bpm:115" could search for tracks with a BPM within 5 (or whatever number is decided upon) BPM of 115.

[Daniel Schürmann (daschuer)]

We already support
bpm:140
bpm: >140
bpm: >=140
bpm: 140-150

~bpm:115 looks wrong in this relation.

I think we support

~key:2A

but not the obvious key:~2A :-(

I would not be able to guess it.

I think we should support both.

@rryan: Is there something I have forgot?

[Be (be.ing)]

I disagree. I'd rather see that the current track's BPM is 145 and type "~bpm:145" than think about how far from the current BPM I want to search then add and subtract that number from the current track's BPM then type out that range.

[Daniel Schürmann (daschuer)]

Ah sorry, my comment was misleading.
The proposed feature is useful.

I prefer only bpm:~145 over ~bpm:145
That's all.

[Be (be.ing)]

Oh, I see. Yeah, bpm:~145 makes more sense.

[Michael S. (arbeit-u)]

Little hint from my side for the range that will be searched around the ~BPM.

Use the "pitch range" (or half) for the search range. BPM outside of this range are not usefull.

[ronso0 (ronso0)]

Use the "pitch range" (or half) for the search range.
+1 for that

another aspect if this request:
when searching bpm:~NN can we also show tracks with BPM that's halve/double of NN? or is that tooo far from the filtering suggested here?

my use case is mixing of footwork or dnb/jungle tracks with hiphop and other similiar slow beats, and it's tedious to basically alter the search string back & forth between '80-86' and '160-175'
Also I have halftime-dnb tracks (~86) where I left the detected BPM (and not double it to 170-176), but of course I'd like to mix them with tracks with regular dnb bpm.

[Dale (dj-kaza)]

Was just searching for such an open request to make exactly the same comment as you ronso0. I really need to be able to limit my views to tracks within a range of current BPM *including* tracks within the range of half and double that BPM! Repeated scrolling up and down up and down is extremely tiresome!

I also though fuzzy searching for BPM currently worked but testing it could make it do so....

I think bpm:~175 (for example) looks better but it should be standardised and Key currently works with ~key:1d and not wih key:~1d....

[Swiftb0y (swiftb0y)]

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