member badge
ultracello
Description:
Allow users to toggle individual MIDI or Bluetooth controller instances on or off within specific project profiles using standard
actions
and
follow actions
.
Problem:
Currently, controller activation is tied to project profile structure. To manage two separate controller configurations (e.g. one Bluetooth, one wired), users must duplicate entire project profiles. For example, managing 8 setups for two controllers results in 16 total profiles. This becomes increasingly unsustainable in complex projects where many profiles are already used for other routing or behavior configurations.
Proposed Solution:
  • Add support for actions and follow actions that can enable or disable specific controller instances (e.g. “Bluetooth Controller A” or “Wired Controller B”) within any existing project profile.
  • These toggles should be exposed as mappable actions and follow action targets, ideally with controller identifiers for precise control.
Benefits:
  • Reduces the number of project profiles required for managing multiple controller configurations.
  • Greatly improves workflow efficiency and scalability in complex performance setups.
  • Allows dynamic switching of controller roles (e.g. switching between foot controller and tabletop pad) without duplicating profiles.
  • Enables context-based controller switching using gestures, MIDI triggers, or automation.
Examples:
  • A user has 8 project profiles for different performance sections. Instead of creating 8 duplicates for Bluetooth vs wired control, they assign a toggle to enable the relevant controller instance globally.
  • A follow action at the end of a performance section disables Bluetooth control and enables wired MIDI, preparing for the next segment seamlessly.
  • A MIDI pedal can toggle its own input handler on or off across all profiles it’s used in—without touching profile structure.
This summary was automatically generated by ChatGPT-4 on August 3, 2025.