Hey I’m looking around your tool and I noticed a couple issues.
The speed1 chop that times each of your tap is clamping at 1. This means you can’t reach a bpm lower than 60 because it stops counting time at 1.
Also, when you begin tapping again, it will initially send that. So instead of adjusting your tempo, you throw in an unrelated 1 in the mix, most likely resulting in a dramatic tempo loss.
The fix is easy though. The first tap should be ignored, that way you don’t count the time elapsed between the last time you used the tool and the first tap you just did.
So I raised the clamp on speed1 to 5 and I use this value to skip an incoming tap while speed is equal to 5. This first tap gets skipped but it reset the speed1 CHOP in the process, ready to account for the next tap.
Edit: I just noticed that if I try to use tap while nothing “fetches” the speed1 value. (like if I’m in presentation mode) Every values recorded by the taps will be 0.2 Giving me a bpm of 300. This is weird. Considering this action still interacts with TD’s behavior shouldn’t it be accurate?
Edit2: I know this is related to the changes I did to your .tox.
Edit3: Avoiding to use a speed fixes the issue. I’ve attached my TOX to this post. It’s just the tap tempo segment changing the tempo of TD.
jbl.tap_tempo.tox (2.85 KB)