Programming at Speed: The Disciplines That Separate Touring LDs From the Rest
The 1,000-show concert series is the ultimate stress test for lighting console programming methodology. Productions like Taylor Swift’s Eras Tour — which surpassed USD 1 billion in gross revenue and played to over 10 million audience members across 149 shows — or Ed Sheeran’s Mathematics Tour (255 shows across three years) expose every weakness in a programming approach that might survive a 20-date run. Across these marathon tours, the MA Lighting GrandMA3 show file must remain stable, manageable, and operable by a rotating crew of associate programmers who may encounter it for the first time mid-run without the luxury of a pre-tour programming camp.
The discipline of programming for longevity rather than immediate visual impact is one of the most underappreciated skills in professional lighting design. A GrandMA3 show file built for a 255-show run must accommodate venue-specific overrides without corrupting the base programming, set list variations that occur at any show with minimal programming intervention, emergency backup cue paths accessible when primary sequences fail under show pressure, and the inevitable fixture substitutions that occur when touring inventory encounters damage and local rental supplements with different model specifications that need to integrate seamlessly with existing programming.
Show File Architecture: Building for the Long Haul
Experienced touring LDs approaching a multi-day concert series begin with show file architecture decisions that will determine the file’s operational resilience across every subsequent show. The fixture patch structure must accommodate the tour’s primary inventory while providing designated substitute universe addresses for local supplemental fixtures. Sequence numbering conventions follow hierarchical schemas — main show sequences in the 100 range, alternate versions in the 200 range, venue-specific overrides in the 300 range — that allow any programmer encountering the file mid-tour to navigate it intuitively.
The preset library — the GrandMA3’s system of stored parameter values that form the building blocks of cues — requires particular discipline on long-run shows. On a 250-show tour, the preset library will be modified dozens of times as new fixtures enter the rig, as LD creative decisions evolve, and as venue-specific calibrations require adjustments. Productions that have used global presets — which propagate changes across all cues referencing them automatically — have discovered mid-tour that a well-intentioned calibration update can unexpectedly change the look of fifty different song cues simultaneously. The counter-discipline: song-specific local presets for all lighting looks that are creatively intentional, with global presets reserved only for technical calibration values.
Timecode and the Multi-Day Show Continuity Challenge
Productions that lock GrandMA3 to SMPTE timecode for automated show sequences face particular challenges across multi-day events. When a production plays the same venue for three or four consecutive nights — as arena tours routinely do in major markets — timecode offsets may need adjustment to accommodate set length variations between nights, support act timing changes, and broadcast windows for special televised performances. The GrandMA3’s timecode engine’ s offset management allows these adjustments without rebuilding cue stacks, but requires a rigorous show prep protocol where the production’s timecode master — typically residing in the show control system or a QLab playback server — is synchronized with the GrandMA3 file before doors open each night.
For multi-day festival productions where multiple artists perform across the same stage setup across three or four days — events like Rock in Rio, Lollapalooza, or Reading and Leeds — the GrandMA3 session architecture enables multiple artist show files to coexist within a single network session, with the systems operator switching active show files between artist sets without console reset. This capability, used by production companies including LD Systems and Solotech for major multi-artist events, allows seamless transitions between artists with completely different lighting designs while maintaining the network session stability that prevents the mid-show crashes that have plagued less architecturally robust platforms.
The Programmer-LD Dynamic on Extended Tours
Extended touring productions typically separate the lighting designer (LD) from the console programmer — a division of labor that reflects the different creative and technical skill sets the two roles require. The LD defines the visual language of the show: color palettes, movement vocabulary, thematic lighting approaches per song. The programmer implements that language in the GrandMA3 with the technical precision and workflow efficiency that the demanding touring schedule requires. On a 255-show run, this relationship must survive the creative evolution of the LD’s vision, the touring pressures that compress programming time, and the occasional tension between artistic ambition and operational practicality.
Leading touring programmers — practitioners whose credits include Robe Lighting’s Educator program graduates, MA Lighting Certified Programmers, and veterans of companies like PRG and Bandit Lites — describe the key discipline of extended tour programming as defensive programming: building show files that anticipate failure and degrade gracefully. Every critical look has a backup. Every automated sequence has a manual override. Every fixture type has a designated fallback position that produces an acceptable result even if the primary programming sequence cannot execute. On a 1,000-show tour, statistical certainty dictates that multiple significant technical failures will occur. The programmer’s job is to ensure that none of them are visible to the audience.
The Legacy Show File and Institutional Knowledge
One of the underappreciated assets created by a multi-year concert series is the institutional knowledge embedded in a mature GrandMA3 show file. A show file that has survived 1,000+ performances across four continents contains accumulated solutions to hundreds of venue-specific challenges — audience geometry overrides, structural rigging restrictions, local power phase relationship adjustments, venue-specific focus positions for permanent installations — that represent months of accumulated problem-solving. Productions that treat this institutional knowledge as a transferable asset, exporting, documenting, and archiving show files for future reference, create a competitive advantage for subsequent tours in the same or comparable venues that is literally impossible to recreate from scratch.
