T
Toinooz
Description:
Introduce a way to capture the current state of all actively playing clips. This would allow users to later reference this state in clip actions, enabling operations such as start, stop, solo, clear, or stretch — even after other unrelated actions have occurred.
Problem:
Currently, there is no way to recall which clips were playing at a certain moment. This limits the ability to create dynamic, modular setups where a specific configuration of playing clips can be restored or acted upon later in a performance.
Proposed Solution:
  • Add "Currently playing clips" to the list of parameters that can be stored.
  • Allow actions on clips to target stored lists such as "previously playing clips" or "stored playing clips list".
Benefits:
  • Enables restoration of clip states during live performance.
  • Supports advanced workflows that rely on clip state memory.
  • Provides more modular control in complex projects.
Examples:
  • A performer triggers a scene of clips, then moves on. Later, they press a button to instantly bring back that same clip configuration.
  • Actions like "solo all clips that were playing at moment X" become feasible.
This summary was automatically generated by ChatGPT-4 on 2025-06-05.
Original Post:
The idea is to store the state of the currently playing clips, so they can be used in a clip action later on for either start, stop, solo, clear, stretch, etc, even after multiple other actions have occurred.
A simple way to do this would be to add "Currently playing clips" to the list of saved parameters, and add "previously playing clips" or "stored playing clips list", in the target of the actions on clips.