AJ Kerezy
Description:
Add the ability to explicitly set the MIDI output channel (or channel set) used by MIDI-generating features such as MIDI Clips (loops) and MIDI One Shots, so users can control where outgoing note/CC data is sent.
Problem:
At the moment, MIDI Clips and MIDI One Shots cannot be configured to send on a specific MIDI channel. This is a significant limitation because selecting an output channel is standard practice across MIDI hardware (keyboards, pads, controllers) and MIDI-generating software (sequencers, arpeggiators, generative tools).
Without per-source channel control:
  • MIDI generated inside the app can collide with other MIDI sources (external controllers, AUv3 MIDI generators, other tracks).
  • Users cannot isolate internal MIDI for routing, filtering, or bindings.
  • Workflows that depend on "channel separation" become fragile and require messy workarounds.
A concrete use case: a simple MIDI Clip with a few notes is used to trigger button widgets via MIDI bindings. The user wants those notes to be sent on (for example) MIDI Channel 5 to avoid interfering with other notes coming from plugins or external hardware.
Proposed Solution:
1) Per-clip / per-one-shot MIDI channel setting
  • Add a "MIDI Output Channel" parameter to MIDI Clips and MIDI One Shots.
  • Support at least:
- Single channel (1-16)
- "All channels" / "Omni" (for backward compatibility and special cases)
2) Optional: multi-channel selection
  • If feasible, allow selecting multiple channels (e.g. 1+2+10) or a channel range, for advanced routing.
3) Consistent availability anywhere MIDI is generated
  • Apply the same concept anywhere the app generates MIDI notes/CC internally (e.g. MIDI clips, one shots, virtual keyboard, other MIDI emitters if present), so the behavior is predictable and consistent.
4) Safe defaults and project compatibility
  • Default existing projects to the current behavior (e.g. "All channels" or the current implicit channel behavior), so nothing breaks on update.
  • Clearly display the selected channel in the relevant editors and inspectors.
Benefits:
  • Proper channel isolation for complex rigs and multi-device setups.
  • Prevents unintended MIDI interference between internal MIDI, AUv3 MIDI generators, and external controllers.
  • Enables cleaner routing, filtering, and bindings (especially for performance control schemes).
  • Aligns with established MIDI standards and user expectations.
Examples:
  • Widget triggering without collisions:
- A MIDI Clip sends four notes on Channel 5.
- MIDI bindings listen only on Channel 5, so external keyboards (Channels 1-2) do not accidentally trigger widgets.
  • Multi-instrument routing:
- One Shots on Channel 10 trigger a drum module.
- MIDI Clips on Channel 2 trigger a bass synth.
- Live keyboard on Channel 1 stays independent.
  • Template reliability:
- A performance template project uses dedicated channels for internal automation clips (e.g. Channel 16).
- Copying the template preserves channel discipline and prevents setup drift.
This summary was automatically generated by GPT-5.2 Thinking on 2025-12-27
.
Original Post:
Sadly.... right now, you CANNOT specify which channel or channels a MIDI Clip (loop) or MIDI One Shot - broadcast, or sends MIDI data /notes out on. Very Sad
STANDARD of PRACTICE: Pretty much EVERY MIDI generating plugin or software (Harmony Bloom, Rozeta, etc.) and EVERY MIDI generating hardware, like keyboards of all types, drum pads, etc. --- they ALL let you specific or setup which MIDI Channel(s) to send MIDI out on.
RATIONALE: Since LP is not following the standard or best practice.... that should be enough itself. HOWEVER.... use case: I have a MIDI Clip (loop) with 4 simple notes, that I created in the LP Editor. I will use these 4 notes to trigger button widgets, via a MIDI binding in the control profile. I want these 4 MIDI notes sent out on MIDI Channel 5 so as not to interfere with any other MIDI notes - from plugins (MIDI generators) or physical keyboards, or physical drum pads.
REQUEST: In any place in LP where MIDI can be generated, e.g. MIDI clips (loops), MIDI One Shots, Virtual Keyboards .... (did I miss anything ?) ; add functionality in the software to let the user setup which MIDI channel the MIDI is sent out on.