Rane HAL1x Design Guide - Page 99

When should I use a Distributed Program Bus?

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

CHAPTER 3: Key Audio Design Features The following image illustrates the relationship between the Distributed Program Bus and Zone Processor block: When should I use a Distributed Program Bus? To determine if a Distributed Program Bus would be useful in your system, ask yourself this question: Does my system contain one or more audio inputs that are common to two or more of my output zones? If yes, then a Distributed Program Bus may be the right block for you! TIP: Remember that, when using the Zone Processor block or Room Combine Processor block to define your zones, the Distributed Program Bus and all of its inputs are included automatically. You cannot specify which inputs to include or exclude. If you need only one of its inputs for a certain zone, you could select that input and avoid exposing the other input selections (in other words, do not provide end users with input selection control in that zone). NOTE: Including a Distributed Program Bus does not eliminate the addition of local audio sources for a specific zone. See details on the facing page. How do I create a Distributed Program Bus and then incorporate it into my system? The process for creating the Distributed Program Bus is very simple. From the DSP palette in the Processing Workspace, you drag a Distributed Program Bus block into your Processing Map. You configure the inputs that will be common to all zones (zones defined by a Zone Processor or Room Processor block) and then connect them to the Distributed Program Bus. You provide custom names for each input. And you're done! NOTE: An audio system can contain only one Distributed Program Bus. To then incorporate those inputs into your zones, you drag Zone Processor blocks (from the DSP palette) into your Processing Map, connecting them to your system. Each Zone Processor block automatically includes a connection to the Distributed Program Bus. There is nothing more you need to do to connect its channels into your system. NOTE: When working in a Room Combine situation, the Distributed Program Bus is automatically included in each Room Processor. 95

  • 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 following image illustrates the relationship between the Distributed Program Bus and Zone Processor
block:
When should I use a Distributed Program Bus?
To determine if a Distributed Program Bus would be useful in your system, ask yourself this question: Does
my system contain one or more audio inputs that are common to two or more of my output zones? If yes,
then a Distributed Program Bus may be the right block for you!
TIP
:
Remember that, when using the Zone Processor block or Room Combine Processor block to define
your zones, the Distributed Program Bus and all of its inputs are included automatically. You cannot
specify which inputs to include or exclude. If you need only one of its inputs for a certain zone, you
could select that input and avoid exposing the other input selections (in other words, do not provide
end users with input selection control in that zone).
NOTE
:
Including a Distributed Program Bus does not eliminate the addition of local audio sources for a
specific zone. See details on the facing page.
How do I create a Distributed Program Bus and then incorporate it into my system?
The process for creating the Distributed Program Bus is very simple. From the
DSP
palette in the Processing
Workspace, you drag a Distributed Program Bus block into your Processing Map. You configure the inputs
that will be common to all zones (zones defined by a Zone Processor or Room Processor block) and then con-
nect them to the Distributed Program Bus. You provide custom names for each input. And you're done!
NOTE
:
An audio system can contain only one Distributed Program Bus.
To then incorporate those inputs into your zones, you drag Zone Processor blocks (from the
DSP
palette) into
your Processing Map, connecting them to your system. Each Zone Processor block automatically includes a
connection to the Distributed Program Bus. There is nothing more you need to do to connect its channels
into your system.
NOTE
:
When working in a Room Combine situation, the Distributed Program Bus is automatically
included in each Room Processor.
CHAPTER 3: Key Audio Design Features
95