A multi-day concert series is not a collection of separate shows sharing a venue. It is a living show file that grows, adapts, and evolves across multiple performance days, with programming decisions made at 11pm on night one influencing the creative and technical possibilities available on nights two through five. Managing this living document — maintaining version control, protecting critical cue stacks from accidental modification, managing the constant stream of artist requests and creative adjustments that arrive between show days — is one of the most sophisticated workflow challenges in grandMA3 programming, and the techniques that experienced programmers have developed to address it represent some of the most valuable operational knowledge in the live entertainment industry.
Show File Architecture for Multi-Day Series
The architecture of a grandMA3 show file for a multi-day concert series begins with a decision about cue stack organisation that will define the entire programming workflow: whether to build individual sequence pools for each artist or act, or to build a single master sequence that manages the entire run with conditional playback logic. Experienced festival and multi-day series programmers generally favour the individual sequence approach for maximum flexibility — each artist’s cue stack occupies its own sequence pool, with a master sequence managing the transition and house cue states between sets. The grandMA3’s pool management system allows sequences to be organised into named executor pages corresponding to each show day or each artist, with page protection enabled to prevent accidental overwriting of programmed sequences during live operation. Show file version control — saving named snapshots before every significant programming session and after every show day — is an operational discipline that has prevented catastrophic data loss on more occasions than the industry cares to admit.
Timecode Integration in Extended Runs
Multi-day concert series that incorporate timecoded musical performances — particularly touring productions with precisely timed pyrotechnic, automation, and video cue integration — use grandMA3’s timecode management in ways that reveal the platform’s depth. The console supports simultaneous reception of MIDI timecode, LTC (linear timecode), and Art-Net timecode, allowing different stage elements to sync from different timecode sources without creating conflicts. For a five-night residency at a major arena, the typical timecode architecture involves an Aaton Cantar X3 or Sound Devices 970 multitrack recorder generating LTC distributed to the lighting, video, and automation systems, with the grandMA3 acting as a slave that executes pre-programmed cue stacks in response to received timecode. The system’s timecode offset function — allowing the console to receive a raw timecode value and offset it by a user-defined amount — gives operators the ability to adjust synchronisation without modifying the timecode source, a critical capability when sharing timecode infrastructure with pyrotechnics companies whose safety interlocks make timecode source modification operationally impossible.
Multi-Day Rig Changes and Fixture Management
A multi-day concert series at a major venue frequently involves fixture changes between show days as touring productions bring their own lighting rigs that supplement or partially replace the house inventory. Managing these fixture changes in a running grandMA3 show file requires patch management discipline that prevents the accidental re-addressing of already-programmed fixtures while adding new inventory. The grandMA3’s fixture exchange function — which allows a programmer to substitute one fixture type for another while preserving all programmed cue data, automatically translating parameter data to the new fixture’s profile — is invaluable in this context. When a touring production arrives with 48 Robe BMFL Spots to supplement the 96 Claypaky Sharpy Plus units already in the house rig, the exchange function allows the existing Claypaky cue data to be applied to the incoming Robe fixtures without manual reprogramming, provided the parameter mapping between the two fixture types is compatible — a compatibility that the GDTF standard is progressively standardising across the industry.
The Human Element: Programmer Workflow and Team Coordination
Behind the technical architecture of a multi-day series show file is a programming team whose workflow disciplines are as important as their console skills. Senior programmers on major multi-day series — residencies at venues including the O2 Arena, Crypto.com Arena, and Madison Square Garden — maintain programming logs documenting every modification made to the show file, the reason for the modification, and the programmer responsible. These logs serve dual purposes: they provide an audit trail when investigating unexpected show behaviour, and they create a knowledge transfer document that allows a substitute programmer to step into the role with minimal briefing. The grandMA3’s built-in show notes function — a text field embedded in the show file that travels with the data — allows programmers to embed operational notes directly in the sequences, executors, and patches that documentation addresses, creating a self-documented show file that is more valuable than any external spreadsheet.
