Device / OS: Quad Cortex & Quad Cortex Mini / CorOS
Category: System Architecture / Control / MIDI
1. Preset Aliasing / Pointer References Across Setlists (Linked Presets)
Current Behavior:
When adding a preset to multiple Setlists or slots, CorOS creates independent duplicate files. Any tweaks made to tone, gain, EQ, or block routing on one copy are not reflected in the others. Users must manually re-save, re-copy, or rewrite the preset across all locations.
Proposed Solution:
Implement a Preset Aliasing / Linked Preset system. When adding a preset to a Setlist, users should have the option to add it as a “Reference / Alias” pointing to a single Master Preset. Updating the master preset automatically updates all linked instances across all Setlists.
User Benefit:
Drastically reduces preset management overhead for touring musicians. Adjusting a core tone or making stage EQ tweaks will instantly update all gig setlists without manual duplication.
2. Per-Preset Custom Footswitch Mapping (Flexible Hybrid Allocation)
Current Behavior:
Footswitch layouts are bound to rigid global/hybrid modes (e.g., fixed rows or pages split equally between Scenes and Stomps). On compact hardware like the Quad Cortex Mini, this rigid split limits flexibility on a 4-footswitch layout.
Proposed Solution:
Allow Per-Preset Footswitch Reassignment. Within any given preset, users should be able to map individual physical footswitches to any function without layout restrictions (e.g., 3 Scenes + 1 Stomp, 4 Stomps, or 1 Preset Jump + 3 Scenes).
User Benefit:
Unlocks the full potential of hardware controllers—especially the Quad Cortex Mini—by eliminating arbitrary mode splits and allowing custom pedalboard configurations per song.
3. Native MIDI CC Commands for Sequential Preset Navigation (Preset +1 / -1)
Current Behavior:
Direct preset switching via MIDI currently relies on explicit Program Change (PC) messages tied to specific slot numbers. Basic MIDI controllers without state memory or counter logic cannot easily cycle through presets sequentially using a single button.
Proposed Solution:
Add dedicated global Control Change (CC) parameters for Preset Next (+1) and Preset Previous (-1) commands. Receiving this CC value should tell CorOS to advance or go back one preset relative to the currently active preset.
User Benefit:
Provides seamless, sequential preset scrolling when using simple, compact, or budget MIDI foot controllers (e.g., single-button switches or basic foot controllers) without requiring complex internal scripting on the controller side.