T
Teemu Paavolainen
Description:
Introduce folder-based organization for Project Control Profiles, allowing users to group and manage profiles by controller or category within the profile list.
Problem:
Currently, all Project Control Profiles appear in a single flat list. Even managing two controllers becomes cumbersome, as users must manually create lists of profile options for widgets, replicate those lists across widgets, and keep everything synchronized. This process is error-prone and time-consuming, especially when adding new profiles.
Proposed Solution:
Enable folder support in the Project Control Profiles list. Each folder can represent a controller or category, containing its associated profiles. Widgets referencing profiles within a folder automatically inherit the relevant context, and newly added profiles within that folder become available without requiring manual updates to every widget.
Benefits:
  • Simplified profile management for multiple controllers.
  • Reduced manual duplication and maintenance of profile lists.
  • Faster setup of widgets with the correct context already available.
  • Easier scalability when adding new controllers or profiles.
Examples:
  • Folder “Launchpad X” contains profiles for different modes; widgets automatically show only Launchpad X options.
  • Folder “Foot Controller” holds expression pedal and switch mappings; adding a new profile immediately makes it available to related widgets.
  • Teachers and performers can quickly switch between controller setups without wading through an unsorted global list.
This summary was automatically generated by GPT-5 Thinking on 2025-08-20.
Original Post:
With all Project Control Profiles now in one list, it soon becomes very cumbersome to manage even two different controllers: To make widgets for selecting just one profile at a time for each device, you'll have to manually create a list of options from which to make the relevant selection, and then copy that list to all other similar widgets. With something like folders for different controllers in the Project Control Profiles list, you'd have the relevant context always ready, AND could add new profiles in those folders without having to manually update each controller-specific listing wherever you've scattered them.