Rane HAL1x Design Guide - Page 118

Advanced Topics

Page 118 highlights

HAL SYSTEM DESIGN GUIDE the toggle to be a read-only control-a characteristic that has ramifications for the control links in which it participates: l When a link containing a read-only control is active, only the read-only control is enabled in the Halogen software. For example, if you link a two-position switch (connected via a Logic In port) to a Mute control in your Halogen Processing Map, you will no longer be able to toggle the Mute checkbox. It will be disabled in the software. Why is this? Because Halogen cannot send information to a read-only control, it has no way of keeping the controls in sync should one of the other controls in the link be changed within the software. When a read-only control participates in a link, only that control can be changed. l You cannot include more than one read-only remote device in a single control link. Why? Because read-only devices cannot track one another. l A read-only control link participant must be the control link's Link Master. In other words, because no other participants in the link can update the read-only control, the read-only control must be the participant in charge of updating the other participants. See below for details on the role of the Link Master. l You can configure each HAL Logic In port as a two position selector, allowing you to link the switch connected to the Logic In port to other two position selectors in your system. It is important to note that, in addition to being a read-only control, the Logic In selector can only have two selections. Therefore, once linked, you will no longer be able to increase the number of selections in other participants. For example, once a Logic In selector is linked with a two channel source selector, it is not possible to add channels to the Selector Block. Advanced Topics What issues should I consider when adding more than two controls in a single control link? When including three or more controls in a single control link, the direction in which you drag and drop new participants is important, as outlined below: l If using the All Links dialog box to create the control link, simply drag and drop the new participant onto the link in the All Links dialog box. OR l If using the control-to-control drag and drop method, when adding the third or greater control, always drop the new control onto a control already participating in the link. In other words, the control link target1 should be an existing participant. You can think of the control link like a party. If a person decides to join the party, the person goes to the party, the party doesn't come to the person! If you were to drop one of the link's existing participants onto a new control, Halogen would offer only two options: removing the source control from its existing links, and/or creating a new control link between the source and the target. If, however, you dropped the new participant onto the existing participant, Halogen would offer the option of adding the new participant to the existing control link. TIP: When creating a link that contains more than two controls, think of one control as the bucket into which you'll drop all the other controls. Of course, in keeping with the previous analogy of people coming to a party, you can think of this one control as the party host! 1The control onto which you will drop one or more other controls to create a control link. Think of the control link target as a bucket into which you place all the other controls participating in the link. 114

  • 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

the toggle to be a read-only control—a characteristic that has ramifications for the control links in which it
participates:
l
When a link containing a read-only control is active, only the read-only control is enabled in the Hal-
ogen software. For example, if you link a two-position switch (connected via a Logic In port) to a
Mute control in your Halogen Processing Map, you will no longer be able to toggle the Mute check-
box. It will be disabled in the software. Why is this? Because Halogen cannot send information to a
read-only control, it has no way of keeping the controls in sync should one of the other controls in the
link be changed within the software. When a read-only control participates in a link, only that control
can be changed.
l
You cannot include more than one read-only remote device in a single control link. Why? Because
read-only devices cannot track one another.
l
A read-only control link participant must be the control link's Link Master. In other words, because no
other participants in the link can update the read-only control, the read-only control must be the par-
ticipant in charge of updating the other participants. See below for details on the role of the Link
Master.
l
You can configure each HAL Logic In port as a two position selector, allowing you to link the switch
connected to the Logic In port to other two position selectors in your system. It is important to note
that, in addition to being a read-only control, the Logic In selector can only have two selections. There-
fore, once linked, you will no longer be able to increase the number of selections in other participants.
For example, once a Logic In selector is linked with a two channel source selector, it is not possible to
add channels to the Selector Block.
Advanced Topics
What issues should I consider when adding more than two controls in a single control link?
When including three or more controls in a single control link, the direction in which you drag and drop new
participants is important, as outlined below:
l
If using the
All Links
dialog box to create the control link, simply drag and drop the new participant
onto the link in the
All Links
dialog box.
OR
l
If using the control-to-control drag and drop method, when adding the third or greater control, always
drop the new control onto a control already participating in the link. In other words, the
control link
target
1
should be an existing participant. You can think of the control link like a party. If a person
decides to join the party, the person goes to the party, the party doesn't come to the person! If you
were to drop one of the link's existing participants onto a new control, Halogen would offer only two
options: removing the source control from its existing links, and/or creating a new control link
between the source and the target. If, however, you dropped the new participant onto the existing par-
ticipant, Halogen would offer the option of adding the new participant to the existing control link.
TIP
:
When creating a link that contains more than two controls, think of one control as the
bucket
into which you'll drop all the other controls. Of course, in keeping with the previous anal-
ogy of people coming to a party, you can think of this one control as the party host!
1
The control onto which you will drop one or more other controls to create a control link. Think of the control
link target as a bucket into which you place all the other controls participating in the link.
HAL SYSTEM DESIGN GUIDE
114