A Command preset can only be turned on (asserted). Unlike Toggle and Selector presets, it cannot be turned off. Once a Command preset is asserted, the only way to overwrite its parameter values in the system is to assert or activate another preset. Therefore, a common practice when using Command presets is to create them in pairs—one preset containing the specific settings you need and another preset with opposite settings. Of course, if you want to return to the system default settings, you can simply assert the Baseline preset over the currently active Command preset. For more details on Command presets, see About Presets.
note: This example uses the same scenario as the Toggle 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. When a balcony is muted, they also want the end user volume control device in that balcony to be disabled (to prevent someone from accidentally turning it way up when the audio is muted).
Choosing the Appropriate Preset Control
As this is a Command preset example, we'll assume you've chosen the assert preset model for your audio design! The only preset type available to you if you want to use the assert approach is the Command preset. To give you maximum control and flexibility, you've decided to create your Command presets in pairs whenever possible. In this scenario, you'll create a pair of presets for each balcony. One preset mutes the audio and disables the DR that controls the volume and the other preset un-mutes the audio and enables the volume control DR.
A DR2 works well in this situation (for end user control of the presets) as it can be configured to display one or more Command controls. You've decided to configure a single DR2 to display the Command 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 presets for one of the preset pairs, configure the relevant blocks (muting the volume and disabling the volume control, and then un-muting the volume and enabling the volume control), and add them to their respective preset. The procedure outlines the creation of the upper balcony preset only. You would simply repeat the procedure to create the preset pair for the lower balcony, configuring the relevant block 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.
In this example, we'll test only the upper balcony presets. You would use the same procedure to test the lower balcony presets.
When the preset is asserted, 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 the Assert checkbox next to the preset in the All Presets dialog box.
When the preset is asserted, the DR1's Enable checkbox should be selected and the Line Output block should no longer be muted.