Rane HAL1x Design Guide - Page 151

All Presets, Preset References, Update, Is there a recommended work flow for creating presets?

Get Rane HAL1x PDF manuals and user guides View all Rane HAL1x manuals
Add to My Manuals
Save this manual to your list of manuals

Page 151 highlights

CHAPTER 3: Key Audio Design Features If you decide to use the ScratchPad feature, you will likely control it from within the Halogen software. If, however, you need to expose a control for enabling, disabling, and/or resetting the ScratchPad, you can do so using control links. The ScratchPad's two controls-the Enable/Disable Toggle control and the Reset Command control-can be linked to a DR or some other remote hardware device. We do not recommend exposing this control to end users, however, unless they have a thorough understanding of the ScratchPad's purpose and behavior. Is there a recommended work flow for creating presets? There are a variety of work flows you can use when creating presets, but we recommend the following: 1. Establish your Baseline preset by creating the default parameter values for all the blocks in your system, creating and testing the control links you want in your system (in its default state), and then saving everything to your Baseline preset. 2. Decide what preset control type best fits the scenario for which you are creating a preset. 3. Open the All Presets dialog box and add a new preset (of the control type you have decided upon). 4. For each block you want to save to the preset, configure its parameters appropriately and test the behavior (including relevant control links). When all blocks and control links are created and tested, select the relevant blocks and drag them into the preset. 5. Test the preset. 6. Return to (or assert) your Baseline preset and begin at step 3 to create your next preset. 7. Repeat steps 3 through 6 until you have created all the presets you need. 8. If several presets contain the same block or control link, test their interactions and make any necessary adjustments in to get the behavior you want. Be sure to review the control link priorities. 9. Test all presets. An alternate approach: 1. Create your Baseline preset as outlined in the above procedure. 2. Create all your anticipated presets in the All Presets dialog box. These presets will be empty until you add the relevant blocks. 3. Drag a block into all the presets that should contain it. 4. Click the square in the middle of the blue preset bar at the bottom of the block to open the block's Preset References dialog box. 5. Configure that block appropriately for one of the presets. 6. In the Preset References dialog box, click Update for the relevant preset. 7. Reconfigure the block for another of the presets and then click Update for that preset. 8. Continue until you have added the properly-configured block to all the presets that contain it. 9. Repeat steps 3 through 8 for each system block contained in one or more of your presets. 10. If more than one of your presets contain control links, review the control link priority list to adjust their priorities, if necessary. 11. Test all presets. What are some best practices when designing and working with presets? BEST PRACTICE: Early in your design process, decide what the default state should be for each block, hardware control, and control link in your system, configure these items accordingly, and save them to 147

  • 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
If you decide to use the ScratchPad feature, you will likely control it from within the Halogen software. If,
however, you need to expose a control for enabling, disabling, and/or resetting the ScratchPad, you can do so
using control links. The ScratchPad's two controls—the Enable/Disable Toggle control and the Reset Com-
mand control—can be linked to a DR or some other remote hardware device. We do not recommend expos-
ing this control to end users, however, unless they have a thorough understanding of the ScratchPad's purpose
and behavior.
Is there a recommended work flow for creating presets?
There are a variety of work flows you can use when creating presets, but we recommend the following:
1.
Establish your Baseline preset by creating the default parameter values for all the blocks in your sys-
tem, creating and testing the control links you want in your system (in its default state), and then sav-
ing everything to your Baseline preset.
2.
Decide what preset control type best fits the scenario for which you are creating a preset.
3.
Open the
All Presets
dialog box and add a new preset (of the control type you have decided upon).
4.
For each block you want to save to the preset, configure its parameters appropriately and test the
behavior (including relevant control links). When all blocks and control links are created and tested,
select the relevant blocks and drag them into the preset.
5.
Test the preset.
6.
Return to (or assert) your Baseline preset and begin at step 3 to create your next preset.
7.
Repeat steps 3 through 6 until you have created all the presets you need.
8.
If several presets contain the same block or control link, test their interactions and make any nec-
essary adjustments in to get the behavior you want. Be sure to review the control link priorities.
9.
Test all presets.
An alternate approach:
1.
Create your Baseline preset as outlined in the above procedure.
2.
Create all your anticipated presets in the
All Presets
dialog box. These presets will be empty until
you add the relevant blocks.
3.
Drag a block into all the presets that should contain it.
4.
Click the square in the middle of the blue preset bar at the bottom of the block to open the block's
Preset References
dialog box.
5.
Configure that block appropriately for one of the presets.
6.
In the
Preset References
dialog box, click
Update
for the relevant preset.
7.
Reconfigure the block for another of the presets and then click
Update
for that preset.
8.
Continue until you have added the properly-configured block to all the presets that contain it.
9.
Repeat steps 3 through 8 for each system block contained in one or more of your presets.
10.
If more than one of your presets contain control links, review the control link priority list to adjust
their priorities, if necessary.
11.
Test all presets.
What are some best practices when designing and working with presets?
BEST PRACTICE
:
Early in your design process, decide what the default state should be for each block,
hardware control, and control link in your system, configure these items accordingly, and save them to
CHAPTER 3: Key Audio Design Features
147