DMX Consoles and Software: How to Choose
The same 24 fixtures can be driven by a cheap USB interface or by a touring console. The difference is not how many channels they output; it is how they let you organise the show. The right choice depends far more on the kind of work you do than on fixture count.
In short
- A console’s value lies in how it organises the show, not channel count.
- Always programme positions and colours through palettes.
- Moving lights demand a console with palettes and an effects engine.
- An offline editor is decisive where rehearsal time is expensive.
- A widely used platform means you can find a substitute operator.
- Back up the show file after every rehearsal; build redundancy on sACN priority.
What a console actually does
A DMX console is fundamentally a device that repeatedly broadcasts 512 numbers. The valuable part is how it produces those numbers. A good console gives you:
- Patch — fixtures defined by profile, so you work with “colour” and “pan” rather than channels.
- Groups — selection sets such as “front of house” or “back light”.
- Palettes / presets — frequently used colours, positions and gobos. Change a fixture’s position and you update the palette; every cue using it follows.
- Cues and cue lists — sequenced looks with fade times.
- Effects engine — waves, circles and rainbows without programming them by hand.
- Submasters / playbacks — faders and buttons for live control.
Why palettes matter so much
The mistake beginners most regret is writing positions directly into cues. On tour the rig shifts slightly every day; if positions are baked into cues you correct hundreds of them individually. If you used position palettes, you update the palette and the whole show follows. Programme everything through palettes.
Types of console
| Type | Strength | Suited to |
|---|---|---|
| Simple fader console | Instantly understood, cheap, few failures | Small venue, fixed install, a handful of pars |
| Software plus USB-DMX interface | Cheapest route, powerful programming, visualiser support | Workshop, small club, learning, fixed installs |
| Software plus hardware wing | Software power with the speed of physical faders and keys | Mid-size venues and touring |
| Moving light console | Palettes, effects engine, timecode, redundancy | Concerts, theatre, TV, large events |
Software options
The range runs from free and open source through to industry-standard platforms. For learning and small installs, free software is more than adequate; in professional work the deciding factor is usually not the software itself but how widespread it is in the industry — because on tour you need to be able to find a substitute operator who knows it.
Almost every serious platform offers an offline editor, letting you programme a show on a laptop without the console. Where rehearsal time is expensive, that should be near the top of your criteria.
Questions to ask when choosing
- Are there moving lights? If so you need palettes and an effects engine; programming a moving head from a simple fader console is punishing.
- Is the show fixed or live? Theatre favours cue lists, concerts favour busking capability.
- How many universes? Aim for at least twice today’s requirement; pixel work consumes universes fast.
- Do you need timecode? Essential for shows synchronised to music or video.
- Do you need redundancy? On critical work a second console must take over automatically — the cleanest route is the sACN priority field.
- Who will use it? A platform the person inheriting the system already knows beats a technically superior one nobody can operate.
Common mistakes
- Not backing up the show file. To a USB stick and the cloud, after every rehearsal. Console drives fail too.
- Putting the console on the main network. Keep lighting separate; video traffic through an unmanaged switch can take the show down.
- Updating software on show day. Never.
- Not verifying the fixture profile. If the profile and the fixture’s actual mode disagree, nothing behaves as expected — detail in the channel chart article.
- Relying on one console. Keep at least a basic fallback that can run a usable look.
Related articles
Project and product support
Stuck somewhere in your installation, or unsure which product fits? Drop us a line for project consultancy and product support.
