virus 1980
Description:
Add first-class controls to
suspend/disable/enable Follow Actions
at multiple scopes—Global, Page, Color group, Track, and individual Clip—with mappable actions and conditions (e.g., “while recording”). Include targeting tools to disable
specific
follow actions by ID/tag rather than all-or-nothing.
Problem:
Follow Actions are great for automating program changes and flow, but sometimes you need them
temporarily off
—for example, to record into an
empty clip
without sending its stored program change. Today, a clip can be empty yet still carry a Follow Action that fires on trigger, causing unwanted device changes and disrupting performance.
Proposed Solution:
  • Scopes & Toggles:
-
Global:
Suspend All Follow Actions
/
Resume All
.
-
Color Group:
Enable/Disable Follow Actions for Color = X
.
-
Track/Clip:
Enable/Disable Follow Actions
(per target).
-
Page/Project presets
that recall scope states.
  • Selective Targeting:
- Tag follow actions (e.g.,
progChange
,
lighting
,
sceneAdvance
) and
Enable/Disable by Tag
.
- Address follow actions by
stable ID
for surgical control.
  • Context Conditions:
- One-tap
“While Recording” guard
: block follow actions during record/overdub on selected clips/tracks.
- Options:
Block on empty clips
,
Block on armed tracks
,
Block on manual trigger only
.
  • Scheduling & Safety:
- Quantize state changes to bar/loop boundary (optional), with
preview/HUD
showing what will be suppressed.
- Undoable, with
timeout
(auto-resume after N bars/seconds) and
panic
action to re-enable everything.
  • UI & Feedback:
- Small badge on clips/tracks when follow actions are
suspended
; global status light with quick menu (All / Color / Track / Clip / Tags).
- Inspector shows active blocks and their origins (scope, tag, condition).
  • Automation API & Variables:
- Actions:
Suspend/Resume Follow Actions (scope/tag/ID)
,
Toggle Follow Actions While Recording
,
Enable Only… (whitelist)
.
- Vars:
followActionsSuspended
,
suspendScope
,
suspendTags[]
,
isClipEmpty
,
isRecording
.
  • Backwards Compatibility:
- Existing follow actions remain unchanged; suspension layers sit “on top” and can be saved with the project or ignored per preference.
Benefits:
  • Prevents unwanted program changes or scene jumps while capturing new ideas.
  • Fine-grained control (by scope and by tag) avoids over-disabling unrelated automation.
  • Safer live workflow with clear visual feedback and quick global recovery.
  • Cleaner templates—no need for duplicate “no-FA” copies of clips/pages.
Examples:
  • Before recording into empty “Lead” clips, trigger
    Suspend Follow Actions (Color=Red, While Recording)
    so embedded program-change follow actions won’t fire.
  • Keep lighting FAs active but **disable only
    progChange
    -tagged** follow actions during a sound-design section.
  • Map a footswitch to
    Toggle: Suspend All FAs (2 bars)
    —auto-resumes after two bars to restore normal automation.
  • Per-clip switch:
    Disable Follow Actions on This Clip
    while you overdub; the global status stays unaffected.
This summary was automatically generated by GPT-5 Thinking on 2025-09-07.
Original Post:
Disable Follow Actions (Global-Colour-Clip level)
Action to disable Follow Actions on all levels.
In my scenario, I am using Follow Actions on clips to send program changes to my synths when these clips are triggered, but that is not always necessary. Sometimes I just want to record something in an empty clip without switching the sound on my synth because of the clip’s Follow Action which i am currently recording .The clip may be empty, but it is still carry the Follow Action. Being able to disable these follow actions with widgets would resolve these kinds of issues. Even better, to target multiple specific Follow Actions.