Console integration

The console calls the show.
The plot keeps up.

Spotlight Maestro listens to your console's own show control output: ETC Eos, grandMA2 and grandMA3 are all supported. When the desk fires a cue, every device in the venue scrolls to the matching spot cue. No exports, no pairing, no assistant keeping a manual document up to date.

The show's cue list on an ETC Eos console display

Scene 4 · What console tracking actually means

Active 1

Your cue numbers, exactly as you write them

Each spot cue carries a console cue reference in free text. Write 287, LX42.5, w/ 18 or in 294.4: the app reads the number out of whatever you wrote. When a cue fires with no spot cue of its own, the plot holds on the last spot cue at or before it, so operators always see the instruction they are holding.

Tracking is per device, on purpose

Every operator's screen keeps tracking while the caller wanders the plot with tracking off on their own device. Tap any cue and that device takes manual control, marked plainly with a MANUAL badge; the next console cue puts it back in sync automatically.

Built for real systems

Point the app at the main console's address and cue list, and it ignores the backup desk, or any console parked on a checklist. Multi-part cues are read correctly, a Go To Cue back to the same number still moves every screen, and a console cue never yanks the plot out from under someone typing in it.

You can see what the console is saying

The status pill knows connected and receiving from connected but hearing nothing. A live monitor shows the last sixty messages exactly as they arrived, marked matched, filtered or skipped. Send Test Cue fires a cue number with no console attached, which is how a plot gets checked before it ever reaches the theatre.

Follow: one driver, every screen.

Tracking the console automates the plot; Follow gives the spot caller control. One person steps through the show from the master plot or the calling script and every connected screen moves with them. Great for manually calling spot cues independently of the console, or without a console at all. One driver at a time, named on every toolbar, and the console takes back control the moment tracking is reinstated.

The toolbar with Follow engaged: the amber Follow pill lit beside the console status — Follow engaged · the amber pill, lit on every screen in the venue

Pick your desk in Settings.

The console type is one dropdown in Settings, Console Sync. The tracking, the manual override, the monitor and the test tools work identically on all of them.

Console Sync · Eos

ETC Eos family

Eos Ti, Gio, Ion, Element, Apex and ETCnomad. Enable OSC RX and TX in Setup, System, Show Control; the app connects to the console and subscribes. A main console address and main cue list filter keep backup desks out of the plot.

Console Sync · grandMA2

grandMA2 and dot2

Followed over MIDI Show Control on Ethernet, no MIDI hardware involved. On the console: Setup, Console, MIDI Show Control, with MSC Out set to Ethernet, Exec.Page and Command Format All. An executor filter keeps the plot on the show's executor.

Console Sync · grandMA3

grandMA3

grandMA3 sends no show control over MIDI on the network, so the app follows its OSC output instead. On the console: Menu, In & Out, OSC, one output line pointed at the host machine with Send on. A sequence filter keeps the plot on the show's sequence.

The evidence, on screen.

Show control failures are difficult to debug. The live monitor shows every message as it arrives, before any filtering, and names the filter that discarded anything it skipped.

Send Test Cue injects a cue number as though the console had fired it, so the plot has to find it by the console cue numbers written in the show. That is the honest test, and it needs no console in the venue.

The live console message monitor — The live monitor · every message, tagged

And the plot can sit on the console screen.

The app serves the live plot, or a spot summary strip, as a standard video stream for a console's video tab or magic sheet, or any other device that accepts an RTSP stream. The plot on the console screen: no other followspot tool does it.

An Eos display in cue 282: the Spotlight Maestro spot summary strip placed as a magic sheet item beside the lighting rig — An Eos screen, live in cue 282 · the summary strip as a magic sheet item, right on the rig

The call on the show recording.

From Settings, Connections, the app feeds VOR (getvor.app) and KoalaCue (koalacue.com) live text for its video overlay: the calling line word for word, each spot's own instruction, and a running summary per spot. Point your camera at the stage and every recording captures the spot cues, so watching back a performance shows exactly what was done at every moment.

A VOR recording of the stage: the LXQ282 calling line across the top, each spot's summary down the left, and the Eos cue text below — A VOR recording · the calling line, the spot summaries and the console cue, burned in live

The technical corner.

The connection facts, per console. The manual has the full step by step setup for each.

Console	Protocol	Connection
ETC Eos family	OSC. TCP recommended, OSC 1.0 and 1.1 framing both supported, or UDP with the console transmitting.	Network. TCP port 3032 by convention.
grandMA2 / dot2	MIDI Show Control over Ethernet, received directly off the network. Acts on GO and TIMED GO.	Network. UDP, port 6004 by default, with device and executor filters.
grandMA3	The console's OSC sequence output. Acts on Go+, Goto, Top, Load and On.	Network. UDP, port 8000 by default, with a sequence filter.