Guides4 min read
grandMA3 Session Sync vs MSC and OSC for Theatre Calling
Move a Theatre cue list between CueSync and grandMA3 without re-storing looks, and choose when Session Sync, OSC or MIDI Show Control fits.
CueSync TeamShow Control Engineers
Three Ways CueSync Talks to a grandMA3 in Theatre
On a scripted show, "syncing with the lighting desk" means two separate jobs that happen at different hours of the day. During tech and notes, you want the stage manager's cue numbers, labels and follow or timecode positions on the desk without typing them twice. During the performance, you want each GO or timecode frame to fire the right cue cleanly.
CueSync separates those jobs across three paths so one never interferes with the other:
| Path | When it runs | Transport | What travels | Best fit |
|---|---|---|---|---|
| Session Sync | Tech & notes (show stopped) | UDP/TCP OSC + optional Lua read-back or USB XML | Sequence cue skeletons, labels, fades, lane colours, native MA3 Timecode objects | Building or merging a cue list with a lighting programmer |
| grandMA3 OSC | Live show | UDP (default, port 8000) or TCP OSC | Sequence Go+/Goto, executor levels and keys, macros, Grand Master blackout/restore | Calling a show from Run Mode or chasing timecode slots |
| MIDI Show Control | Live show | DIN MIDI, RTP-MIDI or USB MIDI | Standard MSC GO, TIMED_GO, LOAD / standby, ALL_OFF | Touring into house rigs where IP/OSC access to the console is locked down |
How Session Sync Protects the Programmer's Looks
The reason lighting programmers hesitate to let an external show controller write to their sequence is simple: a blind Store /Overwrite wipes out channel values. Session Sync is built around three safeguards in File → Sync, Import & Export → Sync to GrandMA3…:
- Preview before anything leaves the Mac. Opening the dialog sends no
Store,DeleteorLabelcommands. Every MA3 command CueSync plans to send is listed in the diff preview first. - Scratch sequences vs. adopted baselines. Sequences 900–999 (configurable under Settings → Advanced → grandMA3 Sync) are CueSync's scratch workspace. Outside that range, CueSync refuses to write blindly unless you adopt the console's existing sequence as a baseline via the optional bridge plugin — or explicitly confirm a one-off write.
- Additive merge by default. Once a baseline exists, re-pushing after rehearsal notes relabels or retimes existing cues without re-storing them, and deleted cues stay on the console marked removed (kept on console) unless you switch Delete removed cues on console on.
Decimal insertions stay readable too: because grandMA3 numbers initial cues sequentially to keep stored looks anchored, an inserted CueSync cue 1.5 keeps its desk slot and carries Q1·5 at the start of its console label so the stage manager and programmer still speak the same cue number.
Choosing a Layout: Timeline, Lanes or Show Lanes
Under Theatre track to sync, CueSync offers three ways to map your Show Editor structure onto grandMA3 sequences:
- Timeline merges every grandMA-routed lane of the Part into one sequence and one Timecode Track — ideal when one lighting operator calls the whole room from a single main cue stack.
- Lanes gives each department lane (for example
LX Key,Movers,Followspot) its own sequence and its own Track inside a shared Timecode object so independent playheads never step on each other. - Show lanes spans multiple Parts across the house clock so
LXin Act I and Act II lands on one continuous sequence.
Cues routed exclusively to non-grandMA outputs (such as QLab or Resolume) are omitted automatically and counted in the summary. Lanes or MSC cues naming pyro, laser, flame or CO2 are held back from desk sequence and Timecode exports unless you right-click the lane chip and set Output Routing → grandMA desk → On deliberately.
Sending Timecode Objects Over the Network or USB
With cuesync_bridge (1.7.0 or newer) running on the console, Send sequence + Timecode… pushes the cue merge first and then transfers the native MA3 Timecode object in numbered, checksum-verified chunks before checking the console's Timecode pool to confirm every event points at an existing cue. Notice what is left out of that Timecode object on purpose: GO, standby and follow cues receive no timecode event so the console still waits for a human call on scenes that follow an actor rather than the clock.
When there is no network path to the console at tech, Export MA3 macro (USB)… and Export Timecode XML (USB)… write the exact gma3_library files and companion README instructions onto a stick.
Console OSC Checklist Before Tech
Because UDP OSC is connectionless, a misconfigured console line drops commands silently while CueSync reports them sent. Check six items once in Menu → In & Out → OSC on the grandMA3:
- Enable Input and Receive Command both switched on
- Preferred IP / Interface matching the subnet of the CueSync Mac
- Prefix left completely empty
- Port matching CueSync's output (8000 by default)
- Page / Fader / Key strings left at their defaults (
Page,Fader,Key) - Fader Range set to
100
Further Reading
- grandMA3 Session Sync in the manual — full dialog reference, bridge setup and edge cases
- grandMA3 integration guide — live OSC verbs, Looks and sequence feedback
- QLab or grandMA3: Which One Should Be Master?
- Show control for Theatre
- Download CueSync
grandMA3® is a registered trademark of MA Lighting International GmbH. CueSync is independent software and is not affiliated with or endorsed by MA Lighting.
Frequently Asked Questions
Does Session Sync overwrite the lighting looks already stored on the grandMA3?
Not when merging. Once CueSync holds a baseline for a sequence — either because CueSync created it in the 900–999 scratch range or because you clicked Adopt console as baseline with the read-back bridge running — re-syncing only relabels or retimes existing cues and stores genuinely new cues. Existing looks on unchanged cues stay intact.
Can I use Session Sync during a live performance?
No. Session Sync is blocked while a show is live so an authoring push can never write to a running sequence. Stop the show in CueSync before opening File → Sync, Import & Export → Sync to GrandMA3.
Do I have to install the Lua bridge plugin on the console?
No. Pushing a cue structure over OSC and exporting an MA3 macro or Timecode XML for a USB stick work without the bridge. Installing cuesync_bridge.lua adds read-only sequence feedback so CueSync can detect desk-side edits, browse console sequences, adopt a sequence as baseline and verify network Timecode pool imports.
When should I fire grandMA3 over MIDI Show Control instead of OSC?
Reach for MIDI Show Control when the house desk has OSC disabled by venue policy or sits across a 5-pin DIN MIDI opto-isolator, and all you need is numbered Cue GO, Timed GO, Standby or Off commands. Reach for grandMA3 OSC when you also need executor faders, macros, sequence feedback or Session Sync.
Can I inspect the dialog before subscribing?
Yes. With a free account you can run the demo show and tour the app in read-only mode. Building and saving your own shows, and connecting real outputs, need a paid plan.
Keep Reading
- Guides
QLab or grandMA3: Which One Should Be Master?
Two systems that both want to own the show clock. How to decide which is authoritative, and why the wrong answer only shows up under pressure.
- Guides
MIDI Show Control: Still the Most Reliable Cue Trigger
MSC is a 1991 spec that still runs theatres. The SysEx byte format, the command families, the 128-byte cap, and four ways it fails without an error.
- Guides
How to Send Timecode to grandMA3: LTC, MTC and Art-Net
grandMA3 can follow SMPTE/LTC, MIDI timecode or Art-Net timecode. How each reaches the console, which to choose, and what happens when the source drops.