AuviTran AVM500-ES, Руководство пользователя

Страница: 13 / 52

Powering an AVM500-ES for the first time
Fig. 4: Example of architecture
In this network, the AVY16-ES100 in the LS9 mixing console is the Primary Master (PM). Indeed, there is no EtherSound
network plugged on its In port, but only the control PC. The Out port of the AVY16-ES100 is connected to port {Ain} of the
AVM500-ES. Ports {B, C, D}, that are Outputs ports, are connected respectively to port In of DME4io, NAI48-ES and NXAmp
4x4. Port {E} is unused.
Remember that in this example, the AVY16-ES100 is PM, so it generates the audio clock. This clock is transmitted to the
AVM500-ES port {Ain} through EtherSound. As described in the previous paragraph, AVM500-ES propagates the clock from
{Ain} to {B, C, D, E}, so the three third-party devices are properly feed with clock.
When running AuviTran ES-Monitor software on the control PC, the Tree View of this network will be the following:
Fig. 5: Hierarchy view of example architecture
The AVY16-ES100 is obviously the Primary Master, followed by port {Ain} of the AVM500-ES. Ports {B, C, D, E} are on the
same hierarchy level, as expected. And behind each port, we can find our three EtherSound devices.
AVM500-ES User’s Manual v2.1 AuviTran 2010 13