-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable searching for tracks in a range of bpms #6283
Comments
Commented by: ywwg |
Commented by: ywwg Whoops typo, forgot to initialize a variable. |
Commented by: esbrandt Thanks Owen, tested and works like a charm. |
Commented by: rryan The patch looks good to me except I'd prefer that we make the user be a little more explicit about searching by BPM. Bart did some work on this for his GSoC project but it hasn't been merged yet. So that people don't have to learn the new way when his branch merges, I think it'd be better if this patch matched the behavior of the advanced search branch. Doing this just means checking for a "bpm:" prefix. For example: [com truise bpm:110-120] |
Commented by: rryan Trunk now has the ability to do queries like:
|
Duplicate of #5572 |
Reported by: ywwg
Date: 2012-02-23T21:47:02Z
Status: In Progress
Importance: Wishlist
Launchpad Issue: lp939845
Attachments: search_bpm.diff
It would be nice to search for tracks of a certain bpm range. Here's a patch that does it!
Just type a term in the form "120-140" (no spaces) in the search box. The patch looks for the hyphen and then looks for two integers on either side. If any of these requirements isn't satisfied the term is treated as a regular search term.
The text was updated successfully, but these errors were encountered: