PROVANTAGE / Production Notes 02
Live sound consoles are systems, not scoreboards.
A console should not be selected because it tops a generic ranking. It should be selected because its signal architecture, operator workflow, networking and recovery plan fit the production.
Start with the system
The surface is only the part we touch.
On many professional platforms, the control surface, processing engine and stage I/O are distinct parts of one system. That distinction affects where audio is converted, where it is processed, how operators connect and what happens if a link or component fails.
The useful question is not “How many faders does it have?” It is “Can this complete system carry, control and recover every signal the event depends on?”
Five-question selection check
Define the production before naming the console.
How many inputs, outputs, buses and matrices are required, and where must each physical connection live?
Who owns front of house, monitors, broadcast, recording and communications, and which controls must be simultaneous?
Do scenes, snapshots, layers, macros, processing and crew familiarity support the pace and complexity of the show?
Which transport, clock, switch, cable, latency and gain-control decisions connect the system end to end?
How will the team respond to loss of power, control, processing, network, I/O or the current show file?
Different work, different priorities
One specification sheet cannot describe every show.
Corporate & conference
Presenter changes, panels, playback, remote contributors and record feeds reward clear patching, controlled recalls and calm operator workflow.
Concert & festival
Large input lists, monitor mixes, guest files, rapid changeovers and line checks place greater pressure on I/O, speed, familiarity and support.
Broadcast & recording
Signal splits, gain ownership, isolated feeds, multitrack capture and virtual soundcheck must be planned without compromising the live mix.
Operational reality
The biggest console is not automatically the safest choice.
Capacity without a rehearsed workflow can add risk. A well-understood system with verified files, labelled patches, current documentation and a practical recovery route may serve the event better than a larger platform the crew cannot operate efficiently.
- Build the signal map
- Assign control ownership
- Confirm system compatibility
- Prepare and version show files
- Rehearse recovery
Professional reference architectures
Reference systems, not a universal ranking.
Current professional families illustrate different implementations of distributed processing, control, I/O and show workflow. Allen & Heath documents dLive around a MixRack containing processing, I/O and networking; Avid presents VENUE S6L as configurable surface, engine and I/O components; Yamaha documents RIVAGE PM as a component-based ecosystem with patching, networking and scene workflows.
These are reference architectures, not endorsements or claims about PROVANTAGE inventory. Availability, software compatibility, support and crew suitability must be verified for each production.
Before show day
A dependable file is more than a saved mix.
Confirm firmware and file compatibility, patching, labels, permissions, sample rate, clocking, network subscriptions, scene scope and recording paths. Keep controlled file versions and an accessible recovery copy.
Then test the system in the configuration in which it will actually operate. Documentation is valuable; a rehearsed response is better.
The PROVANTAGE position
Good console selection protects the production, not the equipment list.
We plan audio around the programme, venue, signal flow, operators and consequences of failure. The console follows those decisions.
Plan the technical brief