Integrations
Route OSC into and out of a lighting graph
OSC is addressed messages on a network. WavePhase can take OSC into the graph (Artist+) and send OSC out. Structure a stable address tree and document it for anyone else touching the rig.
Who this is for
Houses that already have TouchOSC, a show-control PC, or another app that should talk to lighting without becoming a second desk.
Who it is not for
Operators who only need a phone blackout — Web Control or MIDI is simpler and available on more tiers.
Addressing and topology
Name a tree and freeze it
Pick addresses such as /wash/dimmer and /heads/spread. Changing them mid-season breaks every tablet on the gig.
Map ranges once
Normalize incoming values into 0..1 fixture channels. Do not leave raw 0–127 sitting next to 0–1 DSP pins.
Independent kill
Keep a MIDI or Web Control blackout that does not depend on the OSC sender staying alive.
Implementation facts
- Availability
- OSC unlocks on Artist and above in the current pricing grid.
- Direction
- OSC in to the graph; OSC out when another system needs WavePhase values.
- Network
- Same wired show LAN as Art-Net/sACN. Do not bounce OSC across public Wi-Fi for cue-critical looks.
OSC mapping
- 01Pick addresses such as /wash/dimmer and /heads/spread.
- 02Map ranges into 0..1 fixture channels.
- 03Keep a MIDI or Web Control kill independent of OSC.
- 04Write the address list into the show folder so the next operator is not guessing.
When OSC fits — and when it fails
Tablet bank
TouchOSC-style surfaces into the same pins as Live Control.
Show-control PC
Another app already speaks OSC — do not invent a second lighting program.
Port and firewall
Wrong UDP port or a laptop firewall looks like a dead sender. Confirm listen address before you rewrite the graph.
Docs and guide
Limitations and transparency
OSC is only as stable as the sender and the LAN. A crashed tablet is not a WavePhase bug.
FAQ
Free account required — no credit card — Windows, macOS and Linux.