Rane HAL1x Design Guide - Page 150

Resetting or Disabling the ScratchPad, Controlling the ScratchPad, Disable the ScratchPad

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 150 highlights

HAL SYSTEM DESIGN GUIDE that is configured to behave as a Selector. If you created a Toggle preset, you could link it to a Logic In device, or to a Toggle control displayed on a DR2 or DR3. If you created a Command preset, you could link it to a Command control displayed on a DR2 or DR3 or to a Logic In configured as a Command control. For procedural details, see Linking a Preset to a DR or Other Remote Device in the Halogen Help System. If an end user remotely changes a preset value (for example, increases the volume), can I capture that new value for future use? Yes you can. HAL System presets contain a handy feature called Scratch Pad, that tracks and stores changes made to any of the preset values. NOTE: By changes, we mean changes made dynamically, usually by an end user, not changes actively saved to the preset itself. Let's walk through an example to illustrate how Scratch Pad works. Suppose your system contains a preset that configures a room's audio for Friday Night Bingo. The same crowd usually shows up every Friday night and it seems they always have to turn up the volume to hear the announcer. Wouldn't it be nice if each time you activate your Friday Night Bingo preset, it could return the room to the settings as adjusted by the Bingo audience members instead of returning to the original preset values? With Scratch Pad, you can do this! You simply enable the Scratch Pad feature for the Friday Night Bingo preset. It then keeps track of any changes made to any of the preset's block parameters. The next time you activate Friday Night Bingo, it remembers the last change the Bingo attendees made to the volume and returns that value. Scratch Pad works on a preset level, never affecting any preset other than its own. In other words, each preset has its own, dedicated Scratch Pad. By default, a preset's Scratch Pad is disabled. For details on enabling it, see Enabling/Disabling Scratch Pad in the Halogen Help System. You cannot enable the ScratchPad for a subset of the preset's blocks. Once enabled, it monitors the preset parameters for all of the preset's blocks and if one of them changes, it tracks the change. If the same parameter changes again, the ScratchPad overwrites the old change with the new one-thus it keeps only the last value for each changed parameter. When the preset is activated again, it uses the ScratchPad values. Resetting or Disabling the ScratchPad So what happens if, once the ScratchPad is enabled and begins saving changed parameter values, you want to return to your original preset values? Rest assured that those original values are safe and sound and never altered by the ScratchPad. The HAL System provides you with two options for returning to those values: l Disable the ScratchPad: When you disable the ScratchPad, the preset returns to its original values the next time it is applied, the ScratchPad values disappear, and the ScratchPad no longer tracks changes to the preset values. l Reset the ScratchPad: When you reset the ScratchPad, its values return to those of the original preset, but it is still enabled and will continue tracking any changes to those values. You should always deactivate a preset before resetting its ScratchPad. If you tried to reset an active preset's ScratchPad (in other words, the preset's ScratchPad is tracking the current working values of the system), nothing would change. This may sound confusing, but it's actually quite simple. If you reset an active preset's ScratchPad, the ScratchPad's values return to the original preset values but the ScratchPad then immediately saves the current working values-as that's its job. So, in essence, you're back where you started before you reset the ScratchPad. BEST PRACTICE: Avoid performing a ScratchPad reset when the preset is active. Controlling the ScratchPad 146

  • 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
that is configured to behave as a Selector. If you created a Toggle preset, you could link it to a Logic In
device, or to a Toggle control displayed on a DR2 or DR3. If you created a Command preset, you could link
it to a Command control displayed on a DR2 or DR3 or to a Logic In configured as a Command control.
For procedural details, see Linking a Preset to a DR or Other Remote Device in the Halogen Help System.
If an end user remotely changes a preset value (for example, increases the volume), can I capture that
new value for future use?
Yes you can. HAL System presets contain a handy feature called Scratch Pad, that tracks and stores changes
made to any of the preset values.
NOTE
:
By
changes
, we mean changes made dynamically, usually by an end user, not changes actively
saved to the preset itself.
Let's walk through an example to illustrate how Scratch Pad works. Suppose your system contains a preset
that configures a room's audio for Friday Night Bingo. The same crowd usually shows up every Friday night
and it seems they always have to turn up the volume to hear the announcer. Wouldn't it be nice if each time
you activate your Friday Night Bingo preset, it could return the room to the settings as adjusted by the Bingo
audience members instead of returning to the original preset values? With Scratch Pad, you can do this! You
simply enable the Scratch Pad feature for the Friday Night Bingo preset. It then keeps track of any changes
made to any of the preset's block parameters. The next time you activate Friday Night Bingo, it
remembers
the last change the Bingo attendees made to the volume and returns that value.
Scratch Pad works on a preset level, never affecting any preset other than its own. In other words, each preset
has its own, dedicated Scratch Pad. By default, a preset's Scratch Pad is disabled. For details on enabling it,
see Enabling/Disabling Scratch Pad in the Halogen Help System. You cannot enable the ScratchPad for a sub-
set of the preset's blocks. Once enabled, it monitors the preset parameters for all of the preset's blocks and if
one of them changes, it tracks the change. If the same parameter changes again, the ScratchPad overwrites the
old change with the new one—thus it keeps only the last value for each changed parameter. When the preset
is activated again, it uses the ScratchPad values.
Resetting or Disabling the ScratchPad
So what happens if, once the ScratchPad is enabled and begins saving changed parameter values, you want to
return to your original preset values? Rest assured that those original values are safe and sound and never
altered by the ScratchPad. The HAL System provides you with two options for returning to those values:
l
Disable the ScratchPad:
When you disable the ScratchPad, the preset returns to its original values the
next time it is applied, the ScratchPad values disappear, and the ScratchPad no longer tracks changes
to the preset values.
l
Reset the ScratchPad:
When you reset the ScratchPad, its values return to those of the original preset,
but it is still enabled and will continue tracking any changes to those values. You should always deac-
tivate a preset before resetting its ScratchPad. If you tried to reset an active preset's ScratchPad (in other
words, the preset's ScratchPad is tracking the current working values of the system), nothing would
change. This may sound confusing, but it's actually quite simple. If you reset an active preset's Scratch-
Pad, the ScratchPad's values return to the original preset values but the ScratchPad then immediately
saves the current working values—as that's its job. So, in essence, you're back where you started before
you reset the ScratchPad.
BEST PRACTICE
:
Avoid performing a ScratchPad reset when the preset is active.
Controlling the ScratchPad
HAL SYSTEM DESIGN GUIDE
146