Soi
Description:
Expand the “Load Project” action with dynamic target pickers (Project Browser, specific Folder, Setlist, Recent), plus a one-tap “Reload Current Project” option. Show the chosen target inline on the action row for clarity.
Problem:
Performers who choose songs on the fly can’t easily pick a project at trigger-time. Current options (specific/next in folder or setlist) don’t cover ad-hoc choices, and the action row doesn’t display which project it targets—making large libraries of bindings hard to audit. There’s also no direct way to quickly reload the currently open project.
Proposed Solution:
  • New Target Modes:
-
Project From Browser…
→ Open project browser, user selects, then the action executes.
-
Project From Folder…
→ Jump straight into a chosen folder to pick a project.
-
Project From Setlist…
→ Jump straight into a chosen setlist to pick a project.
-
Recent Project…
→ Present the system’s “Recent Projects” list.
-
Reload Current Project
→ Instantly reload the project in memory.
  • Inline Target Label:
    The action row shows the resolved target (e.g., “Load Project → Recent:
    Ambient Swell
    ” or “Folder:
    Dance Set
    ”).
  • Quantize & Behaviors:
    All picker modes honor existing “Load Project” behaviors (copy mixer levels, start clock, quantization, bindings).
  • UX Options:
    Optional “cue then commit” flow; allow footswitch mapping to open picker, confirm on second press; remember last selection per action (configurable).
  • Safety:
    Undo/confirm for reload; keep engine-safe transitions as today.
Benefits:
  • Flexible, on-the-spot song selection without losing the advantages of the action (clock/quantize/level copy).
  • Faster navigation during shows; fewer duplicated bindings.
  • Clearer projects with visible targets on action rows; easier troubleshooting.
  • A single tap to refresh the current project for a clean slate.
Examples:
  • A “Choose Next Song” button opens
    Setlist: Tonight
    ; you pick any track and it loads at the next quantized boundary while copying mixer levels.
  • A “Dance Mode” button jumps to
    Folder: Uptempo
    so you can keep the floor moving, then auto-starts clock.
  • A “Recent Project…” binding recalls something you rehearsed earlier without digging through folders.
  • A footswitch bound to
    Reload Current Project
    resets the template mid-rehearsal.
  • In the actions list, items now read “Load Project → Folder:
    Ballads
    ” so targets are obvious at a glance.
This summary was automatically generated by GPT-5 Thinking on 2025-08-25.
Original Post:
More target options for “Load Project” action
Within the “Load Project” action, it would be great to have the following target options:
1) “Project From Browser…”
In this case, activating the action would open the project browser. Then the user could choose which project to load, and once they do, then the action would execute. It would be a bit like actions that target “next tapped clip”, but for projects rather than clips.
2) “Project From Folder…”
Similar to above but instead jumps straight into a folder to select a project from
3) “Project From Set List…”
Similar to above but instead jumps straight into a set list to select a project from
BENEFITS
Performers who prefer to choose songs in the moment rather than from a pre-planned set list can still enjoy the benefits of the “Load Project” action like:
-Copy Levels
-Start Clock
-Quantization
-Triggering via widget or binding
-Etc.
EXAMPLE
I could have a “Choose Next Song” button that brings me to a folder or set list with all of the songs that I might play at this gig. Whichever one I choose will load and it will copy mixer levels.
Later if people are dancing and I want to keep them on the dance floor, I could press a “Choose Next Dance Song” button which could bring me to a folder or set list with only the danceable songs from my repertoire. And I could do it while the first song is still playing and have it quantize and start clock automatically so I don’t skip a beat getting into the next song.