Where and why we use OSC
OSC (Open Sound Control) has been with us for many years across very different productions. We like to use it when we want to control a system from a distance without being cabled to the machine, or when different devices need to talk to each other.
Typical uses
A media server in the basement
Large productions and permanent venues often put the media server somewhere you can’t reach from the auditorium. With OSC, one network command is enough and the clip plays.
QLab and video
Many shows use QLab as the audio or timing master. With OSC, QLab can drive a media server just as cleanly as an audio cue. Ports and commands are in controlling QLab via OSC.
Lighting and playback
An ETC Eos or an MA desk can trigger QLab directly, or the other way round, and with OSC that is surprisingly straightforward. We describe how this works with a ChamSys desk in controlling ChamSys from QLab, and the other direction, from an ETC Eos, in triggering QLab from Eos.
Keeping several systems in sync
When sound, video and lighting have to react together, OSC is often more flexible than MIDI, because you can send unambiguous messages with parameters to different devices. We’ve done it this way for years once a show is set and goes on tour: one GO, and lighting and audio run in sync.
Where OSC is strongest
For us, OSC is at its best when you want to send clear, simple commands over a defined network connection, wherever the devices are. Or when FOH on a small production is networked and one technician runs everything.
That was one of the reasons we eventually decided: if we’re going to build a controller like the FrenschPress, it should speak OSC directly, with no extra software and no detours.