Runs a user macro stored on the console.

What the macro does is whatever was recorded into it at the desk; this server cannot see its contents, so ask the user what a macro number does rather than guessing from its number.

Sets the grand master level, optionally fading to it.

The grand master scales the entire rig, so this is one of the few commands here that can black out a show on its own. Confirm before sending it during a performance.

Turns the console's blackout on or off.

ZerOS accepts several spellings for the argument ("1", "on", "true" and so on); this sends "1" and "0", which are the least ambiguous.

Fires a specific cue.

Naming the playback is the clearer call, but the cue-only form is worth knowing about: an FLX S48 user reported the playback-qualified address being ignored where the cue-only one worked. If a cue will not fire, try omitting the playback before concluding the console is not listening.

Presses Go, advancing to the next cue.

With no playback given this drives whichever playback the console currently considers active, which this server has no way to know. Naming the playback is the safer call whenever you know which one you mean.

Sets which cue is next, without firing it.

This is ZerOS's "Next" command. Use it to jump the standby cue somewhere else in the stack, then go_cue to run it.

Pauses a running fade.

Releases a playback, returning the channels it holds to the stack below.

Brings a playback into view on the console's screen.

Changes what the operator sees and nothing about the lighting output.

Sets a playback's fader level, optionally fading to it.

Omitting the fade time is not the same as fading in zero seconds: ZerOS then uses the playback's own raise and lower times, moving rather than snapping. Pass fade_seconds=0 if you want an instant change.

Reports what can be determined about the link to the console.

How much that is depends entirely on the transport. Over TCP a connection either establishes or it does not, which is real evidence. Over UDP there is none to be had: nothing is ever returned, and a successful send only means the packet left this machine.

Either way, a healthy link is not evidence that any individual command was understood. ZerOS acknowledges nothing.

Returns what this server has sent to the console.

This is your own history, not the console's state. Every entry means "this message left this machine"; none of them means the desk received it, acted on it, or is still in that state. Someone may have moved a fader by hand a second later and this server would never know.

Use it to retrace what you did, never to answer what the rig is doing.