Open bdyetton opened 10 months ago
Hello Benjamin,
I'm glad to hear that you tried the BPM analyzer. In my opinion, it's a common issue with BPM detection methods to discern whether a track is, for example, 70 BPM or 140 BPM (twice 70). I could adjust the range from 60 to 180 BPM. However, in this scenario, the accuracy becomes unstable in certain situations. This happens because the algorithm sometimes chooses double or half the original BPM.
To address this issue, the algorithm needs to be refined. It should be capable of distinguishing between slow and fast music, especially when the result falls within the range after division or multiplication with the original BPM with 2.
greetings Matthias ;)
Hi Matthias, Agreed, i've seen the same issues many times in consumer software like Serato or Mixed In Key! However, if the range is extended to 90-179BPM (rather than 60-180) then there will be a unique BPM for each track. Perhaps something like 70-139BPM is better though, while this would force dubstep and drum and base to half BPM (sitting at ~70BPM and ~86BPM) its better than than hip-hop being doubled to >140BPM.
Hi, Are there technical limitations that restrict the audio range to 110-160 BPM? I'd love for it to at least pick up the full range of music genres at full or half tempo e.g. (90-179BPM). Thanks!