Total Chaos home page
Documentation sections
Early Access Last updated 2026-09-11

grandMA3 Integration

Send OSC from CueForge to grandMA3 consoles — early-access workflow and verification guidance.

Early Access

CueForge is designed to send OSC triggers to grandMA3 consoles and onPC installations. In the 0.99.1 beta this workflow is early access: it is designed to send, but it has not yet been validated against a real MA3 installation. Verify it against your specific MA3 software version before relying on it in a live show.

Verify before showtime

External MA3 behaviour varies between software versions and configurations. Menu paths and OSC responses must be verified against the exact MA3 version used by the operator. Do not assume this workflow works until you have seen it work in your environment.

LTC reception in beta 0.99.1

MA3-to-CueForge LTC reception was physically checked at 25 fps through Studio 1824c Input 8 (48 kHz). This is separate from OSC sending to MA3. Follow the Timecode setup guide for input lock, rate matching and deliberate trigger arming; do not treat this one setup as acceptance of every MA3 integration path.

Intended design

  • CueForge sends OSC messages to MA3 — for example from an OSC Cue, or from the cue editor’s Triggers section when another event should fire MA3
  • Configurable host, port, address pattern, and typed arguments
  • Typical intent: trigger MA3 executors or sequences in step with sound, video, and automation cues

These are designed capabilities of the OSC send path, not validated MA3-specific features. Confirm the exact address patterns your MA3 build responds to.

Direction

CueForge sends OSC to MA3 only. Bidirectional control is planned but not available in this beta.

Requirements

  • grandMA3 console or onPC with network connection
  • Valid IP address and port for MA3 OSC input
  • MA3 OSC input enabled and configured
  • Shared network or direct Ethernet link between CueForge and MA3

Verification checklist

  1. Enable OSC input in MA3 network settings and note the IP address and port.
  2. In CueForge, create a dedicated OSC Cue aimed at MA3 — set Host, Port, and Address.
  3. Use the cue’s Test Send button to fire the message manually against a non-production executor.
  4. Verify the MA3 executor responds as expected in your MA3 version.
  5. Only after successful testing, map to production targets — and re-verify before every show.
Exact menu paths

Exact MA3 menu paths should be verified against the target software version; they vary between releases.

Show safety notes

  • Never test on a live rig without output isolation.
  • Use a test executor or sequence before mapping to production fixtures.
  • Confirm IP, port, protocol, and command mapping before every show.
  • Label every CueForge cue with its MA3 target for clarity.
  • Document your network layout and share it with the crew.

Current limitations

  • Send-only; bidirectional control is planned.
  • Not validated against a real MA3 installation in this beta.
  • Exact executor syntax depends on MA3 software version.
  • No automatic MA3 show file sync. Maintain cue numbering alignment manually.