markdeejay75
it would be handy to search direct in the search box a set range of BPM numbers or to search below 100 BPM to be able to use.. BPM<100
Posté Mon 15 Jun 15 @ 4:34 pm
djdad
Search for a range of BPM is already available.
Add the BPM field to the Search options and type e.g. 120-130 in the Search box.
< and > cannot be used though
Add the BPM field to the Search options and type e.g. 120-130 in the Search box.
< and > cannot be used though
Posté Mon 15 Jun 15 @ 7:35 pm
markdeejay75
Okay, so can < and > be added in the future please (devs??)
Posté Mon 15 Jun 15 @ 8:03 pm
PachN
I don't see why.
Everything you could do with < and > is possible already.
Examples:
BPM < 100
0-100
Bpm > 120
120-999
Bpm < 130 and BPM > 80
81-129
Everything you could do with < and > is possible already.
Examples:
BPM < 100
0-100
Bpm > 120
120-999
Bpm < 130 and BPM > 80
81-129
Posté Thu 18 Jun 15 @ 7:51 am
markdeejay75
I didn't try a space between BPM and <
Posté Thu 18 Jun 15 @ 8:48 am
markdeejay75
PachN wrote :
I don't see why.
Everything you could do with < and > is possible already.
Everything you could do with < and > is possible already.
Not in the search box. just tried it again and no.
bpm 80-100 works in that range but bpm < 100 just makes it look on netsearch..
Posté Thu 18 Jun 15 @ 4:36 pm
PachN
That is not what I meant to say.
Of course "BPM < XXX" is not working, because it is not implemented.
Instead of using < > you can do it with the - operator.
Again the examples with some descibing text.
If you want to get all tracks with a BPM smaller 100, you would type:
BPM < 100
But that is not how it works. Just try this:
0-100
If you want tracks with BPM > 100 try this:
101-999
If you want tracks between a BPM range of 120 and 140, try this:
120-140
Now again the question: What other scenarios do you have in mind, that makes it necessary to use < or > that can not be covered using the desribed examples above?
Of course "BPM < XXX" is not working, because it is not implemented.
Instead of using < > you can do it with the - operator.
Again the examples with some descibing text.
If you want to get all tracks with a BPM smaller 100, you would type:
BPM < 100
But that is not how it works. Just try this:
0-100
If you want tracks with BPM > 100 try this:
101-999
If you want tracks between a BPM range of 120 and 140, try this:
120-140
Now again the question: What other scenarios do you have in mind, that makes it necessary to use < or > that can not be covered using the desribed examples above?
Posté Fri 19 Jun 15 @ 4:08 am