You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes the BPM number doesn't update for a long time (I guess because the analysis is not confident enough?), so it's impossible to know whether the currently visible number is the current measured BPM or a stale number.
So it would be good to print or somehow indicate how long ago the number was last updated.
The text was updated successfully, but these errors were encountered:
Hello Horacio!
Thanks for your feedback. Currently, BPM keeps being displayed after it "stabilized". Right after "destabilization" it changes back to "Listening...", so in ideal scenario there is no stale number. Of course, in real-life all scenarios are possible. I'll have a look at what can be done.
Btw, you can get some extra info about events and BPM calculation in the browser console after you start the app in debug mode like that: https://bpmtech.no/?debug=true
Sometimes the BPM number doesn't update for a long time (I guess because the analysis is not confident enough?), so it's impossible to know whether the currently visible number is the current measured BPM or a stale number.
So it would be good to print or somehow indicate how long ago the number was last updated.
The text was updated successfully, but these errors were encountered: