The client I’m working for is so bad at calling lighting cues, it’s comical. It isn’t rocket science!
“Standby LX [number]. (~10-20 seconds gap) LX [number] Go.”
Or, if cues are too fast for that: “Standby LX [number] through [number]. (Gap) LX Go. Go. Go. Go. Go. Go...”

By having a standard format, a good operator can hit the button on the ‘G’ of ‘go’ every time, by anticipating the rhythm, and with muscle memory.

Meanwhile, tonight, I have heard:
“Lights change!”
“Go next cue”
“Lights cue”
“(2 minute silence) ... go”
“Lights next cue go please”
“Cue go”
“Go cue”
“Bows go”
“Blackout now”
“Go” (but someone else talking, not actually a real go, causing a cue to be triggered early)

Another important part — if you’re discussing a ‘go’ cue on comms, not actually triggering one, you always use “gee oh” instead to refer to it, like an escape sequence. This is to prevent any unintended cuing.
Similarly, “stop” in case of an emergency is repeated three times, a bit like mayday in aviation.

Follow

I will say I’m definitely enjoying the contemporary dance stuff a lot more than I expected from working on ballets before.

Sign in to participate in the conversation
Cathode Church

A place for trans makers, coders, tinkerers and dreamers.