Manual

Surface Mapping

Surface Mapping lets you bind MIDI notes, CCs, Program Changes, or OSC messages to CueForge2 actions globally — separate from per-cue triggers. Open it from the Window menu.

#Bindable actions

### Transport

• go — fire GO (same as space bar)
• stop — stop the active cue
• panic — full PANIC
• pause — pause playback
• resume — resume playback

### Navigation

• selectNext — move armed cue down one row
• selectPrevious — move armed cue up one row
• showModeToggle — toggle Show Mode

### Continuous (value 0.0 – 1.0)

• masterVolume — set the grand master output volume

### Cue-specific

• Fire by cue number — fires a named cue directly from a surface button
• Goto by cue number — arms (gotos) a named cue without a separate GO press
• Fire by hotkey — fires the cue assigned to a specific hotkey letter or F-key

#Binding sources

Each binding is triggered by one of:

• MIDI Note On (channel 1–16, note 0–127)
• MIDI Control Change (channel 1–16, CC number 0–127)
• MIDI Program Change (channel 1–16, program 0–127)
• OSC address — any incoming OSC path you choose (e.g. /my/button)

#Value transform

For continuous actions (masterVolume), each binding can remap the incoming MIDI or OSC value range to the 0.0 – 1.0 target range, so a fader that only travels 0–100 maps cleanly to full-scale.

#Tips

• Use Surface Mapping for physical control surfaces (MIDI faders, buttons, OSC tablets).
• Use per-cue MIDI triggers (Trigger tab) when you want a specific incoming event to fire one specific cue.
• Both systems work simultaneously.