Description:

Add a setting that guarantees a minimum pre-roll (time or beats) before a quantized recording actually starts—so you always get a usable “count-in” even if you trigger very close to the loop boundary.

Problem:

Current count-in quantization aligns starts nicely, but if you tap near the end of the cycle, recording can begin almost immediately with effectively no prep time. That makes on-screen triggering tricky (especially with mixed loop lengths) and forces players to watch the clock rather than play.

Proposed Solution:

Introduce Minimum Count-In with two units:

• Beats (musical) or Milliseconds (time).

Behavior: when a record/overdub is quantized to the next boundary, if the remaining time to that boundary is less than the minimum, defer to the subsequent boundary (or enough boundaries) so the performer always receives at least the configured pre-roll.

Options: per-action override, per-project default, and per-track preference; visual/HUD countdown; choice to include/exclude metronome click.

Benefits:

• Reliable, predictable prep time before recording—fewer rushed entrances.

• Less “clock watching”; more focus on playing.

• Consistent feel across projects and loop lengths.

• Works equally well for screen taps, footswitches, and MIDI triggers.

Examples:

• Minimum = 1 beat: you tap 0.25 beats before the bar—start is deferred one bar so you still get a full beat of count-in.

• Minimum = 300 ms: on a fast tempo, taps that are too close to the boundary wait one extra cycle to deliver ~300 ms of prep.

• Per-track: melodic loops use 1 beat; percussion uses 0 beats (instant) for tight pickups.

This summary was automatically generated by GPT-5 Thinking on 2025-08-25.

Original Post:

Add the possibility to set a minimum amount of time / beats for the count-in quantization

The count-in quantization is useful to get loops aligned, but also to get a minimal amount of time before the recording starts if you're triggering the loops using the ipad screen. But if you're triggering very near the end of the current cycle, you won't get any time at all and the recording will be starting almost instantly. This forces you to pay close attention to the clock cycle and can be quite tricky to anticipate just listening to the loops currently playing if they are of various length.

It would be nice to be allowed to set a minimum amount of time / beats that the count-in must have, otherwise it will just wait for the next cycle.