Rane HAL1x Design Guide - Page 152

Active Presets list, Save Baseline, Baseline, When you click

Page 152 highlights

HAL SYSTEM DESIGN GUIDE your Baseline. You can configure your entire system and save it to the Baseline all at once, or you can move from block to block, saving each block to the Baseline as you go. See Customizing the Baseline Preset for procedural details. BEST PRACTICE: Name your presets as soon as you create them. This helps alleviate confusion later. Note that all preset names must be unique. BEST PRACTICE: When creating presets, a good approach is to think through and configure blocks for the entire preset, test the functionality, and then select all the relevant blocks and drag them to the preset. BEST PRACTICE: Try to avoid including the same blocks in different types of presets (with the exception of the Baseline, of course, as it contains every block in the system. Including the same block in different types of presets makes management of the presets and the block parameters values much more difficult. It's okay to use different preset types as long as they are independent from one another (again, the Baseline is an exception). BEST PRACTICE: Avoid asserting the Baseline unless you are using only Command presets. Asserting the Baseline over a Toggle or Selector preset creates a dilemma. To then place the Toggle or Selector above the Baseline (in the Active Presets list1), you would have to deactivate and then re-activate it. In this scenario, the best way to return to the Baseline is to deactivate the Toggle and Selector presets. BEST PRACTICE: Because a preset cannot change a control link's priority, it is very important to confirm that your control links are prioritized correctly for the behavior that you want. It is always a good idea to double-check the control link priority list before, during, or after your creation of presets. Of course, testing your presets also helps you determine if your links are working according to plan when the presets are activated. BEST PRACTICE: Avoid performing a ScratchPad reset when the preset is active. 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 or a subset of blocks, do not click Save Baseline! You should instead update only those specific blocks in the Baseline. For details, see Updating the Baseline Preset in the Halogen Help System. 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. 148

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196

your Baseline. You can configure your entire system and save it to the Baseline all at once, or you can
move from block to block, saving each block to the Baseline as you go. See Customizing the Baseline
Preset for procedural details.
BEST PRACTICE
:
Name your presets as soon as you create them. This helps alleviate confusion later.
Note that all preset names must be unique.
BEST PRACTICE
:
When creating presets, a good approach is to think through and configure blocks for
the entire preset, test the functionality, and then select all the relevant blocks and drag them to the pre-
set.
BEST PRACTICE
:
Try to avoid including the same blocks in different types of presets (with the excep-
tion of the Baseline, of course, as it contains every block in the system. Including the same block in dif-
ferent types of presets makes management of the presets and the block parameters values much more
difficult. It's okay to use different preset types as long as they are independent from one another (again,
the Baseline is an exception).
BEST PRACTICE
:
Avoid asserting the Baseline unless you are using only Command presets. Asserting
the Baseline over a Toggle or Selector preset creates a dilemma. To then place the Toggle or Selector
above the Baseline (in the
Active Presets list
1
), you would have to deactivate and then re-activate it. In
this scenario, the best way to return to the Baseline is to deactivate the Toggle and Selector presets.
BEST PRACTICE
:
Because a preset cannot change a control link's priority, it is very important to confirm
that your control links are prioritized correctly for the behavior that you want. It is always a good idea
to double-check the control link priority list before, during, or after your creation of presets. Of course,
testing your presets also helps you determine if your links are working according to plan when the pre-
sets are activated.
BEST PRACTICE
:
Avoid performing a ScratchPad reset when the preset is active.
WARNING
!
When you click
Save Baseline
in the Processing Workspace toolbar,
all blocks
in your Proc-
essing Map are saved to the Baseline with their current parameter values. If you only want to save the
values for one or a subset of blocks, do
not
click
Save
Baseline
! You should instead update only those
specific blocks in the Baseline. For details, see Updating the Baseline Preset in the Halogen Help Sys-
tem.
1
A dynamic list of active presets maintained by the system that changes as presets are asserted, activated, and deac-
tivated. 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 pre-
set is deactivated it is removed from the list.
HAL SYSTEM DESIGN GUIDE
148