Rane HAL1x Design Guide - Page 149

CHAPTER 3: Key Audio Design Features another active preset containing this DR block existed above the Baseline in the Active Presets list1. BEST PRACTICE: Although you could return to the Baseline by asserting it over your activated Toggle and/or Selector presets, causing it to overlay every block in the system, we recommend against this practice. Because you cannot deactivate the Baseline, the only way to then get one of the lower priority Toggle or Selector presets above the Baseline is to deactivate and then activate it-a needless complication. The best way to return to the Baseline is to deactivate your Toggle and Selector presets. Working in Conjunction with Command Presets Command presets cannot be deactivated. They can only be asserted. Therefore, if you assert a Command preset (other than the Baseline) and want to return to the Baseline, you must assert the Baseline, which places it at the top of the preset priority list and overlays every setting of every processing block in your system. System Startup Options: You can configure HAL to power up into one of two possible states: its most recent state or the baseline preset. For details, see Configuring HAL Bootup Behavior in the Halogen Help System. WARNING! When you click Save Baseline in the Processing Workspace toolbar, all blocks in your Processing Map are saved to the Baseline with their current parameter values. If you only want to save the values for one block or a subset of blocks, do not click Save Baseline! You can instead update the Baseline for only that block or subset of blocks. For details, see Updating the Baseline Preset in the Halogen Help System. How do I create a preset? The first step when creating a preset is to decide how the preset should be controlled. Which approach do you plan to use-assertion or activation/deactivation? Will the preset be controlled by end users? If so, what type of remote hardware device are you using? Is the preset a standalone item or one of several choices? The answers to these questions help you choose which type of preset to create. Once you have decided on a preset control type, you then open the All Presets dialog box and create the initial (empty) preset into which you will drag and drop the appropriately configured blocks and controls that are relevant to the preset. Depending on the type of preset you are creating, the procedure differs slightly. See Creating Presets in the Halogen Help System for details. TIP: There are many ways to approach creation of a preset. You can set up the whole system and then drag the relevant blocks into the preset (remember that you can select and drag multiple blocks at once) or you can focus on one block at a time, dragging it into the preset when you finish the block's configuration. For particularly complex systems, the latter approach may prove easier to manage. Once I've created my presets, how do I give the end user control over the preset? This is the easy part! Once you've created your preset, you simply use control linking to provide end users with access to the preset. You create a control link that connects the preset to an appropriate remote hardware device. For example, if you created a Selector preset, you could link that preset to a DR2, DR3, or Logic In 1A dynamic list of active presets maintained by the system that changes as presets are asserted, activated, and deactivated. The presets are listed in priority order. When a preset is asserted or activated, it goes to the top of the list and its parameter values overlay the current working values for the corresponding system parameters. When a preset is deactivated it is removed from the list. 145