Phase 2: add user mapping profiles with follow and sticky track binding #7
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal\nMake multi-controller orchestration configurable without changing semantic device definitions.\n\n## Scope\n- Persist per-surface mapping profiles.\n- Support follow-selected-track and sticky-track binding for controllers.\n- Allow referential parameter behavior relative to active track/runtime state.\n- Keep raw MIDI mappings separate from OPSL semantic parameter truth.\n\n## Acceptance criteria\n- A MIDI keyboard can follow Push track selection or remain attached to a chosen track.\n- Profile changes are persisted and restored.\n- Conflict and ownership behavior is documented for multiple controllers targeting one parameter.\n- Tests cover follow, sticky, rebinding, and referential updates.\n\n## Non-goals\n- A broad visual remapping editor in the first implementation.