Aviom ASI - Manual (Page 27)

19 Asi c
oNNectioNs
Pro64 Parallel Connections
The ASI can be connected to any available port on an MH10 Merger Hub that
is part of the Pro64 network.
B A
B A
Input
B A
Output
B A
Input
B A
Output
B A
Input
B A
Input
B A
Output
1 2
Merger
3 4 5 6 7 8 9 10
B A
B A
Input
B A
Output
B A
Input
B A
Output
B A
Input
B A
Input
B A
Output
1 2
Merger
3 4 5 6 7 8 9 10
B A
B A
Input
B A
Output
B A
Input
B A
Output
B A
Input
B A
Input
B A
Output
1 2
Merger
3 4 5 6 7 8 9 10
B A B A
Input
B A
O
utput
B A
Input
B A
O
utput
B A
Input
B A
Input
B A
O
utput
1
2
M
er
ger
3
4
5
6
7
8
9
10
1 2
Merger
3 4 5 6 7 8 9 10
A B
Pro16 Pro64
A-Net Systems Interface
1-16 17-32 33-48 49-64
This diagram shows the ASI connected to a Merger Hub in parallel.
Channel Routing
To use the audio inputs connected to Pro64 input modules with Pro16
Personal Mixers via the ASI, connect audio signals in blocks of sixteen
channels that will map in a useful manner to the Pro16 devices. Each group
of sixteen Pro64 channels (1‑16, 17‑32, etc.) becomes a separate Pro16 stream
when output from the ASI. No remapping of channels is possible within the
A‑Net Systems Interface.
Connecting Pro16 Modules
Any Pro16 Series device with an available A‑Net In port can be connected to
the ASI.
Pro16 Series input modules (such as the AN‑16/i or AN‑16/i‑M) or console
interface cards (such as the Y1 card for Yamaha® digital consoles) should not
be connected to the ASI A‑Net Systems Interface.
 N
ote
: The ASI does not translate Pro16 Series A‑Net data into Pro64 Series
data. Do not connect the A‑Net outputs from Pro16 Series modules
to the Pro16 or Pro64 ports on the ASI.