The MC-8 Pro currently routes MIDI exclusively through a channel-to-port mapping model. While powerful, this approach introduces unnecessary friction in modern hybrid rigs where a single footswitch action must intentionally send different messages to different physical outputs.
I recommend adding optional message-level output port selection as a firmware enhancement, while preserving full backward compatibility with the existing channel-centric routing model.
Practical limitation in real-world rigs
The current channel-centric routing model forces users into one of two compromises.
Option A: Channel explosion
Users must allocate separate MIDI channels purely for routing purposes, even when devices already use fixed or overlapping channels, or when logical grouping would otherwise favor shared channels. This increases channel management complexity, cognitive load during preset creation, and the risk of channel collisions in larger rigs.
Option B: Unintended message fan-out
When two devices require different physical connections but share a MIDI channel, messages are unavoidably duplicated across all enabled ports. This often forces users to rely on external filtering or additional hardware workarounds. The issue is amplified in hybrid setups that combine DIN MIDI hardware, USB MIDI devices, and Bluetooth MIDI targets.
Why message-level routing is needed now
Modern performance rigs increasingly rely on a single controller and a single footswitch to control multiple targets simultaneously, often across different transport layers. Common examples include a DIN MIDI looper paired with a USB-connected modeler, USB-based DAW control combined with DIN hardware effects, or Bluetooth app control alongside wired stage gear. In these scenarios, the intent is per message rather than per channel.
The MC-8 Pro already supports multiple messages per preset, independent actions per message, and rich conditional logic. What is missing is the ability to explicitly define which physical output a given message should use.
Proposed firmware enhancement
Add optional message-level output port selection. For each preset message, allow an additional Output Port parameter with the following options: inherit from MIDI channel as the default behavior, DIN MIDI, USB Device Port 1 through 4, Bluetooth, or Omniport MIDI.
Backward compatibility
Default behavior would remain unchanged. Existing presets would continue to rely entirely on channel-based routing, and message-level routing would apply only when explicitly configured.
Benefits
This approach introduces no breaking changes and does not disrupt existing workflows. It immediately reduces channel sprawl, makes preset intent clearer, and aligns the MC-8 Pro more closely with modern hybrid rig requirements.
Alignment with MC-8 design philosophy
The MC-8 Pro is positioned as a high-end programmable MIDI controller designed for complex, multi-device rigs and precise, deterministic control. Message-level routing does not weaken the channel-based model. It complements it by adding a higher-precision routing layer when needed.
Thank you
The MC-8 Pro already excels in message density and control logic. Adding message-level output routing would remove a real and present limitation without sacrificing reliability or simplicity. This enhancement would materially improve real-world usability today. Thank you for considering this request.
