OSC: Difference between revisions

From CUADC Wiki
Jump to navigation Jump to search
(Created page with "'''OSC''' (short for '''Open Sound Control''') is a protocol for networking together a wide variety of computer-controlled devices for the purposes of managing a performance and providing show control. OSC is generally considered more modern and far superior to the older MIDI/MSC protocol. It is also easier to deal with, being carried in simple UDP packets that can be routed or switched over a conventional layer-3 or layer-2 IP network (that is to say, it uses standa...")
 
m (categorising)
 
Line 33: Line 33:
* CCC in this case maps to the name of the cue (case sensitive) in the QLab stack - e.g  1 or S1, S6, P1 etc.
* CCC in this case maps to the name of the cue (case sensitive) in the QLab stack - e.g  1 or S1, S6, P1 etc.
</pre>
</pre>
[[Category: Sound]]
[[Category: Lighting]]

Latest revision as of 20:17, 9 September 2022

OSC (short for Open Sound Control) is a protocol for networking together a wide variety of computer-controlled devices for the purposes of managing a performance and providing show control. OSC is generally considered more modern and far superior to the older MIDI/MSC protocol. It is also easier to deal with, being carried in simple UDP packets that can be routed or switched over a conventional layer-3 or layer-2 IP network (that is to say, it uses standard computer networking equipment).

When to use OSC

It is often useful to connect QLab to other devices in the theatre (e.g. the sound and lighting desks) in order to automate cues and reduce the number of operators required. Common scenarios include:

  • A mainshow wants to avoid stitching a sound op for each performance; they link QLab to the lighting desk so that when certain LX cues are triggered, the corresponding sound effect(s) follow suit.
  • A complex musical might have a similar set-up above so that the sound op can concentrate on the mix without having to pay attention to SFX cues.
  • A complex touring show, which is performing the same set of cues at multiple venues, creates a QLab file which contains OSC cues; this can be used to remotely control whatever lighting desk is present at each venue.
  • A lateshow with a very small technical team creates a QLab show file which contains audio cues & OSC cues; QLab is run from the stage manager's desk with no additional ops.
  • A show has a sequence of lighting and sound effects that must be precisely synchronised (e.g. thunder & lightning).

EOS/QLab Setup

Setup>Show>Show Control (or Setup>System>Show Control>OSC):
OSC TX = Enabled
OSC TX IP Address = 10.41.1.115
OSC TX Port Number = 53000

ECU>Settings>Network>Interface Protocols:
OSC = TCP Format for OSC 1.1

Then on a cue, enter the following on the command line:
Cue NNN Execute String /cue/CCC/start

(On EOS both Execute and String are bottom right softkeys)

Note:

* NNN is the EOS cue you want to sync with QLab
* CCC in this case maps to the name of the cue (case sensitive) in the QLab stack - e.g  1 or S1, S6, P1 etc.