Skip to content
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

How to determine the BPM data is valid in realtime... #8

Open
themindfactory opened this issue Apr 17, 2018 · 1 comment
Open

How to determine the BPM data is valid in realtime... #8

themindfactory opened this issue Apr 17, 2018 · 1 comment

Comments

@themindfactory
Copy link

So far I think I have the code working, I have currently an array of DFT "bins" 32 of them, 40hz to approx 200hz in 5hz increments... I call the BPM algo by first populating the vector with the bins 1 2 3 ... 32 32 ... 3 2 1... this is correct, I am faking out the FFT vector :-)

I get quality scores that climb as the music is played sometimes in excess of 50,000, is this OK?

The winner # seems to be 10X too big and the winner_lo seems OK, but just is delayed compared to winner...

But in the scenario of printing out the BPM to the screen, how to determine when the time is right and the BPM is currently solid and valid.

Thanks for the awesome code!

RichardS

@themindfactory
Copy link
Author

Also as I think some more on this subject....

  1. when you build vector and send it with the "FFT" data 1 2 3 3 2 1 this is size 6??
  2. why does it seem to output data and then stop and "think" for awhile before outputting more data?
  3. I have noticed it will lock in on a BPM faster if my audio input is low.... the louder seems to take longer to lock....
  4. what is the best data to have for the fastest recognition...

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant