grandMA3 Setup Guide

CueSync speaks to grandMA3 natively — it sends real console commands over the network, pushes your cue list to a desk sequence, and can read the desk back. That native path has been run on a grandMA3 console and on grandMA3 onPC, and it is the one to use. (Driving grandMA3 with raw Art-Net DMX is also possible — see the last section.)

Prerequisites

• grandMA3 console or grandMA3 onPC on the same network as your Mac
• Every CueSync edition includes grandMA3 output; Session Sync (cue-list push/pull) is a Theatre/Production feature
• Ethernet strongly recommended

Step 1: Add the grandMA3 Output in CueSync

1. Go to Network → Outputs → + and add a grandMA3 (UDP) output with your console's IP address. UDP is the recommended transport — a grandMA3 desk may not open an OSC-over-TCP listener, so a TCP output may never connect.
2. Confirm the output shows connected.

Step 2: Let the Console Accept Commands

On the console, open the OSC line settings and enable both Enable Input and Receive Command. Without Receive Command the desk silently ignores every command CueSync sends — this is the most common configuration error. Leave the line's Prefix empty (with a prefix set, none of CueSync's commands reach the desk), and check the OSC page's Interface names the network your Mac is on.

Step 3: Fire the Desk from CueSync

• Looks — build grandMA3 Looks on the Palette screen and fire them from pads, cues or Auto Pilot; CueSync resolves each Look to the matching console commands.
• Cue actions — attach grandMA3 actions (Go, executor, macro commands) to any cue in your stack, triggered by beat, phrase, timecode, or manually.

Step 4 (Theatre/Production): Session Sync

File → Sync, Import & Export → Sync to grandMA3… moves your whole Theatre cue list to the desk without re-programming:

• Push your cue structure into a sequence in the scratch range (900–999 by default; type any number in it) — or, after Adopt console as baseline with the bridge running, into the sequence your LD already programmed. The dialog previews every command and never re-stores existing cues, so the looks your LD programmed survive a re-push.
• Send the Timecode object over the same connection — one song or the whole setlist — and CueSync reads back from the desk what arrived. Re-export the bridge plugin from Install bridge… and load it on the console first, so the desk can report its Timecode pool.
• Export as an MA3 macro or Timecode XML to carry the show on a USB stick when there's no network to the desk.
• Install the read-back bridge (a read-only Lua plugin) to get drift warnings and pull the console's cue list back into CueSync.

Troubleshooting

Alternative: Art-Net DMX

CueSync can also output raw Art-Net DMX for grandMA3 to receive as a DMX input source. Use it when you want fixture values as DMX, for example to feed executor faders as DMX remotes; the native output above carries the commands. See ArtNet Configuration.