member badge
ultracello
Description:
Add a repeat/loop mode for Action Sequences, and provide robust ways to stop or abort running sequences via Actions. Stopping should support immediate abort, graceful stop at sequence end, scheduled stop after a musical/time delay, and conditional stop triggers (events/conditions).
Problem:
Repeating Action Sequences are only safe and usable in performance if users can reliably stop them under different circumstances:
  • Sometimes you need an emergency kill: stop immediately, no waiting.
  • Sometimes you want a clean exit: let the current run finish, then stop.
  • Sometimes you want a timed exit: stop after X ms or after X beats/bars, musically aligned.
  • Sometimes the stop should be automatic when a condition/event happens (e.g., clock reset, stop all clips, transport stop).
Without strong stop/abort controls, repeat mode can become risky:
  • A sequence can keep running when the musical context changes.
  • Users need complex workarounds or manual intervention to regain control.
Proposed Solution:
1) Repeat settings (sequence-level)
  • Repeat mode:
- Off (default)
- Repeat indefinitely
- Repeat N times
  • Optional: loop region (loop start/end step)
2) Add explicit stop/abort actions for sequences
Provide Actions such as:
  • Abort Sequence (immediate)
- Stops the sequence instantly, cancels any pending delays/waits.
  • Stop Sequence After Current Run (graceful)
- Allows the sequence to complete its current pass, then stops before restarting.
  • Stop Sequence After Delay
- Delay specified as:
- Milliseconds, or
- Beats/Bars (tempo-synced, optionally quantized to beat/bar boundary)
  • Stop All Sequences (optional global safety action)
3) Conditional stop / event-based stop rules
Add optional stop conditions that can be attached to a running sequence instance (or configured on the sequence):
  • Stop when clock is reset
  • Stop when transport stops
  • Stop when "Stop All Clips" is triggered
  • Stop when a specified clip/group stops/starts (optional)
  • Stop when a boolean condition becomes true (if Loopy has condition system usable by actions)
Implementation note:
  • This can be modeled as a "Sequence Stop Trigger" system, similar to Follow Actions triggers, but applied to running sequences.
4) Visibility and predictability
  • Show that a sequence is running and whether it is:
- repeating
- scheduled to stop (and when)
- armed with conditional stop rules
  • Prevent accidental multiple concurrent instances unless explicitly enabled.
Benefits:
  • Makes repeat mode safe for live use: users can always regain control.
  • Supports both "emergency stop" and "musical stop" workflows.
  • Reduces complexity vs. building stop logic with additional helper sequences and workarounds.
  • Enables more ambitious automation patterns with clear lifecycle control.
Examples:
  • Emergency kill:
- A repeating FX modulation sequence is running; user triggers "Abort Sequence" to stop immediately.
  • Clean exit:
- A 4-bar repeating build sequence is running; user triggers "Stop After Current Run" so it finishes the bar cleanly, then stops.
  • Timed exit:
- Start a repeat sequence and schedule "Stop after 8 bars" so it automatically ends at a musically correct point.
  • Conditional exit:
- Sequence repeats while performing; if the clock is reset or "Stop All Clips" is triggered, the sequence stops automatically to avoid unintended actions.
This summary was automatically generated by GPT-5.2 Thinking on 2025-12-27
.
Original Post:
Let's say you have added two actions for your widget. Example:
1st long press:
peel -1 clip
2nd long press:
replace +1 clip
Can we have a repeat mode for action sequences please?
Wanted results for the example above should be:
1st long press:
peel -1 clip
2nd long press:
replace +1 clip
3rd long press:
peel -1 clip
4th long press:
replace +1 clip
5th long press:
peel -1 clip
6th long press:
replace +1 clip
and so on...
Please also let us set the amount of repeats.