Trigger Mapping
Trigger Mapping is how CueForge connects cue markers to external systems. When playback reaches a marker, its mappings fire — starting another cue, sending an OSC message, making an HTTP request, or outputting MIDI. In the current 0.99.0 beta, OSC, MIDI, and HTTP triggers are verified in both directions: cues can send them, and Control Mapping can receive them to fire cues and show actions.
How a cue's markers map to trigger outputs
What it does
Trigger Mapping connects cue markers to external actions. When playback reaches a marker, its mappings fire — starting another cue, sending an OSC message, making an HTTP request, or outputting MIDI. Eight trigger target families exist, each with its own availability: Internal Cue, OSC, MIDI, and HTTP are available now. Resolume, MA3, and QLab sends are in early access — validate them in your own environment before showtime. The Timecode family uses CueForge's internal clock only; external LTC/MTC chase is planned and not part of this beta.
Why it matters
Modern productions rarely rely on a single system. Trigger Mapping lets CueForge coordinate with lighting desks, media servers, audio systems, and custom hardware — turning a single operator action into a precisely timed, multi-system event.
Typical workflows
- Add a marker to a cue at a specific time
- Create a trigger mapping for that marker
- Select the target family (OSC, MIDI, HTTP, etc.)
- Configure address, arguments, or payload
- Validate and save the mapping
- Test the cue with its Test button before showtime
Safety note
Test every trigger mapping during tech rehearsal. Network conditions and external device states can change between sessions.
Current limitations
- HTTP cues complete on transport success, not HTTP 2xx.