March 2013
About this Guide In recent years, several network technologies have emerged for centralized management and control of large scale audio installations. This guide focuses on EtherSound, a digital audio transmission protocol developed by Digigram of France. Using a single CAT5e cable, up to 64 channels of audio may be transmitted in both directions. Compliant with IEEE802.
Contents Step 0 Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 System Description ････････････････････････････････････････ 3 Physical Setup ････････････････････････････････････････････ 4 Launching AVS-Monitor ･････････････････････････････････ 6 Bidirectional Loop Settings ･････････････････････････････････ 9 Wordclock Settings ･･･････････････････････････････････････ 16 Making Audio Patches ････････････････････････････････････ 21 Remote Head Amp Control ････････････････････････････････ 30 Making the
Step 0 System Description Step 0 System Description We will use a typical example to explain the configuration procedure for EtherSound networks.
Step 1 Physical Setup Step 1 Physical Setup Connecting Devices Connect EtherSound devices in a daisy chain by connecting the OUT port of one device to the IN port of the next device. The first EtherSound device in the daisy chain is called the “Primary Master”. The Primary Master supplies the wordclock for the EtherSound network. Connect the setup PC to the unconnected IN port of the Primary Master. Maximum Cable Length The specified limit for CAT5e cables is 100 meters under ideal conditions.
Step 1 Physical Setup EtherSound Topologies EtherSound networks may be configured in the following topologies. Daisy Chain Devices are simply connected in a single line. Ring The ring topology may be considered a variant of the daisy chain created by connecting the first and last devices together. Connecting devices in a ring topology makes it possible to make the system tolerant to cable faults. Tree Standard Ethernet switches can be used to create Tree topology.
Step 2 Launching AVS-Monitor Step 2 Launching AVS-Monitor EtherSound is a very flexible system supported by many manufacturers for many differing purposes. To setup and monitor EtherSound devices Yamaha recommends AVS-Monitor by AuviTran. This program can be used to setup other manufacturers’ devices at the same time as Yamaha's. AVS-Monitor may be downloaded from: http://www.auvitran.
Step 2 Launching AVS-Monitor ③ If devices do not appear as intended, recheck physical connections, and press the “Reset ES Network” button. Configuring AVS-Monitor The first time you use AVS-Monitor, you must turn AuviTran service ON and select the network adapter which is connected to your EtherSound network.
Step 2 Launching AVS-Monitor Setting device names By default AVS-Monitor identifies devices by their MAC addresses, (a 12 digit hexadecimal number). To make configuration operations easier, it is recommended to set names for each device. For each device: ① Select the device in the Tree view or List view. ② Click on the properties tab. ③ In the “Name Box”, type in a name. In this example set the following names for the three devices.
Step 3 Bidirectional Loop Settings Step 3 Bidirectional Loop Settings Audio transfer on EtherSound networks takes place in two directions; away from the Primary Master and towards the Primary Master. Data flow away from the Primary Master is referred to as “Downstream”, data flow towards the Primary Master is referred to as “Upstream”. Up to 64 channels of audio may be carried in each direction. received by all following devices.
Step 3 Bidirectional Loop Settings Bidirectional Loops A bidirectional loop is a segment of the network where data may be transferred in both upstream and downstream directions. In most cases, it is desirable for the network to be bidirectional. However there are some cases where data transfer must be mono directional. (See the side notes on the Tree Topology.) EtherSound allows the user to specify which segments of the network are bidirectional.
Step 3 Bidirectional Loop Settings The Start Loop Parameter The beginning of a bidirectional loop is typically the Primary Master device. This can be modified by setting the Start Loop parameter on at the desired device. The Start Loop Parameter ends a bidirectional loop by blocking upstream channels from travelling further upstream. The Start Loop Parameter is required for tree and star topologies. See the side notes below on Tree Topology.
Step 3 Bidirectional Loop Settings Checking current bidirectional loop settings When AVS-Monitor is launched, previously stored settings are retrieved from the devices. We must first check the current settings. Select Tree view. The current bidirectional loop settings can be determined from the icons appearing to the left of each device. If the following icon appears, the device is in mono directional mode (downstream only).
Step 3 Bidirectional Loop Settings End Loop settings For our example we need a bidirectional loop to span the entire network. The start of the loop is by default the Primary Master device. Assuming that the network was in mono directional mode, we simply need to set the End Loop parameter on at the last device, DME8o-ES. ① Select DME8o-ES in Tree view. ② To turn the End Loop settings off, right click DME8o-ES in Tree view and move the mouse to highlight “Device functions” as shown below.
Step 3 Bidirectional Loop Settings Note: The “End of BiDir Loop” and “Start of BiDir Loop” parameters may also be viewed and modified in I/O Patch tab of each device.
Step 3 Bidirectional Loop Settings Tree Topology EtherSound was designed primarily for Daisy Chain and Ring topologies. However, in some cases, physical location of devices may favor a topology having branches. Such a topology is called Tree topology. When using Tree topologies, devices below the switch are not allowed to transmit on upstream channels through the switch. Devices must be prevented from transmitting upstream by checking the Start Loop parameter of devices immediately below the switch.
Step 4 Wordclock Settings Step 4 Wordclock Settings In daisy chain EtherSound networks the device furthest upstream is the Primary Master device, and is always the wordclock master for the EtherSound network. network does not need to be specified by the user. Thus the wordclock master for the The wordclock settings for each device will depend on if the device is Primary Master or Non-Primary Master.
Step 4 Wordclock Settings Selection of Sampling Rate The dip switch “SW2” on MY16-ES64 must be set to “48K” (when using 44.1/48 kHz) or “96K” (when using 88.2/96 kHz). Note: In this example, since we are using 48 kHz, set SW2 to “48K”. The choice between 44.1 and 48 kHz or 88.2 and 96 kHz is made by changing the settings of the device hosting MY16-ES64. all MY16-EX cards connected to MY16-ES64.
Step 4 Wordclock Settings ■NAI48-ES settings Wordclock Source The wordclock source setting depends on if the device is Primary Master or Non-Primary Master. We have the following options: Primary Master W. Clock AES/EBU 1~6 Non Primary Master EtherSound 48K EtherSound 96K In this example, since NAI48-ES is receiving the 48kHz wordclock from the Primary Master, select ”EtherSound 48K” in the AVS-Monitor NAI48-ES Control tab.
Step 4 Wordclock Settings ■DME8o-ES settings Wordclock Source Since the selection of wordclock source for DME Satellite ES series devices (DME8i/8o/4io-ES) is performed automatically, there is no user wordclock source setting. DME Satellite ES series devices synchronize to an internal EtherSound wordclock module. This wordclock module automatically configures itself as wordclock master or slave depending on if the device is Primary Master or Non-Primary Master.
Step 4 Wordclock Settings Verifying wordclock settings If the network is properly synchronized, a check mark will appear in the Synchro Status box of each device on the network. For all devices: ① Select device in Tree view. ② Select Control tab. ③ Verify that a check mark appears in Synchro Status.
Step 5 Making Audio Patches Step 5 Making Audio Patches AVS-Monitor has two views for setting up patches, Net Patch view and I/O Patch view. Net Patch View In Net Patch view, you can make patches directly between SOURCES (outputs of the device to the EtherSound network) and RECEIVERS (inputs of the device from the EtherSound network). When making patches with Net Patch view, AVS-Monitor automatically assigns EtherSound channels and in some cases modifies Bidirectional Loop parameters.
Step 5 Making Audio Patches I/O Patch View In I/O Patch view, creating a patch requires two operations. First you must patch a transmitting device output to an EtherSound network channel, then patch the EtherSound network channel to a receiving device input. I/O Patch View requires more operations than Net Patch View, but allows you to specify the EtherSound network channel assigned to each patch.
Step 5 Making Audio Patches In this example, we will use I/O Patch view to make the following patches: ① Transmit 10 channels from NAI48- ES to M7CL (inputs from stage to FOH mixer) ② Transmit 2 channels from M7CL to DME8o-ES (stereo mix for FOH speakers) 23
Step 5 Making Audio Patches ① Patching 10 channels from NAI48- ES to MY16-ES64 (M7CL) First select NAI48-ES in the Tree view and select the I/O Patch tab. Since MY16-ES64 is upstream from NAI48-ES, we will send on upstream EtherSound channels. In this example we will send data from NAI48-ES’s device outputs 1~10 using upstream EtherSound channels 1~10. In the lower box, right click the intersection of the 1st row and the 1st column.
Step 5 Making Audio Patches Repeat this procedure for all 10 channels. When this is complete, I/O Patch View should appear as shown below. Now 10 channels of audio from NAI48-ES have been sent to the EtherSound network. Next select MY16-ES64（M7CL）in Tree view.
Step 5 Making Audio Patches We will now receive the upstream audio channels 1~10 transmitted by NAI48-ES on MY16-ES64 inputs 1~10. In the upper box, right click the intersections of the 1st row and 1st column to the 10th row and 10th column. Now 10 channels of audio from NAI48-ES pass through the EtherSound network and are received by MY16-ES64.
Step 5 Making Audio Patches ② Patching 2 channels from MY16-ES64 (M7CL) to DME8o-ES Since DME8o-ES is downstream from MY16-ES64 (M7CL), we will transmit on downstream channels. We will send data from MY16-ES64 (M7CL)’s outputs 1~2 using downstream Ether Sound channels 1~2. In the lower box, left click the intersection of the 1st row with the 1st column, and the 2nd row with the 2nd column.
Step 5 Making Audio Patches In the upper box, left click the intersections of the 1st row and 1st column and the 2nd row and 2nd column to receive the downstream audio channels 1~2 transmitted by MY16-ES64 (M7CL) on DME8o-ES inputs 1~2. Now 2 channels of audio from MY16-ES64 pass through the EtherSound network and are received by DME8o-ES. This completes patching for our example.
Step 5 Making Audio Patches Audio Patches When Using 96 kHz In I/O patch view, when using 88.2 or 96 kHz sampling frequency, two EtherSound channels are used to transmit one audio channel. When a column is selected, two adjacent columns will be selected automatically. Overwriting Channels An EtherSound device may transmit data onto any EtherSound channel regardless of whether the channel is in use or not. Transmitting audio data onto an EtherSound channel already in use is called overwriting.
Step 6 Remote Head Amp Control Step 6 Remote Head Amp Control Remotely controllable head amp units may be controlled using EtherSound’s Data Tunneling capabilities. Data Tunnel EtherSound D-Sub 9pin HA Control Data In our example system, we will configure a data tunnel between MY16-ES64 (M7CL) (controlling device), and NAI48-ES (receiving device).
Step 6 Remote Head Amp Control ■Setting up MY16-ES64 (M7CL) (controlling device) Select MY16-ES64 (M7CL) in Tree view or List view and select the control tab. Serial Port Mode The Serial Port Mode will depend on the host device of the MY16-ES64. This example uses M7CL. Since M7CL uses its REMOTE port to output control data, select Mode 3. See the next side notes.
Step 6 Remote Head Amp Control MY card Serial Port Mode For a host device that outputs control data from via its REMOTE port select Mode 3. For a host device capable of outputting control data via its internal slot, select Mode 2. The Serial Port Mode setting for various Yamaha digital mixers is given in the table below.
Step 6 Remote Head Amp Control Remote Head Amp Control Setup for LS9-32 Press the [RACK5-8] key to access the EXTERNAL HA screen. In the COMM PORT box, select “SLOT1” as the communication port for the MY16-ES64 card. (When using LS9-16, select “SLOT”.) Specify the input ports for an external HA. Move the cursor to the EXTERNAL HA PORT SELECT popup button for each head amp unit, and press the ENTER key.
Step 6 Remote Head Amp Control Serial Communication Mode Set the Serial Communication Mode to Unicast. Since the head amps requiring control are connected to NAI48-ES, in the list box, select NAI48-ES. Serial Port Configuration Set the Baud Rate to 38400.
Step 6 Remote Head Amp Control ■Setting up NAI48-ES (receiving device) Select NAI48-ES in Tree view or List view and select the Control tab. Serial Communication Mode Set the Serial Communication Mode to Unicast and select MY16-ES64 as the destination. Note: Multicast is not used with Yamaha products. When AVS-Monitor is used to control the Head Amp directly, select “Slave”.
Step 6 Remote Head Amp Control Serial Port Configuration Set the Baud Rate to 38400.
Step 6 Remote Head Amp Control Head Amp Control with AVY16-ES / AVY16-ES100 When controlling head amps with AVY16-ES, AVY16-ES must be the Primary Master. Select the destination device and press Start button as shown in the diagram below, In the control tab of the receiving device, select "Slave" as the Serial Communication Mode. When using AVY16-ES, there can be only one receiving device on the entire system.
Step 6 Remote Head Amp Control Head Amp Control with Multiple Receiving Devices The previous section explains the procedure for setting up a data tunnel between one controlling device and one receiving device. If there is more than one device that needs to receive HA control data, create a chain of data tunnels using the same procedure for a single tunnel for each link of the chain. Be sure to create a data tunnel from the final device back to the controller.
Step 6 Remote Head Amp Control Head Amp Control with Multiple NAI48-ES When controlling multiple NAI48-ES units, ensure that each AD8HR on the system has a unique ID by using the ID Start From parameter. AD8HRs connected to the same NAI48-ES will be assigned consecutive IDs. The “ID Start From” parameter determines the ID of the first AD8HR unit. Up to eight AD8HR units may be used on the entire network.
Step 6 Remote Head Amp Control Head Amp Control with SB168-ES When remotely controlling SB168-ES units, the 16 internal head amps of SB168-ES will appear as two AD8HR units in the console’s display.
Step 6 Remote Head Amp Control D-Sub 9pin Cables for Head Amp Control When controlling head amps with Yamaha devices such as AD8HR, MY16-ES64, NAI48-ES, PM5D, M7CL-48/32, DM2000, DM1000 and DME series, or AuviTran’s AVY16-ES100 card, be sure to use a D-sub 9pin (female) crossover cable with pin assignment shown below.
Step 7 Making the System Redundant Step 7 Making the System Redundant Cable redundancy can be added to the system by using EtherSound’s Fault Tolerant Ring Mode. However, when using this mode, there are certain restrictions to observe. Patching Restrictions A special patching scheme which ensures patches continue to work after cable failures must be used. Specifically: End Loop parameters for all devices must be set to “ON” Audio must be transmitted on downstream channels only.
Step 7 Making the System Redundant We will now explain the procedure for making our daisy chain system redundant. Wordclock Source settings Since all devices must be configured as non-primary master devices, we must change the wordclock settings for MY16-ES64. Referring to the section on wordclock settings for MY16-ES64, the clock setting of the host device (M7CL) for non-Primary Master devices must be set to the slot containing MY16-ES64.
Step 7 Making the System Redundant End Loop settings End Loop settings must be turned on, for all devices. End Loop is already set for DME8o-ES. Repeat the following procedure for MY16-ES64 (M7CL) and NAI48-ES. ① In Tree view, right click the device name and move the mouse to highlight “Device functions” as “End of BiDir Loop”. ② Release the mouse to toggle the parameter’s state. A check mark to the left of “End of BiDir Loop” appears to indicate that the parameter is active.
Step 7 Making the System Redundant Audio Patches For patches to continue to work after cable failures, we must make sure that transmission takes place only on downstream channels and reception takes place only on upstream channels. In this example, we will make the following repatches.
Step 7 Making the System Redundant ① Repatching 10 channels from NAI48- ES to MY16-ES64 (M7CL) Select NAI48-ES in Tree view: We must reconfigure NAI48-ES so that it transmits on downstream channels. Press the “Clear All” button to clear current patches. Since downstream EtherSound channels 1 and 2, are already in use by MY16-ES64 (M7CL), configure NAI48-ES to transmit on downstream EtherSound channels 3~12 to avoid conflicts. Use the same procedure given in Step 5.
Step 7 Making the System Redundant Next select MY16-ES64 (M7CL) in Tree view. Reconfigure it to receive 10 audio channels from NAI48-ES on upstream EtherSound channels 3 ~ 12.
Step 7 Making the System Redundant ② Repatching 2 channels from M7CL to DME8o-ES Select DME8o-ES in Tree view. In Step 5 we configured DME8o-ES to receive on downstream EtherSound channels 1 and 2. However, since all channels are looped back, we can receive the same data on upstream EtherSound channels 1 and 2. Right click on the previous patches to change the patches to upstream channels.
Step 7 Making the System Redundant Selection of Preferred Primary Master and Ring Active setting In a daisy chain EtherSound network, the device supplying wordclock is always the Primary Master device (the first device in the chain). In Fault Tolerant Ring Mode, since there is no “first” device, a wordclock master must be specified by the user. This device is called the “Preferred Primary Master.” In the Tree view, right click on the device you wish to select as the preferred primary master.
Step 7 Making the System Redundant Wordclock for Ring Topologies For ring topologies, the device for which the user sets Ring Active becomes the Preferred Primary Master and assumes the role of wordclock master. the network reverts to a daisy chain network. In the event of a cable failure, In this case, the wordclock master device automatically switches from the Preferred Primary Master to Primary Master, the device at the start of the daisy chain.
Step 8 Saving your Configuration Step 8 Saving your Configuration All EtherSound device settings with the exception of device names can be committed to non-volatile memory, eliminating the need for reconfiguration each time the network is powered on. For each device on the network, ① Select the device in Tree view. ② From the File menu, select “Write to Non Volatile Memory” or use the short cut icon on the tool bar. ③ The following message will appear when the write operation is complete.
Step 8 Saving your Configuration Auto Configure Function of M7CL-48ES and SB168-ES System When using M7CL-48ES and SB168-ES in certain configurations (*), the Auto Configure function may be used to automatically setup audio patches and head amp control. Auto Configure may be used with systems having one M7CL-48ES and from 1 to 3 SB168-ES units. (For details, refer to the M7CL-48ES user’s manual.
Step 8 Saving your Configuration AVS-Monitor / M7CL-48ES Control Page AVS-Monitor / SB168-ES Control Page 53
Step 8 Saving your Configuration Quick Setup Function of SB168-ES and MY16-ES64 System When using SB168-ES in certain configurations, the Quick Setup function may be used to automatically setup audio patches and head amp control. Quick Setup may be used with systems having one MY16-ES64 card and from 1 to 4 SB168-ES units. However after setting the patches by using “Quick Setup”, it is strongly recommended that all the patches are not changed. (For details, refer to the SB168-ES user’s manual.
