Understanding Scenes on Your Live Sound Console

Scenes are a powerful feature found on nearly every modern digital live sound console, from compact mixers like the Behringer X32 to large-format desks like the DiGiCo SD series. A scene is essentially a snapshot of your mixer’s current state—it captures fader positions, EQ curves, dynamics settings, auxiliary send levels, bus routing, FX parameters, and even mute groups. When you save a scene, you freeze a complete configuration that can be recalled instantly, allowing you to switch between drastically different mixes for different songs, acts, or sections of a performance.

Scenes go beyond simple presets. While a preset might save a specific effect or channel strip setting, a scene encompasses the entire console. This makes scenes indispensable for theatrical productions with multiple acts, festival setups where different bands share the same console, or any show where you need to transition smoothly between distinct sound requirements.

Most digital consoles offer scene management that includes naming, numbering, and even password-protected scenes. Understanding the full capabilities of your console’s scene system is the first step to using it effectively. For example, the Allen & Heath dLive allows scenes to store not only the mixer state but also the recall of the entire surface layout, while the Yamaha CL series offers scene crossfade times to avoid abrupt changes. Knowing these nuances will help you tailor your scene workflow to your console.

Step-by-Step Guide to Programming a Scene

The basic process of saving a scene is similar across most consoles, but the exact button names and sequences vary. Below is a general workflow that applies to the majority of digital boards. Consult your console’s manual for specifics, but the principles remain universal.

1. Set Up Your Mix

Before saving, dial in your desired settings for a particular part of the show. This includes fader levels, EQ, dynamics, FX sends, and routing. For example, if you are programming a scene for a ballad that requires a reverb-heavy vocal and quieter drums, adjust those elements on your console. Make sure all channels, groups, and matrixes are configured exactly as you want them to be recalled.

2. Enter Scene Save Mode

Most consoles have a dedicated scene section on the surface, often with buttons labeled “Store,” “Save,” “Scene Memory,” or a numeric keypad. In digital desks, you may need to press a “Screens” button and then select “Scene” from the touchscreen. For example, on the QSC TouchMix, you tap the “Scenes” tab and then “Save.” On the Yamaha CL5, you press the “Scene Memory” button and then use the dialogue on the screen.

3. Choose a Destination

You will be prompted to select a scene number or slot. Some consoles automatically assign the next available number; others let you choose from a list. Pick a location that is easy to remember—many engineers group scenes in blocks of 10 (e.g., scenes 1-10 for setlist order, 11-20 for backups). If your console supports it, also give the scene a descriptive name like “Intro Song” or “Act 2 Jazz.”

4. Confirm and Save

Once you have selected the slot and entered a name, press “Store,” “Enter,” “Save,” or whatever confirmation the console requires. Some desks ask if you want to save the current state and overwrite any existing scene; confirm that you do. The console will then write the scene to memory, often with a brief progress indicator. Always double-check that the scene is saved by recalling it later.

5. Test Recall

After saving, switch to a different scene or reset the console (if safe to do so) and then recall the scene you just saved. Verify that all settings load correctly. Pay special attention to any parameters that might be excluded from recall—some consoles allow you to “mask” certain inputs or outputs so they are not affected when you call up a scene. If something is missing, check the recall scope settings (see below).

Advanced Scene Management Techniques

Basic scene programming is just the beginning. To truly master live sound, you need to understand how to manage scenes efficiently and avoid pitfalls during a show.

Recall Scope and Safety

Most digital consoles allow you to define what a scene actually recalls. This is called “recall scope” or “filter.” For example, you might want a scene that changes only the reverb settings for a ballad but leaves all fader levels unchanged. In the Yamaha CL series, this is done through “Recall Safe” and “Recall Filter.” In the Behringer X32, you can use “Safes” to protect individual channels or parameters. Using recall scope wisely prevents unintended changes—for instance, you can safe the master fader so it never jumps when you hit a scene.

Similarly, “Scene Safe” or “Global Safe” parameters let you lock critical elements like the main output mute, the head amplifier gain (if you are using a separate gain stage), or talkback mics. Always set these safes before a show.

Naming and Organization

A well-named scene list is a lifesaver in a fast-paced show. Use clear, consistent naming that includes the song number, title, and key features. For example: “01-Intro (Piano + Vocal),” “02-Rock Anthem (Heavy Drums),” “03-Ballad (Verb+Delay).” Avoid vague names like “Scene 4” or “New Scene.” Many consoles let you reorder scenes in a list; do this in rehearsal to match your setlist sequence. If your console supports scene comments or notes, add reminders like “Check wireless mics” or “Guitarist capo.”

Scene Crossfade and Transition

Abrupt scene changes can cause clicks, pops, or jarring volume jumps. Higher-end consoles offer scene crossfade or fade times. For example, the Yamaha CL and QL series allow you to set a fade time for fader movements when recalling a scene, so the mixer transitions smoothly over a few seconds. The Allen & Heath Avantis has a “Scene Fade” per channel. If your console supports this, use it for transitions that need subtlety, such as moving from a sparse interlude to a full band section.

Backup and Export

Scenes stored only in the console’s internal memory can be lost if the desk resets during setup or if you work on multiple shows. Always back up your scene files to a USB drive, SD card, or via Ethernet to a computer. Most modern digital mixers support exporting scenes as individual files or show files. On the Behringer X32, you can save to USB and load later. On the Soundcraft Vi series, you can archive entire shows. Consider keeping a backup drive in your gig bag, and make sure the file format is compatible with your specific firmware version.

Using Scenes in a Live Performance

Recalling scenes during a show is straightforward, but doing it seamlessly requires practice and discipline.

Recall Methods

You can typically recall a scene by pressing a dedicated scene recall button and entering the scene number, or by scrolling through a scene list on a touchscreen. Some consoles have hardware buttons that can be assigned to specific scenes (like function keys or user-assignable switches). In large venues with a monitor engineer, you might use MIDI or OSC commands to trigger scenes remotely from a laptop or midi controller. For example, the DiGiCo SD series supports MIDI scene recall, which can be triggered by a guitar rig or a click track.

Modifying Scenes on the Fly

During a performance, you may need to tweak a scene—for example, if a vocalist is singing louder than during sound check. To modify a recalled scene, simply adjust the mixer settings while the scene is active. Then, if you want to save those changes, perform a save operation with the same scene number. Many consoles will ask whether you want to overwrite the existing scene. Be careful: if you overwrite the original, you lose the previous version. Consider saving a modified scene to a new number first, then rename it as needed.

Building a Scene List for a Show

For a multi-song set, create a scene for each song, or for specific transitions (e.g., scene for announcement with only vocal and acoustic guitar, then scene for full band). Arrange scenes in chronological order. In rehearsal, practice recalling scenes with the band so you can anticipate any issues. Some engineers use a separate scene for the beginning of each song and then recall it just before the downbeat. If your console allows, you can chain scenes so that recalling a scene automatically enables the next one (like cue lists on an ETC lighting console), but this is rare on audio desks.

Common Pitfalls and Troubleshooting

Even experienced engineers can run into problems with scenes. Here are some common issues and how to avoid them.

  • Unintended fader jumps: If fader positions jump between scenes, use recall safe on critical faders like the main mix bus, or enable crossfade. Alternatively, use the console’s “Fader Glide” if available.
  • Scene not recalling all parameters: Check the recall filter. Often, certain parameters like routing, FX parameters, or head amp gain are excluded by default. Adjust the scope to include what you need.
  • Scene missing after power cycle: Did you save to internal memory? Some consoles require you to explicitly save the scene to a file. After saving, check that it is still present after a reboot. Back up to external media.
  • Accidentally overwritten scene: Use confirmation dialogs if the console asks. Some desks have an “Undo” function for scene recalls—familiarize yourself with it before the show.
  • MIDI or OSC triggers not working: Verify that the console’s MIDI settings are correct (channel, note numbers, program change). Test with a simple trigger before the show.

Best Practices for Scene Management

To get the most out of your console’s scene capabilities, adopt these habits during setup and performance.

  • Start with a clean console: Before programming scenes, reset the console to a blank default state to avoid carrying over old settings.
  • Label everything: Not just scenes, but also channels, buses, and FX slots. A well-labeled console reduces confusion when recalling scenes.
  • Use scene notes: Document the purpose of each scene, any special considerations (e.g., “Scene 5: acoustic set – make sure guitar DI is unmuted”).
  • Test recall during sound check: Recall each scene with the band playing to confirm no parameters are missed. Especially check mute groups, FX sends, and monitor mixes.
  • Keep a paper backup: Print a scene list with names and numbers. If the touchscreen fails or the scene list becomes corrupted, you can quickly rebuild from notes.
  • Update scenes after sound check: As you make tweaks, save the final versions. Do not rely on memory—save changes immediately.

Conclusion

Mastering the art of programming and saving custom scenes on a live sound console is one of the most impactful skills you can develop as a front-of-house or monitor engineer. Scenes give you the ability to move between vastly different mixes instantly, freeing you to focus on the performance rather than fumbling with faders. By understanding recall scope, safe parameters, naming conventions, and backup strategies, you can avoid common mistakes and deliver a seamless show night after night. Spend time learning the specific scene features of your console—refer to the manufacturer’s documentation for Behringer X32 scene tutorials or Allen & Heath’s dLive scene management guide—and practice your workflow until it becomes second nature. Your audience and your band will thank you for the polished, consistent sound that only meticulous scene programming can deliver.