grandMA2 (legacy)

What this does: records the state of the grandMA2 bridge. It is frozen. grandMA3 is the supported desk: grandMA3 setup.

Frozen

No Cues release is tested against a grandMA2. No control in Cues starts the MA2 bridge. Do not plan a show around it.

What is still in the code

• HTTP bridge. A small server in Cues on port 8765. An MA2 Lua plugin (HelmCues 4.0.32) polled it every 500 ms, ran the commands it got and posted playback back. Nothing in the app starts it.
• Telnet client. Port 30000, for direct commands. It needs Remote Login on the MA2. Nothing in the app opens it either.
• Track fields. Sequence Options → Lighting Control dates from the MA2 bridge. Its MA2-only controls, Executor End and the sync switch, are no longer shown.

What does not exist

• No MA2 plugin release alongside current Cues builds.
• No tests on an MA2 since the rebuild began.
• No two-way edits, Flash, desk show commands, Panic Off or Sessions on MA2. Those were built for grandMA3.

Run an MA2 today

1. Send timecode from Cues: LTC or MTC. See Timecode.

2. Export the track’s cues: File → Export → Track → MA2 CSV….

3. Program the MA2 timecode show by hand from that list, one track at a time.

• Want the bridge finished? Say so at support with the desk model and software version. It is a decision, not a bug.

When it goes wrong

• Nothing to fix. The bridge is frozen. Use timecode plus the CSV export, or move the desk side to grandMA3.
• The MA2 misses cues. Check the timecode first: rate, offset and the MA2’s timecode input. See Timecode.