The Complete Guide to Stage Automation for DJs in 2026
Stage automation replaces manual cue stacks with audio-reactive lighting, visuals, and timecode. The full 2026 playbook for DJs and lighting designers.
CueSync TeamStage Automation Engineers
On this page18 sections
- What Is Stage Automation?
- The Hardware Stack
- 1. The Laptop
- 2. Beat Source
- 3. Network
- 4. Protocol Output
- 5. Fixtures
- 6. Visual Systems (Optional)
- The Software Stack
- Protocol Choice
- The Beat Engine
- Fixture Patching
- Cues: The Automation Core
- AutoPilot, CuePad, and Manual Override
- Venue Profiles: The Mobile DJ Secret
- Scaling Up: Theatre and Production
- Common Pitfalls
- Start Small, Scale Smart
What Is Stage Automation?
Stage automation is the coordinated control of lighting, video, audio, and effects from a single source that reacts to music in real time. Instead of pre-programming every cue by hand or hiring an operator to chase the beat, automation systems follow your music and drive your entire rig over DMX, Art-Net, sACN, OSC, MIDI, and timecode — simultaneously.
For DJs, that means your lighting and visuals follow whatever track you play, without prep, without an operator, and without compromising your mix. For lighting designers, it means the mechanical work of beat-chasing is handled so you can focus on creative direction. For production teams, it means beat-chasing no longer needs an operator of its own.
This guide covers the complete stack for 2026 — what you need, how to set it up, how to plan your first show, and how to scale from a mobile DJ rig to a festival stage.
The Hardware Stack
A complete stage automation rig has six layers.
1. The Laptop
CueSync needs a Mac with Apple Silicon and macOS 12 or later. A MacBook Air M2 handles the DJ Edition's full protocol stack comfortably for small-to-medium rigs. For complex shows with 4+ universes, Pioneer DJ Link, Resolume, and plug-in visual software on the same machine, a MacBook Pro M3+ is more comfortable.
2. Beat Source
CueSync needs a beat to follow. Options:
- Pioneer DJ Link (most accurate): Plug CDJs/XDJs into the same network as your Mac — CueSync reads BPM, beat phase and track identity directly, plus phrase analysis from the rekordbox USB
- Local Audio (no decks needed): Play your own WAV, AIFF, MP3, M4A (AAC-LC), FLAC or OGG files from CueSync — each one is analysed for beat grid, phrases, energy and key
- OS2L or Ableton Link (software rigs): Follow a beat grid from VirtualDJ (or from Serato or rekordbox through an OS2L bridge), or an Ableton Link session
3. Network
A basic 5-port gigabit Ethernet switch is enough for most rigs. For touring production with dozens of fixtures and redundancy, move to a managed switch with IGMP snooping (for multicast sACN).
4. Protocol Output
For anything larger than a simple USB DMX chain, an Art-Net or sACN node is your bridge from Ethernet to DMX. Popular options:
- ENTTEC ODE: 1 universe, reliable, well-supported
- DMXking eDMX1/2/4: 1, 2, or 4 universes, compact
- Chauvet Net-X II: 2 universes, mobile-DJ friendly
- grandMA3 Node: for MA3-integrated rigs
5. Fixtures
Fixtures sit behind your console or Art-Net/sACN node, which holds the patch; CueSync fires the console or sends DMX levels to the node. For DJ work, prioritize:
- LED wash/par lights (4-8): foundation
- Moving heads (2-4): dynamic beam/spot looks
- LED bars or battens (1-2): wall wash and uplighting
- Hazer (1, venue-permitting): makes beams visible
See the complete mobile DJ guide for specific fixture recommendations by budget and venue type.
6. Visual Systems (Optional)
If you also run visuals, CueSync drives Resolume (run against a live Arena) and Unreal Engine 5 (verified in-engine, on our own project), and its disguise and TouchDesigner outputs are built to each maker's published interface but have not yet been run against that equipment. One beat source drives both your lighting and your video from the same analysis engine.
The Software Stack
CueSync DJ Edition includes everything you need for the full automation workflow:
- AutoPilot: hands-free automation driven by real-time beat synchronization
- ProDeck: main control surface for monitoring and adjusting during the show
- CuePad: tap-to-fire grid for layering manual cues over AutoPilot
- Cues and actions: each cue pairs a trigger (beat, phrase, energy, timecode, MIDI, OSC) with actions that fire your console, media server or DMX scene
- Network → Outputs: add, test and monitor every output, with live latency graphs and connection events on the Monitor tab
- Looks: named sets of actions in the Palette that any cue, pad or AutoPilot moment can fire
- Venue Profiles: save/load per-room configurations
Protocol Choice
Your protocol choice depends on rig size and network. The full breakdown lives in our DMX vs Art-Net vs sACN guide, but the short version:
- Small mobile rig (<30 fixtures): 1-universe Art-Net node like ENTTEC ODE fed by your Mac over Ethernet
- Club with grandMA3 console: CueSync drives the desk over OSC, and the desk feeds its own nodes over Art-Net (its native protocol)
- Festival or touring rig: sACN multicast for priority merging and bandwidth efficiency
- Anything with Resolume: add OSC alongside your DMX protocol
- Synchronized with Ableton: add Ableton Link for tempo/phase lock
CueSync runs as many outputs at once as you add under Network → Outputs, so you don't have to choose one.
The Beat Engine
The heart of stage automation is the beat engine. CueSync's engine draws on four kinds of information:
- Beat phase and BPM — read from the decks over PRO DJ LINK, or from the Ableton Link, OS2L or tap-tempo source you follow
- Beat grid — on files you play in Local Audio, analysed on your Mac
- Phrase structure — intro, build, drop, chorus and outro boundaries from rekordbox's analysis or CueSync's own
- Energy and key — the track's energy trend and key, available as triggers
Triggers pick which of these fires a cue: Beat (a chosen beat of every Nth bar), Phrase Change, Energy Level, Energy Transition and more. The result is musical lighting, not a metronome.
More on where the beat comes from is in how CueSync detects beats.
Fixture Patching
CueSync does not patch fixtures. The fixture profiles live on your console or Art-Net/sACN node, so patch and address your lights there, setting each physical fixture to its own DMX start address and mode. CueSync's job is to say when and what: it fires a console cue, executor or macro (grandMA3, Eos, MagicQ, Titan), or sends DMX levels to your node from a DMX Look.
In the Palette, a DMX Look holds a protocol (sACN or Art-Net), a universe and a table of channels and values. Import your console's or visualiser's MVR under Settings → Pixels → Fixture patch and the channel table shows fixture names beside the channel numbers.
Cues: The Automation Core
On the Cues screen, each cue pairs a trigger with one or more actions that fire a destination: a console cue, a Look, a Resolume clip, a DMX scene. Example cues:
- Beat → Wash look: a Beat trigger fires an intensity-pulse Look on the downbeat of every Nth bar
- Phrase Change → Scene change: when a new phrase starts, rotate to the next color Look
- Energy Level → Mover look: moving heads come up when the energy enters the band you set
- Phrase Change (drop) → Full rig strobe: every drop in the track's phrase map fires a strobe burst
- Energy Level → Haze burst: an Energy Level trigger fires a hazer burst
Each cue has a trigger — the beat in the bar and bar interval, a phrase type, an energy band — and a Beat cue has an offset in milliseconds for fixture pre-roll. Tune them per venue — a church reception wants very different defaults than a club peak hour.
AutoPilot, CuePad, and Manual Override
Three layers operate on top of each other:
- AutoPilot runs the continuous flow of the show automatically
- CuePad lets you fire pre-built one-shot cues on top of AutoPilot ("first dance spot", "drop highlight", "last song fade")
- Manual override always trumps both — touch any control and you're in charge
The intended workflow uses all three: AutoPilot for the bulk of the show, CuePad for the big moments, manual for the unexpected.
Venue Profiles: The Mobile DJ Secret
Venue profiles carry a room from one gig to the next. A profile saves your per-venue configuration — everything you tuned the first time you set up for that room — so you can recall it on your next visit.
After your first gig at a venue, save the profile. Every future gig at that venue starts from it.
Build three generic templates to start:
- Wedding / Corporate: warm, elegant, subtle movement, drops disabled
- Club / Peak-hour: high-energy, fast beat response, aggressive drop cues
- Festival / Outdoor: maximum impact, wide color palette, full drop sequences
Load the closest template at a new venue, adjust for the specific rig, save the result, and you've just added a new profile to your library.
Scaling Up: Theatre and Production
CueSync DJ Edition handles everything described above. Two further editions are available:
Theatre Edition adds the Show Editor and Run Mode (a multi-track timeline over your master audio), timecode chase of an incoming LTC, MTC, Art-Net or TCNet master (every edition already generates LTC, MTC, Art-Net Timecode and TCNet), and the Companion crew board with cue lights for every department. It's the right choice when your shows have a script and you need frame-accurate multimedia synchronization.
Production Edition adds Predictive Preview (look-ahead showing the automation about to fire), loudness-matched playback, CueSync Crowd publishing to audience phones, and unlimited venue profiles (no cap on saved rig configurations).
Full breakdown in the edition comparison guide.
Common Pitfalls
- Too much reactivity: firing a cue on every beat looks robotic. Use phrase-aligned triggers, and raise the AutoPilot profile's Significance Threshold.
- Underspec'd laptop: file analysis, protocol output, PRO DJ LINK and Local Audio playback running together all benefit from headroom.
- Network conflicts: run a dedicated subnet for Art-Net/sACN if possible. Mixing lighting traffic with Wi-Fi traffic causes drops.
- Skipping the venue profile: always save after the first gig, so the second visit starts from what you tuned on the first.
- No backup plan: have a manual fallback. Consoles, hardware cues, or a second laptop — one of the three.
- Forgetting about strobes: photographers and videographers hate uncapped strobes. Set the room's limits in your venue profile's Output policy (a maximum level for DMX channels, a strobe cap for the pixel wall).
Start Small, Scale Smart
Don't try to build a festival rig on your first weekend. Start with 4-8 LED pars, AutoPilot, and one venue profile. Add moving heads next. Add visual software when you've mastered the lighting. Add timecoded segments when you're running scripted events.
Download CueSync free and run the demo show and tour the app in read-only mode, then subscribe to the DJ Edition when you're ready to go live.
The industry is moving to audio-reactive automation for one reason: it's faster and more flexible than the alternatives. This guide is your map to catching up.
Frequently Asked Questions
Everything that traditionally requires a dedicated operator reacting to music: beat-synced lighting cues, energy-tracking color changes, phrase-boundary scene transitions, drop detection, fog/haze bursts, visual software triggers, and multi-protocol hardware coordination. It does not automate creative direction, setlist selection, or crowd reading — those remain human decisions.
Keep Reading
What Is Music-Driven Lighting Automation? A Definition
Music-driven lighting automation is lighting control that follows the music's beat and structure, from analysed tracks or live deck data. How it works.
ReadHow to Automate DJ Lighting with grandMA3 (2026 Guide)
Step-by-step guide to connecting CueSync to your grandMA3 console for beat-reactive lighting automation at clubs and festivals.
ReadMobile DJ Lighting: The Complete 2026 Setup Guide
Everything you need to set up automated lighting for mobile DJ gigs — gear, software, venue profiles, and the one-laptop workflow with CueSync DJ Edition.
Read