Open topic with navigation
Toggle presets can be activated (turned on) and deactivated (turned off). A Toggle works like a checkbox in a software application. In other words, the user can select it to activate the preset and deselect it to deactivate the preset. For example, if you created a Toggle preset that mutes the audio in a specific zone, the user would activate the preset to mute the audio and deactivate the preset to un-mute the audio.
Toggle presets work independently from one another. For example, if you present the user with a list of Toggle presets, the user can select or deselect one or more of the presets in the list.
For more details on Toggle presets, see About Presets.
note: This example uses the same scenario as the Command preset example. Review both examples to understand the different work flow and strategy used for these different types of presets.
You're designing an audio system for a theater that has seating on the main floor and in two balcony levels. For some performances, the balconies are empty. For this reason, the theater personnel would like the ability to mute and un-mute the audio in those locations. You've decided to create a Toggle preset, one for each balcony, that mutes the audio and disables the DR that controls the volume (to prevent someone from accidentally turning it way up when the audio is muted).
note: For this procedure, we assume that the balconies are not muted and the DR1s located in the balconies are enabled in the Baseline preset.
Choosing the Appropriate Preset Control
As this is a Toggle preset example, we'll assume you've chosen the activate/deactivate preset model for your audio design! You choose a Toggle preset for this scenario because it requires an on/off action and is a standalone preset. You need two presets—one for each balcony—but you would not want to list these in a Selector group, as the two presets work independently from one another.
A DR2 works well in this situation (for end user control of the presets) as it can be configured to display one or more Toggle controls. You've decided to configure a single DR2 to display the Toggle presets for both balconies.
Halogen Configuration — Hardware Workspace
In this procedure, we configure the digital remote that will provide end user control over these presets.
note: For this scenario, we assume there is already a DR1 (for volume control) configured for each balcony location.
Halogen Configuration — Processing Workspace
In this procedure, we create the initial empty preset, configure the relevant blocks (muting the volume and disabling the volume control), and add them to the preset. The procedure outlines the creation of the upper balcony preset only. You would simply repeat the procedure to create the second preset, configuring the relevant parameters for the lower balcony, of course.
note: We assume the Processing Map has already been created and contains the appropriate processing blocks for this scenario. We also assume that the balconies are not muted and the DR1s located in the balconies are enabled in the Baseline preset.
In this example, we'll test only the Mute Upper Balcony preset. You would use the same procedure to test the lower balcony preset.
When the preset is activated, the DR1's Enable checkbox should be deselected and the Line Output block should turn red, indicating it is muted.
note: In this step, we are not only testing the preset, we are also testing the control link between the DR2 and the preset. If you want to test the preset directly, you can select and deselect the Active checkbox next to the preset in the All Presets dialog box.
When the preset is deactivated, the preset's block parameter values fall back to what's configured in the Baseline preset. Therefore, the DR1's Enable checkbox is selected and the Line Output block is un-muted.
Open topic with navigation