N
Niko Ugarov
Description:
Add an option for Tap Tempo so the project tempo is only updated after a user-defined number of taps (N), instead of changing immediately. This prevents accidental tempo changes from stray taps while still allowing deliberate tap-tempo use.
Problem:
Tap Tempo is extremely sensitive by design: even a single accidental tap can immediately change the global tempo. In live performance, accidental tempo changes are high-impact:
  • They can throw loops, quantization, and synced effects off instantly.
  • A user may brush a control unintentionally or trigger a bound tap action by mistake.
  • Recovery can be stressful and disruptive mid-song.
Users want Tap Tempo to be safer by requiring intentional input rather than reacting to one or two unintended taps.
Proposed Solution:
1) Add a Tap Tempo safety setting
  • Preference (global) or per-widget/per-binding option:
- "Update tempo after N taps"
- N configurable (e.g., 2–8 taps)
  • Default remains current behavior to preserve existing workflows unless enabled.
2) Define behavior while accumulating taps
  • Until N taps are received:
- Do not change tempo (hold current tempo).
- Optionally show a small indicator: "Tap tempo: 2/4" to confirm progress.
  • On the Nth tap:
- Set the tempo based on the last (N) taps (typical tap-tempo averaging).
3) Optional timing rules (nice-to-have)
  • Timeout: if taps stop for X seconds, reset the tap counter.
  • Optional "use last N-1 intervals" averaging to improve stability.
  • Optional "quantize apply" to next bar/beat to avoid mid-bar disruption (if desired).
4) Actions/MIDI binding integration
  • Ensure this safety rule applies equally whether Tap Tempo is triggered from:
- a UI button,
- a widget binding,
- or a MIDI/foot controller.
Benefits:
  • Prevents catastrophic accidental tempo changes in live sets.
  • Makes Tap Tempo practical on crowded performance pages and foot controllers.
  • Allows deliberate tempo setting with controlled confidence.
  • Reduces stress and improves reliability for tempo-synced workflows.
Examples:
  • Live safety:
- Set N = 4 taps. A single accidental tap does nothing; only an intentional 4-tap sequence updates tempo.
  • Foot controller:
- Tap tempo is bound to a pedal; N-tap requirement prevents tempo change from an accidental pedal bump.
  • Stable update:
- User taps 6 times; tempo is computed from the last intervals and applied once, yielding a smoother result.
This summary was automatically generated by GPT-5.2 Thinking on 2026-01-18
.
Original Post:
Tap tempo: trigger change after N taps to avoid accidental changes
I tap tempo very often so i've put in on the most accessible button on my foot controller. This button is also quite easy to hit accidentally - sometimes even 2 times, which is enough to change the tempo. Happens quite a lot to me. Especially frustrating, 'cause tempo changes cannot be undone with Undo action. If I could set it to e.g. 4, I think it'd fix the issue - it's very low chance to tap 4 times accidentally in a short time