Solutions
Automate DMX from audio, time, control surfaces and APIs
Automation in WavePhase is a set of clocks you can mix: live audio DSP, local-time schedules, sequences and timecode, API/MCP, OSC/MIDI/DMX input, Web Control, and manual fallback. You are not required to pre-author every possible track, and you are not stuck with audio as the only driver.
Several automation clocks, one patch
- 01Audio DSP and beat for reactive nights.
- 02SMPTE/MTC or sequences when the show must be rehearsed.
- 03Local time for installs that change by hour or day.
- 04API/MCP, MIDI, OSC, or DMX input when another system is in charge.
- 05Web Control and Show Lock for operators and unattended kiosks.
Automation modes
Live audio DSP
Booth feed drives the dancefloor look while the door is open — kick accents, bass-band dimmer, beat-locked chases.
Timecode / sequence
Playback night: looks lock to MTC or SMPTE so video and lights scrub together in rehearsal.
Scheduled / local time
House wash at opening, last-call look at close — Local Time sources, no one sitting at the desk.
API / MCP
A booking app or agent posts a look-change trigger into a source node (Pro+).
MIDI / OSC / DMX input
Resident tech hits a pad for blackout; a visiting desk can merge on paid tiers while WavePhase holds the reactive layer.
Automation examples
Venue open / close
Local Time sources switch looks at opening and last call without anyone sitting at the desk.
Playback show
Lock looks to timecode so video, audio, and lights scrub together in rehearsal.
Agent or app trigger
An external program posts a typed value into the patch over the HTTP API or MCP (Pro+).
Desk merge
Paid tiers can take DMX input so a visiting console overrides while WavePhase holds the reactive layer.
Documentation
FAQ
Free account required — no credit card — Windows, macOS and Linux.