Hi all,

Thanks for your thoughts - I'll try and clear this up :)

Firstly, just to re-iterate - the BTrack algorithm is really two separate sub-systems...

A) Tempo estimation phase: which reports a BPM value in a "tempo octave" of 80 - 160bpm

B) Beat tracking phase: which uses the bpm from the tempo estimation phase as a guide, but is otherwise is an entirely separate process based on its own momentum and analysis of the incoming data (onset detection function)

What I'm getting at here is that the getCurrentTempoEstimate() function is the output of the first phase and not the beat tracker reporting its current tempo. I accept this is confusing, so I am going to make some changes to the algorithm to make this clearer.

In general, it should be more obvious whether you are getting the "tempo estimation phase" BPM value, or the "what tempo is the beat tracker actually tracking beats at?".

@marcuseckert - you make a good point and I've noticed some ambiguity in the comments around my use of "hop size" and "frame size". To answer your question I'll need to take a deeper look, but that could possibly be the cause of some of the issues here also.

@CodingGhost - I'll take a look at your approach as I do this work to see whether it matches what the algorithm is expecting or not.

@Ge-lx - the sample rate thing is also something that should be addressed. Working now as a professional audio software developer I would never do something like hard-code the sample rate. But in research - where I was in 2008-09 when creating BTrack - this is the kind of simplification that is made because almost all the test databases are in 44.1kHz and I was mainly interested in getting good results (rather than the algorithm working in every use case). Obviously I should fix this.

So, I have some work to do - but that's fun. I'll do my best to do this quickly, but I'm also working on multiple product releases at the moment so let's see... :)

As a final thought - in my other repositories on Github, I'm trying to provide the best algorithm possible for the thing that the repo is trying to do. But in this one I'm trying to keep it as a bit of a "preserved record" of my work during my PhD. I want people to be able to read the paper and my thesis and for the code to match their expectations about how things work. So if I seem a bit slow to change this repo, that's a little bit by design so that it matches the written documents out there that I can't change.

Thanks for your patience and I'll report back 😄

Why is the Algorithm detecting only every second beat? #19

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions