grandMA2 Integration
grandMA2 compatibility concepts — documentation draft only, with no runtime support in this beta.
grandMA2 compatibility is a documentation-draft concept only. CueForge does not support MA2 integration in the 0.99.1 beta — there is no runtime support of any kind. This guide records the intended workflow and safety considerations for a future implementation so that MA2 venues can plan accordingly.
Do not plan a show around MA2 integration. There is no MA2 trigger family, sender, or mapping in the current build. Where MA2 is essential, drive it from a system that supports it today and treat CueForge integration as a future possibility.
grandMA2 is a legacy platform. Any future CueForge support would be verified against specific MA2 versions before publication. Verify all syntax against your specific MA2 version before use.
Intended design (future)
- Send OSC or remote-control triggers from CueForge to MA2 executors
- Configurable host, port, and address patterns via the generic OSC path
- Support operators during transitional periods between MA2 and MA3
Any future MA2 support would be send-only. Bidirectional control is not planned.
What to do today
- Use CueForge’s generic OSC Cues for any OSC-capable equipment in the venue.
- For MA2 rigs, keep the existing control path (MA2 remote input, MIDI, or another show controller) until CueForge support is announced and validated.
- Consider the grandMA3 integration for newer desks.
Requirements (future)
- grandMA2 console or onPC with network connection
- OSC or remote control input enabled
- Shared network or direct Ethernet link
Current limitations
- No runtime support in this beta — documentation draft only.
- OSC syntax for MA2 differs from MA3. Verify exact commands against the future implementation.
- Bidirectional control is not planned.