Input Triggers
Input triggers make the DMX Core 100 react to the outside world — a DMX channel crossing a threshold, an OSC or MQTT message, an HTTP request, a contact closure. A trigger either runs an action (play a cue, apply a preset, run a script) or drives a level directly from the signal’s value.
Input Types
| Type | Description |
|---|---|
| Art-Net / sACN | A DMX channel in an incoming network stream reaching a threshold |
| DMX Serial | A DMX channel on the optional DMX-512 board’s input |
| OSC | An OSC message on the configured address |
| MQTT | A message published to an MQTT topic (requires the MQTT integration) |
| HTTP | An HTTP request to a path you define (e.g. /hooks/party-mode) |
| TCP / UDP | Raw data arriving on a TCP or UDP port |
| Digital Input | A physical contact closure / GPIO input |
| Control Value | A Control Value changing on the DSP side — a Q-SYS or Symetrix button, fader, or selector |
Control Value Triggers
A Control Value trigger makes the DSP the source: a wall panel button wired to a Symetrix controller plays a cue, a Q-SYS UCI fader crossing a threshold starts a scene. Pick the Control Value to watch; the remaining settings depend on its kind:
- Toggle — fires when the control turns on.
- Level — set a Threshold %; fires when the level rises to or above it, and re-arms when it drops below.
- Selector — set a Start Choice (choice name or index); fires when that choice becomes active. An optional Stop Choice controls what clears the triggered state.
Only changes made on the DSP side fire the trigger — changing the same Control Value from the DMX Core 100 itself (a custom menu slider, a schedule, another trigger) updates the state silently. On startup or reconnect the first reported value arms the trigger without firing, so a control that is already on never replays its edge.
In Value mode, the Control Value’s live 0–100% position drives the target level instead — turning any DSP fader into a live lighting fader.
Two Modes
- On/Off — run an action. The trigger fires its action when the signal arrives (or crosses the threshold).
- Value — set a level from the payload. The numeric payload drives a target level continuously — a Control Value (e.g. a Symetrix volume), the master dimmer, or a zone intensity. A wall fader sending OSC or DMX becomes a live level control.
Value-mode triggers can name a Transform Script that reshapes the normalized 0–1 value before it lands — response curves, dead zones, thresholds.
Actions
An On/Off trigger can: Apply Ambient Preset, Apply Preset, set/step a Control Value, Fade Out, Fire Output Event, Play Cue, Play Sound, Play Timeline, Run Script, Step Effect, Stop Playback, Tap Tempo, Toggle Mute, Toggle Output, or Toggle Schedule.
For complex logic — conditions, sequencing, payload parsing — use Run Script: the raw payload arrives in the script as ctx.payload.
Press Modes
Actions that respond to a button-like signal have a Press Mode:
| Mode | Behavior |
|---|---|
| Normal | Fires the action on each press |
| Toggle on/off | First press starts, second press stops |
| Flash (hold) | Active only while held — the preset applies on press and releases on release |
| Momentary (release continues past Hold) | For Play Timeline actions: press plays the timeline, release continues it past a Hold milestone |
Momentary is the timeline counterpart to Flash — but where releasing a Flash button turns its preset off, releasing a Momentary button lets the timeline continue. It’s how a tap handle, doorbell, or held button drives an interactive show: pull to start, hold to keep it going, let go to move on.
With a Normal-mode Play Timeline action, pressing again while the timeline waits at a Hold also continues it — press to start, press again to continue.
Trigger Settings
- Code — unique identifier (checked for duplicates)
- Name — display name
- Enabled — turn the trigger on or off without deleting it
- Address — the OSC address, HTTP path, MQTT topic, port, or channel to match
Recording Triggers
Starting a recording from an external signal is configured on the Record page itself, as part of the recorder configuration.