MIDI Integration
Send MIDI from CueForge cues, and receive MIDI into CueForge via Control Mapping.
CueForge supports MIDI in both directions: MIDI Cues send messages to external equipment, and Control Mapping receives MIDI to fire cues and show actions.
Sending MIDI from CueForge
A MIDI Cue sends a message when it fires in the show:
- Output Profile and Output Device
- Message types: Note On, Note Off, Control Change (CC), Program Change (PC)
- Channel 1–16 and the data fields for the chosen message type
- A Test Send button in the cue editor fires the message immediately
Typical targets: synthesizers, samplers, lighting desks with MIDI input, playback hardware.
Receiving MIDI into CueForge
CueForge receives MIDI through Control Mapping. Enable the MIDI listener in Settings → Triggers & Control (choose the input device), then open Window → Control Mapping to author mappings from incoming messages to cue actions or global show actions. Unassigned incoming messages appear in the Trigger Inbox for triage.
Note: Note On and Note Off are treated as distinct controls — pressing and releasing a key can map to different actions. Receiving is verified with real software sources; hardware controller profiles are implemented but still awaiting physical validation sessions.
See Control Mapping and the Trigger Inbox for the full authoring workflow.
Profiles for controllers such as the Akai APC Mini MKII, Allen & Heath SQ, and SoundSwitch Control One are implemented and unit-tested, but physical validation on the real hardware is still in progress. Do not assume controller behaviour until it has been verified in your venue.
Requirements
- For sending: a MIDI output device recognised by the operating system, the target set to receive on the correct channel
- For receiving: a MIDI input device recognised by the operating system and the listener enabled in Settings → Triggers & Control
Test procedure
- For sending: create a test MIDI Cue with a simple Note On and use its Test Send button; confirm the target responds.
- For receiving: enable the listener, create a mapping with Learn, and operate the external controller — or use the Trigger Inbox’s Test on a proposal.
- Only after both directions behave, build production mappings.
Show safety notes
- Avoid duplicate mappings that could trigger unintended devices.
- Verify the MIDI device is connected and recognised before every show.
- Label every mapping with its target device and channel.
- Do not rely on MIDI alone for safety-critical functions.
Current limitations
- No MIDI clock sync.
- Hardware controller profiles are pending physical validation.