Description:
Add context-aware actions to move to the
next/previous project in the currently active setlist
, so a single mapping (e.g., a footswitch) works regardless of which setlist is loaded.
Problem:
Today, navigation buttons can target “next/previous project” only within a
specific
setlist. Reusing the same projects across multiple setlists forces users to reconfigure buttons for every occurrence, creating duplicated work and increasing the risk of errors in live situations.
Proposed Solution:
  • New actions:
    Setlist › Next Project (Active Setlist)
    and
    Setlist › Previous Project (Active Setlist)
    .
  • Options per action:
-
Wrap-around
(stop at ends or loop).
-
Skip
disabled/hidden items.
-
Mode:
Cue
(preload and wait) vs
Load now
(immediate switch).
  • Additional actions/variables:
-
Jump to Project by Offset/Index
within the active setlist.
- Expose
currentProjectIndex
,
projectCount
,
isFirst/isLast
,
currentProjectName
for labels/LEDs/logic.
-
OnProjectChanged
event for updating UI and resetting per-project state.
  • Backward compatible; existing setlist-specific mappings continue to work.
Benefits:
  • One reusable mapping works across all setlists—no per-setlist reconfiguration.
  • Faster, safer set navigation on stage (ideal for foot controllers).
  • Clear feedback (index/name) for performers and techs.
  • Less template duplication and fewer chances for mismatched buttons.
Examples:
  • A dual-footswitch: left =
    Previous Project (Active Setlist)
    , right =
    Next Project (Active Setlist)
    ; HUD shows “3/12 •
    Ambient Drone B
    ”.
  • Use
    Cue
    mode to preload the next project silently; a second press (or
    Load Now
    ) commits the switch without dropouts.
  • Bind a “Jump by Offset -2/+2” for skipping interludes while keeping mappings identical across different setlists.
This summary was automatically generated by GPT-5 Thinking on 2025-08-20.
Original Post:
Select the next/previous projet in current setlist
Currently, it’s possible to assign a button to move to the next/previous project in a specific setlist. However, it would be much more useful if we could assign a button to switch to the next/previous project within the active setlist. I often reuse the same projects in different setlists, and each time I have to reconfigure the buttons for every project involved.