Nodes & Signals
External I/O
WavePhase doesn't live in isolation. Bring values in from OSC, MIDI, DMX, timecode, and an HTTP/MCP API — and send OSC and DMX back out — so it fits into any rig or software setup.
Inputs
OSC In
MIDI In
DMX In
6454) as a 0..1 or raw 0–255 — take control from a console.Timecode In
API In
MIDI learn
The fastest way to bind a physical control: add a MIDI In node, put it in learn mode, then move the fader or press the button you want. WavePhase captures the message and maps it automatically.
Hands-on control
MIDI faders are perfect for a live master dimmer, manual color, or a "panic" blackout — wire them alongside your music-reactive signals for the best of both.Outputs
- OSC Out — send OSC messages (float, int, string, or a trigger shape) to other software and hardware.
- DMX Out — send a single DMX channel via Art-Net or sACN.
- Fixture Out — send a full multi-channel fixture (see Patching).
- Web Control — a browser-based control surface (covered in Controlling Fixtures).
Using WavePhase as a hub
Because it receives OSC, MIDI, and DMX — and sends OSC and DMX — WavePhase can sit in the middle of a rig: take audio analysis in, blend it with console or DAW control, and fan the result out to lights, media servers, and other software — all from one patch.
Default OSC port
OSC input listens on a configurable UDP port (commonly8001). Set the address pattern on the OSC In node to match what your sender is emitting.Driving a patch from software? See the lighting control API.