ETC Eos vs GrandMA3 for Audio-Driven Automation

Both Are Good, Which Makes This Harder

Comparisons are easier when one option is compromised. This one is not: Eos and GrandMA3 both expose a native OSC surface, both accept discrete cue firing and continuous level control, and both report state back so a controller can stay aligned with what the operator is doing.

So the useful comparison is not "which is better" but which idiom matches your show, and that turns out to be a more decidable question.

The Structural Difference

Eos is cue-list-centric. A show is a sequence, and the operator advances along it. Go, back, a cue number, a follow time. This is how theatre thinks, and it is not an accident that Eos dominates theatre.

GrandMA3 is executor-centric. A show is a set of parallel playbacks brought in and out at varying levels. This is how concert, festival and event work thinks, where several elements run simultaneously and independently.

Neither is a limitation. But they produce different natural mappings when a controller starts firing things:

The Command Surfaces

Eos takes the standard /eos/ surface: /eos/key/go_0 for Go, /eos/cue/<list>/<number>/fire for a specific cue, /eos/chan and /eos/sub/<number> for levels, /eos/macro/<number>/fire for macros. Submasters take a float argument, which maps directly onto an energy envelope.

GrandMA3 takes OSC over TCP or UDP, driving cues, executors, faders, fixture groups and macros. The executor model means several continuous parameters running at once is the ordinary case rather than something you arrange.

Both are enabled from the console with no plugin and no middleware. On Eos that is Setup → System → Show Control → OSC.

What Actually Decides It

In practice the protocol surface is rarely the deciding factor. Three things usually are:

The room. Many venues already own one. Automating the console that is bolted into the building beats specifying a better one that has to be hired.

The crew. A console nobody available can program is the wrong console, regardless of how well it automates. This is the factor most often underweighted in a spec document and most often decisive in the building.

The repertoire. A house doing book musicals and a house doing music-led events will diverge on this even with identical budgets, and both will be right.

If none of those settles it, the idiom question above is a reasonable tiebreaker — but it is a tiebreaker, not the main event.

Reading State Back

Both consoles publish state, and using it is not optional for a controller that intends to coexist with an operator.

Eos publishes the active cue on /eos/out/active/cue/... and the show name on /eos/out/show/name. GrandMA3 has an equivalent OSC-out configuration.

A controller firing cues blind accumulates a belief about console state that drifts from reality the moment anyone touches the desk — and on a real show, someone always touches the desk. CueSync reconciles against these feeds on both consoles for exactly that reason. A controller that skips this will eventually fight the operator, and the operator will win, loudly.

One Honest Caveat

CueSync's Art-Net / sACN DMX-over-IP output is experimental beta and has not been verified on hardware. It should not be load-bearing on a show.

Command control over OSC is the production-ready path on both consoles, and it is also the architecturally correct one: firing cues and executors keeps the console's programming intact, whereas pushing DMX levels directly bypasses the desk that someone spent a week programming.

Further Reading

• How to Trigger ETC Eos Cues from Live Audio — the Eos command surface in detail
• How to Send Timecode to GrandMA3 — the GrandMA3 timecode path
• QLab or GrandMA3: Which One Should Be Master? — the adjacent architecture question
• ETC Eos Integration · GrandMA3 Integration

ETC® and Eos® are trademarks of Electronic Theatre Controls, Inc. GrandMA® is a trademark of MA Lighting Technology GmbH. CueSync is an independent product and is not affiliated with or endorsed by either.