Repository navigation
specify BPM range when analysing. #52
Description
Activity
BTW, thank a lot for your work. it's nice to see finally something that i could dream to ditch rekordbox in the future. i keep a windows laptop just for it and it's sooo bloated.
Reacted by Vynull AppThank you! Yeah it's definitely configured more toward dance or trance music at the moment, but shouldn't be too hard to allow changing that. The analyzer applies a perceptual tempo prior, a soft preference centered on ~130 BPM, specifically to stop tracks locking onto a half or third tempo peak (a 124 track also "rings" at ~83, and the prior pulls it back up). That works for four-four house/trance, but for DnB it does the wrong thing: 174 is well above 130, so when the beat tracker finds a strong peak at the half (~87) or third (~58), the prior favors the slower one.
The initial plan is to add a global tempo-range setting, something like
--bpm-range 160-185(and the same in the config file). It'll do two things: re-centres that prior on your range so fast tempos stop getting dragged down, and octave-folds the final BPM into the range you set, doubling/halving (and catching the thirds) until it lands where it belongs. Set 160-185 and a track detected at 87 or 58 comes back as 174. The default stays exactly as it is today, so this only changes anything for people who opt in.I'll do the global setting first because it fixes your whole library in one shot and it's a small, contained change.
No firm ETA yet, but keep an eye on the branches, I'll try to push something soon! Thanks again!
What problem would this solve?
Most of my stuff is DNB and often, analysis is all out of place at half or even a third of the BPM. Being able to set a range fixes ot most of the time.
Proposed solution
Be able to set a range (maybe an advanced section in add files ? ) or even just a global setting.
Alternatives considered
cry.
Hardware context
No hardware.
Before submitting