Learn how to configure the essential mixer settings for the eMotion LV1 live mixer, including channel parameters, latency and buffer settings, and more.
In this video, we’ll get in touch with page 2 of 3 Settings pages: The MIXER page. Here, you’ll learn how to:
- Configure mixer size; (16-channel, 32-channel, or 64-channel).
- Assign controls and channel parameters.
- Optimize latency and buffer settings.
- Build, Customize, and Save personalized plugin, routing and mixer parameter settings for each individual scene and session.
- Sync Mixer Tempo to compatible plugins.
This page is where the behavior of the eMotion LV1 is set. Create tailor-made, system-wide preferences to suit any of your project needs.
Use the Mixer Settings page to establish the mixer configuration, set latency compensation, define auto-save rules, and more.
The Mixer Configuration section sets the size of the mixer. This includes the number of channels, Auxes, and main outs; and whether or not matrix and groups are available.
The eMotion LV1 mixer can have 16, // 32, // or 64 channels, plus up to 8 stereo groups, 16 mono or stereo aux channels, Left/Right, Center, and Mono main outs, and an 8-channel matrix. The maximum mixer size is determined by the eMotion LV1 license.
Usually, you’ll set mixer size when you create a session. If you know how many channels you’ll use, then it makes sense to start with the right-sized configuration. You can also change the mixer configuration of an active session.
If you increase the number of channels, no harm will come to the session, since you’ve not removed any information. But, if you reduce the number of channels in a session, certain information is, of course, lost. Parameters in channels that are no longer part of the session will be discarded.
It’s a good idea to save a session under a new name before you reduce its size.
The Mixing Engine Performance panel sets the mixer’s internal processing priority, which affects DSP performance.
In the Latency Optimized mode, a processing cycle between the mixer and the server CPU must include all the mixer’s signal paths at once, so there is no internal routing latency. However, processing in this mode can be less DSP efficient with certain plugins.
In the DSP Optimized mode, processing can spread across several buffer cycles. This parallel processing gives you greater DSP efficiency. Each buffer has greater processing headroom so this mode can more easily handle plugins that create big peak loads. Latency varies based on the mixer’s internal routing configuration. Certain paths will have zero latency, even in the DSP Optimized mode.
For example, here’s a simple route that has zero internal latency:
I/O → INPUT → AUX MONITOR → I/O
However, this route has more stages and does exhibit internal latency:
I/O → INPUT → GROUP → MASTER → MATRIX → I/O
(In this case, 16 samples)
The server network buffer is the actual amount of time it takes for audio to do the roundtrip between the mixer and the server. This determines the maximum processing latency.
The Server Network Buffer size is set in the Server Rack of the System Inventory page:
- A buffer size of 40-56 Samples provides for an internal routing latency of 0-32 Samples
- A buffer size of 80-112 Samples provides for an internal routing latency of 0-64 Samples
- A buffer size of 160-224 Samples provides for an internal routing latency of up to 128 Samples
(These calculations are based on a sample rate of 48 kHz.)
Plugins that exhibit large intermittent processing spikes can delay the entire processing chain beyond the limits of the network buffer.
This is indicated on the DSP meter as a large average-peak DSP ratio:
The Green area displays average DSP use - The Orange line shows peak use.
*If this ratio is especially large, the processor may overload. Should the peak DSP load reach 85%, the display will turn Yellow. Adjust your DSP use, or you may encounter drops. Remove or disable whatever plugins you can. If this doesn’t help, then switch to the DSP Optimized mode. Or, enlarge your server’s network buffer value.
The Output Routing Latency section sets alignment behavior of the output I/Os. There are two options.
- Entire Mixer Aligned sets the whole mixer to one common delay group. All outputs will be latency aligned. There are no separate delay groups.
- Align by Mix Buss - Delay Group enables up to 16 user-definable delay groups, each of which can have separate delays. Every group is aligned internally.
Mixer Startup sets the condition of the mixer when it launches.
- Previous Session loads the last session, based on its most recent user save.
- Last State loads the most recent session, based on its last auto-save.
- When set to Empty Session, the mixer opens with a blank session each time.
- The History section sets the rules of automatic saving.
Auto Save Every (_) Minutes
This turns auto-save on or off. The save interval is set with a drop-down menu. Range is 3–30 minutes.
When On Scene Update is on an Auto Save session is created each time a scene is stored or recalled.
To load an auto-save History Session:
- Go the Session page of the Show window
- Click “History”
- Browse for a file
History files are not deleted; new saves do not replace old saves. Delete session files using the host operating system.
The entire mixer surface—or selected mixer actions—can be locked to prevent unintended ‘structural’ changes in a session, such as adding, removing, or copying plugins, or changing external patches. Locking these controls does not affect parameters or internal routing.
Activate selected lock options with the Lock button on the right side of the Top Bar.
You can also lock the mixer interface, with or without a password. This does not affect the mixer; it just means you can’t change anything.
There are two options in the Troubleshooting section:
- Enable Logging creates a report that’s used by Waves technical support for troubleshooting and customer service. The report file is placed on the host computer’s desktop. De-select this for normal operation.
- When Show Patch Warnings selected, a prompt is shown whenever you try to create or change a patch in the Patch Window.
Click Update Plugins List to scan the system for new plugins and licenses.
The Tempo button sets the tempo for all relevant plugins in the mixer. Most tempo-based Waves plugins can lock to the tempo of the host application.
To set the tempo:
- Tap the tempo button.
- Or, Ctrl +T on the keyboard.
These taps are averaged to create a tempo value. You can also enter a numeric value. The flashing tempo light helps to determine if the setting is correct. You can also control the Tempo key from an assignable key and from many control devices.
As we’ve seen in this tutorial, the Mixer Settings page is used to set up the basic configuration and behavior of the mixer.
In the next video tutorial you’ll learn about the User Interface page, where you set up meters and program user-assignable keys.