Rane NM 84 User Manual

OPERATORS MANUAL NM 84

NETWORK PREAMPLIFIER

Quick Start

Why is it that the hardest thing about writing the Quick Start is the opening line? What I want to say is, First, design the
network. Only thats hard to say with a straight face  but if you are going to jump right into this thing without reading all of
our hard work, then thats where you begin. By designing a network. Okay, that works...lets move on.

A dedicated network for CobraNet audio is recommended, but not required when using switched networks. The NM 84s
CobraNet technology utilizes standard 100Base-T Ethernet hardware. For CobraNet and network design assistance and a list of
other CobraNet licensed and tested devices, visit

www.rane.com/ethernet.htm

Rear Panel:
OUTPUTS
OUTPUTS

CobraNet Bundle from 1 through 999, plus off/none. Connect the network cable to the
guess to use the
closures to the
same network. Connect the locking 5-pin DIN from the enclosed RS 3 power supply to the
power supply does indeed connect earth ground  the 3rd pin of the AC line cord  to the NM 84 chassis metal. Depressing the
recessed
youre completely done setting up the NM 84.

IN 1

NM 84 can be transmitted on up to 4 different CobraNet Bundles (
channels when transmitting 20-bit audio. CobraNet designates each of the 8 Audio Channels
respectively.

transmitted pair of the four Bundles. The four Bundles to transmit to are independently assignable to one of the 999 Bundles
using the four
CobraNet to transport all 8 Audio Channels. Use the
24-bit transmission.

ally, the NM 84s MRP status can be transmitted over the network for other NM devices to listen to. Set the
Transmit) and

and receive RS-232 channels.

Set the IP address to
IP address. Disco allows you to plug into a CobraNet network with a standard Ethernet computer card (NIC) and discover all of
the CobraNet devices on the network. Disco has the ability to dynamically assign IP addresses as well as update CobraNet
firmware on the discovered CobraNet devices. Check for Disco availability from Peak Audio at
as well as many music retailers which carry The Bee Gees, Donna Summer and the like.

Important Big Picture Concepts

order for design work and may also avoid initial confusion.

FP LOCK

Front Panel:

through

The next four pages set up Monitor Outs;

The two Network Transmit pages (

The

Mem

The

Serial

The

Config

Do yourself a favor and go through the

Connect up to 8 mic or line-level analog audio signals to the
spew an analog, line-level version of the corresponding 8
can independently receive any of the 8 Local Mic Input audio channels or any single Audio Channel from any

RS-232

Memory Recall Port (MRP)

(Front Panel Lock) button at this point disallows further front panel setup, so only press this button in once

There are 17 LCD edit pages allowing access to all NM 84 parameters. The first 8 screens set up Mic Inputs;

IN 8

, respectively. Use the

Bndl

fields;

(Memory) page allows 16 unique NM 84 setups to be

MRP Rx

page sets the RS-232 serial ports

page displays the current/editable IP Address and the editable Name of the NM 84 device (8 characters max).

.

jack to transport RS-232 data over the network to other NM RS-232 device ports? Connect contact

Copy

NetTx A/B

Bndl A, Bndl B, Bndl C

(MRP Receive) fields for any or none of the 16 available MRP channels.

0.0.0.0

(the default) to enable Peak Audios CobraNet Discovery Utility (Disco) to dynamically assign the

on page Manual-8. Reviewing the Applications Examples provides insight into a logical

www.peakaudio.com/cobranet

MIC INPUTS

to recall Memories on this device or any other NM device(s) connected on the

field to copy and paste between the various pages.

Monitor 1

Optimizing Mic Preamplifier Performance

through

and

NetTx C/D

and

Bndl D

Splt

parameter to split the 8 Audio Channels across Bundles when using

Baud

rate along with the

Monitor 4

Bndl

). Each of the 4 Bundles contains all 8 Mic Input audio

) allow selection of either

. When using 24-bit audio, two Bundles are required by

Store

. Also see Ranes ethernet link collection:

MIC INPUT

, respectively. The 8 Mic Input audio channels on the

d and

Recall

232 Tx

and

XLR jacks. The 8

 audio. Each of the four

100Base-T

ed in the 16 Memory locations. Addition-

232 Rx

on page Manual-7, and at least read

RJ-45 jack. I bet you could

POWER

AudCh 1

20-

connector. The RS 3

through

or

24-Bit Formats

fields which set the transmit to

www.peakaudio.com/cobranet

DIRECT
MONITOR

AudCh 8

for each

MRP Tx

,

(MRP

WEAR PARTS:

CobraNet is a trademark of Peak Audio, Inc.

This product contains no wear parts.

Manual-1

Front Panel Description

a Mic Input Meters

meters is the Mute condition when only the Limit indicator  and no others  is illuminated.

b Edit buttons

c LCD Display

d DATA wheel

buttons. Turn the DATA wheel clockwise to increase the parameter, turn it counterclockwise to decrease the parameter.

e Page buttons

pressed and held and MAX >> is pressed, the selected parameter jumps to its highest or to a larger value (see g).

f Cursor buttons

fields on each page. These buttons select each adjustable parameter along the bottom row by moving the underline cursor left
< or right >. When any parameter is selected, the DATA wheel adjusts that parameter. When the EXE button is pressed and
held and MIN > is pressed, the selected parameter jumps to its lowest or to a smaller value (see g).

g EXE (Execute) button

Load

# commands are underlined executes that function. Holding down EXE while pressing MAX >> alters the selected
parameter to its highest or higher nominal value. Holding down EXE while pressing MIN > alters the selected parameter to
its lowest or lower value or

should be self-explanatory. They are meters with an averaging logarithmic filter. The only quirk to these

are provide a quick and convenient way to get to the Edit page for the individual Mic Inputs.

which displays Edit Pages.

. Allows adjustment of the underlined parameter after it is selected with the Page (see e) and Cursor (see f)

. The Previous Page << and Next Page >> buttons scroll through all Edit Pages. When the EXE button is

. When pressed, the Previous < and Next > Cursor buttons move the cursor through each of the adjustable

. Several commands are implemented with this button. Pressing EXE when the

Off.

Copy, Paste

and

Pin 1 and Chassis Grounding

All XLR pin 1s on the NM 84 connect directly to the chassis metal via the XLR jack case itself. (Thank Neutrik for provid-
ing both a female and a male XLR jack which provide manufacturers with this function.) While viewing the XLR jacks, the
lower right screw next to each jack provides the chassis connection. Keeping these screws tight ensures optimal shielding and
electromagnetic interference performance.

Manual-2

Rear Panel Description

a Chassis ground screw

the AC line cord to the NM 84 chassis metal through the RS 3 power supply. This chassis screw is supplied should you need
a point in the rack to earth ground other devices or the metal rack rails. The earth connection is critical and in most installa-
tions, required by law. Please refer to the RaneNote, Sound System Interconnection (available at
included with this manual) for further information on system grounding.

b Power input connector

replacement or a substitute power supply. Using any other type of supply may damage the unit, void the warranty and cause
disco mirror balls everywhere to tragically spin in the opposite direction. After inserting the power connector into the NM 84,
be sure to tighten the outer locking ring to ensure that the power cable cannot be inadvertently pulled out.

c 100Base-T jack

cable or, more often, to a standard 100Base-T repeater hub, switch or media converter in the network.

dÿ

COND indicator

CobraNet device on the network that generates the master clock used to synchronize all other CobraNet devices on the
network. Only one device on the network will have the COND indicator on. If the Conductor is unplugged, removed from the
network or fails, CobraNet automatically assigns a new Conductor on the network. It is rarely important to know which
device is the Conductor.

e LINK indicator

intended for the NM 84. It tells you that the network is actually transporting data. If this indicator is off, no data is present.

f FAULT indicator

also has faults  but then again, doesnt everybody?

g RS-232 port

send RS-232 serial data to devices such as the RaneWare RW 232 line of audio products. This port
control of the NM 84. Be sure the NM 84 is configured properly (i.e., baud rate, Rx and TX channel) for your serial applica-
tion using the

provides a way to transport RS-232 data over the network to subsequent NM device(s). For example, you can

Serial

. A #6-32 screw is supplied for chassis grounding purposes. The NM 84 does connect the 3rd pin of

www.rane.com)

. Use only an RS 3 power supply from Rane, included with this unit. Consult the factory for a

connects the NM 84 with a standard RJ-45 connector to either another CobraNet device using a crossover

illuminates yellow when this unit is the Conductor of the CobraNet network. The Conductor is the one

lights green when any packet is present on the network. This means

lights red when, you guessed it, a fault occurs. Here in Seattle, there are faults everywhere. California

page.

any packet

, including packets not

cannot

be used for serial

and

h Memory Recall Port (MRP)

switch closures between two pins. All 16 Memories can be recalled using Binary Mode (see page Manual-14). Switch
closures on one NM 84 can be transmitted over the network to other NM devices tuned in to the same MRP Channel.

i FP Lock button

pages. A sharp instrument such as a small screw driver or pen tip must be used to depress the FP Lock button.

j Mic Inputs

right XLR mounting screw (when viewed from the rear of the unit). Keep these tight for best EMI protection.

k Monitor Out jacks

Channel within any Bundle.

l Direct Out jacks

converter. Each Direct Out signal is
Cut filter (

. When pressed in, all front panel controls are locked out. The user is able to view, but not edit, all Edit

accept balanced mic or line-level analog audio signals. Shields (pin 1) connect to the chassis through the lower-

provide a means for monitoring Local Mic Input audio channels or for monitoring any CobraNet Audio

emit a balanced analog line-level version of each Mic Input and are fed from a point just before the A/D

Fltr

) and Limiter (

allows any remote switch to recall the first eight NM 84 Memories. These recall using simple

post

the following: Mic/Line Mode; Mute; Trim (

Lim

). Phantom power (+48 VDC) is, of course, not present on the Direct Outputs.

Trm

) control, Gain relays, Low/High

Manual-3

NM 84 LCD Edit Pages

Each Edit page name appears in the upper left corner of
the LCD display. Seventeen (17) pages are found:
 8 pages for Inputs, named

each of the Mic Inputs)

 4 pages for Monitor Outs, named

Monitor 4

 2 pages for Network Transmit, (

C/D

over the network and to select which of four CobraNet

Bundle(s) to transmit onto.
There is one Edit page each for the following:


Mem

Memory Recall Port Transmit (

(

MRP Rx



Serial

(

232 Tx



Config

The top row of text on each Edit page contains the
parameter names. Their current settings appear below the
name. To edit a parameters setting, place the underline cursor
under the value that appears below the parameter name. Use
the lower Previous (<) and Next (>) cursor buttons to move
the cursor. Edit the parameter value by rotating the Data
Wheel. Clockwise rotation increases the value, counterclock-
wise rotation decreases the value. To quickly maximize or
minimize a parameters value, hold down the EXE button and
press Next Page (>>) or Next Cursor (>) buttons, respectively.

Copy, Paste

pages. Move the cursor under the
DATA wheel to select the desired command, then press the
EXE button to execute the command.

Use
clipboard. Navigate to the Edit page where you want to paste
these settings and execute a
button. [For convenience, the
changed to

Load X

corresponding Edit page to be pasted into the current Edit
page. X can be changed to any of the 16 Memories, 1
through 16, using the DATA wheel;
etc. This is an easy way to copy a single Edit pages contents
from a stored Memory into the current page.

(one page for each Monitor Out)

) for selecting 20- or 24-bit Format audio transmission

page for Memory Storing, Recalling and setting the

) channels.

page for setting the RS-232 Baud rate and Transmit

) and Receive (

page for setting the IP Address and Device Name.

and

Load X

Copy

to place the current Edit page contents in a

Paste

after executing the

allows the contents stored in Memory Xs

IN 1

through

NetTx A/B

MRP Tx

232 Rx

) channels.

fields are found in several Edit

Copy

Paste

by pressing the EXE

Copy

IN 8

(one page for

Monitor 1

field is automatically

Copy

Load 1, Load 2, Load 3,

through

and

) and MRP Receive

field, rotate the

command.]

NetTx

Input Edit Pages  IN 1 through IN 8

Each of the eight Input Edit pages sets up one of the Mic
Inputs. Two modes are possible for each Input, Mic or Line
(see LCD screen shot below).

The only differences between Mic mode and Line mode
are that Mic offers selection of +48 volts for phantom power
and the Gain selection differs. Mic mode Gain offers +15, 30,
45 and 60 dB settings while Line mode offers +10 dB and -5
dB gain settings. All other settings and ranges are identical.

Input Parameter Range & Comments

Mode Mic

Mute Off

Trm

(Trim)

Gain

(Mic mode)

Gain

(Line mode)

+48V

(Mic mode only)

Fltr

(Filter)

Lim

(Limiter Threshold)

In 1: Mode Mute Trm Gain +48v Fltr Lim
Copy Mic On +0 15dB Off Off +18

or

Line.

or

On.

+16

to

-20dB

in 1 dB steps.

15, 30, 45

-5

or

Off

up and down for quiet operation and
is automatically turned

Line

Off, LCut
HCut
L/H

(both Low and High Cut)

+18

or

60dB.

+10dB.

or On. Phantom power ramps

Off

when

mode is selected.

(160 Hz Low Cut),

(7 kHz High Cut),

to

-30

in 1 dB steps.

Mic Mode

In 1: Mode Mute Trm Gain Fltr Lim
Copy Line On +0 -5dB Off +18

Line Mode

Manual-4

Monitor Out Edit Pages  Monitor 1 through Monitor 4

The four Monitor Out Edit pages set up the four Monitor
Outputs. Two modes are possible for each Monitor Out:
for monitoring any one of the Local 8 Mic Inputs
or none (
CobraNet Audio Channels (
screen below.) When monitoring an Audio Channel, one must
first select which Bundle (
Audio Channels within each Bundle can be monitored using
the

Bndl

combinations can help avoid carpal tunnel syndrome from
repeatedly rotating the DATA wheel. (Youre welcome. Arent
you glad you read the manual?)

Monitor Parameter Range

Source Local

Bndl

AudCh

Mic

Off

), or

Network

AudCh

in

in

field parameter.

field is where use of the MAX and MIN dual-button

(CobraNet Bundle)

Network

Network

in

Monitor 1: Source Bndl AudCh
Copy Network Off 1

mode

(Audio Channel) integers 1 through 8 from selected

mode Bundle.

Local

mode

for monitoring any one of the

AudCh

Bndl

Off

Remember, each Bundle contains
eight Audio Channels.

Off

Inputs.

) or none (

) to monitor. Any one of the 8

With 999 possible Bundles, the

or

Network

, integers 1 through

, integers 1 through 8 from Mic

Off

Local

). (See the

999

.

Network Mode

Monitor 1: Source Mic
Copy Local Off

Local Mode

Network Transmit (NetTx) Edit pages

The NM 84s eight Mic Input audio channels can be
transmitted on up to four different CobraNet Bundles. The two
Network Transmit Edit pages allow the transmission Format
to be set to 20- or 24-bit for the audio transmitted onto the
CobraNet network. Additionally, the four independent
Bundles to transmit to are setup using the four
parameters, where

Now youre probably wondering:

versions of the same eight audio channels over the network,
aye?

The long answer is on page Manual-9. The short answer
is, when using unicast (point-to-point) networks, often certain
channels must be transmitted to more than one location or
CobraNet node. Thus the NM 84 provides four Bundles for
transmission. CobraNet permits transmission of up to 4
Bundles maximum per CobraNet node.

Two

Format

24-bit audio mode (see the screen below). In 20-bit mode, the
internal CobraNet DSP truncates the 24-bit stream to a 20-bit
stream. Using 20-bit audio over CobraNet permits broadcast
of all 8 Mic Input channels over a single, selectable CobraNet
Bundle. While this makes it harder to impress your friends by
touting your 24-bit audio network, it does make larger
networks easier to manage since you do not need to split the
eight NM 84 Inputs across multiple Bundles as is required for
24-bit mode.

To reap the extra performance of 20% more bits or to
avoid truncation of audio, select 24-bit audio which requires
selecting two different CobraNet Bundles. Once two of the
999 Bundles are selected, the
choose how to divide the 8 available Audio Channels among
the two Bundles. Choices appear as follows:

4, 3/5, 2/6, 1/7

Audio Channels (1 through 7) are transmitted on the first of
the two Bundles you select and the remaining one Audio
Channel (channel 8) is transmitted on the second selected
Bundle.

X

is

A, B, C

modes are possible: 20-bit audio mode and

. For example,

or D.

why transmit four

Splt

parameter field lets you

7/1

means that the first 7

Bndl X

7/1, 6/2, 5/3, 4/

Parameter Range

Format 20 Bit

Bndl A

(1st of 4

possible Bundles)

Splt

(Audio Channel

split) 24-bit mode only (

Bndl B

(2nd of 4
Bundles  the 3rd and
4th Bundles are labeled
C and D respectively.)

NetTx A/B: Format Bndl A Bndl B
20 Bit 1 Off

or

24 Bit

.

Off

, integers 1 through

7/1, 6/2, 5/3, 4/4, 3/5, 2/6

See above

Off

, integers 1 through

).

999.

999.

or

20-Bit Format Mode

NetTx A/B: Format Bndl A Splt Bndl B
24 Bit 1 7/1 Off

24-Bit Format Mode

Manual-5

1/7

.

Memory Edit page

The Memory Edit page stores and recalls the 16 NM 84
Memories. Memory Recall Port Transmit (
Receive (

zero contains the current settings which are always displayed
on the LCD screen. Therefore, all changes made from the
front panel alter the current settings  Memory zero. Once the
desired settings are reached using the Edit pages, Memory
zero (the current settings) can be stored into one of the 16
Memory locations. Additionally, recalling one of the 16 stored
Memories places that Memorys contents into Memory zero
for display, viewing, and further editing if needed.

through 16, is displayed on the top left of the Mem LCD page.

An asterisk (*) appears to the right of this Memory number
when the current settings no longer matched the displayed
Memorys contents. This indicates a change to the NM 84
settings has been made since the last Memory was recalled.

use the DATA wheel to display the Memory number to store
the currents settings into, then press the EXE button.

wheel to display the Memory number to recall from, then
press the EXE button which overwrites the current settings.

transport channels which are asynchronously transported over
the CobraNet network to other NM devices which are set to
listen to the corresponding MRP channels. The
(MRP Transmit) parameter can be set to one of the 16 MRP
channels or
MRP transmission. The numeric settings  integers 1 through
16  tell the NM 84 to Transmit its current MRP contact
closure status over the network to other NM devices that are
set to receive the corresponding MRP channel. This allows
other Rane NM devices to use remotely located NM devices
MRP switch states to change Memories.

Local, Off

the NM 84 to scan its own rear panel Memory Recall Port for
switch closures.
through 16 sets the desired MRP channel to receive from or
listen to.

 All Mic In settings:
 All Monitor Out settings:
 All Serial, RS-232, settings:

Config edit pages are
disallowing Memories to alter the Network Transmit settings,
for example, is to keep the familiarity of a radio broadcasting
paradigm relevant to CobraNet network Bundles. Thus,
sticking to always transmitting audio over the same Bundles
while using Memories to re-route to the desired channels,
helps make things more easily managed. In other words,
always transmit on the same Bundles (i.e., fixed radio station
transmission) but tune in to the desired Bundle and Audio
Channel to receive (Monitor) the audio needed.

MRP Rx

Conceptually, the NM 84 contains 17 Memories; Memory

The number of the most recently recalled Memory, 1

To store the current settings, move the cursor under

To recall, move the cursor under

The NM 84 provides up to 16 MRP (Memory) data

The

MRP Rx

or integers 1 through 16. The

The following parameters are stored in each Memory:

Therefore, parameters found in the NetTx, Mem and

) are also set in this page.

Off

. The

Off

setting  you guessed it  turns off

(MRP Receive) parameter can be set to

Off

turns off the MRP completely and

Mode, Mute, Trm, Gain, 48V, Flt, Lim

Source, Bndl/Mic,

Baud, 232 Rx, 232 Tx

not

stored in Memories. The intent of

MRP Tx

Recall

, use the DATA

Local

) and MRP

MRP Tx

setting tells

AudCh

Store

1

Parameter Range

Store
Recall
MRP Tx
MRP Rx

(MRP transmit)

(MRP Receive)

Mem 1* Store Recall MRP Tx MRP Rx
1 1 Off Off

Integers 1 through
Integers 1 through

Off

, integers 1 through

Local, Off

, integers 1 through

16
16

16

Memory Edit Page

Serial Edit page

The Serial Edit page configures the RS-232 port.

Baud

parameter must be set to the desired baud rate for the

device used with the RS-232 port.

38,400 baud are found. See the complete list below.

The NM 84 provides up to 255 serial data channels which
are asynchronously transported over the CobraNet network to
other NM devices set to receive and transmit over correspond-

,

ing serial channels. The
these respective transmit and receive serial channels for
transport of the RS-232 ports data. Be certain to use one
channel for transmit such as 1, and a different channel to
receive, such as 2. We know that you know that 1 is different
than 2, but this is of course necessary, since RS-232 requires a
different transmit and receive pair and therefore independent
channels.

Another important thing to remember as far as the 232
ports physical connections go,

required connector sex, male or female, when transporting
232 around. All NM devices contain a female RS-232 (DB-9)
connection on the rear.

For example, when transporting Ranes RW 232 protocol
from a computer to an NM 84, over the network to another
NM device, the cabling should be as follows:
The end of the cable at the computer connection will be
female  since the DB-9 on a computers COM ports are male.
The other end of the cable will be male so one can connect it
at the initial NM 84 device. At the second NM device, the rear
panel DB-9 is female, thus requiring a male on the end of the
second cable. The DB-9 Input on RW 232 devices is a female.
Therefore, a male-to-male gender bender is required on the
RW 232 Input side of the second cable to permit using a
standard serial cable.

Parameter Range

Baud 600, 1200, 2400, 4800, 9600,

232 Rx
232 Tx

(232 Receive)

(MRP transmit)

Serial: Baud 232 Tx 232 Rx
38400 Off Off

232 Tx

19200, 38400
Off
Off

Typical choices up to

and

232 Rx

be sure you review the

, integers 1 through
, integers 1 through

parameters set

255
255

Serial Edit Page

16

The

Manual-6

Configuration Edit page

The

Config

Set the
Utility to dynamically assign the IP address.

address displayed in the NM 84 screen will not be updated to
reflect the IP Address assigned by Disco (see the Quick Start
on page Manual-1).

the four IP Address numeric fields until the IP address
matches the numbers assigned by your network administra-
torif you have one. Perhaps Audio Network Administra-
tor is a job title of the future? If you have no administrator,
you may use an address out of the internationally accepted
private network block of addresses, which is 192.168.nnn.nnn
where nnn represents any number between 0 and 255. A good
choice might be 192.168.100.100 just because its easy to
remember if you ever need to know it again. Subsequent NM
devices might use 192.168.100.101, 192.168.100, 102, 103,
104 etc.

the computer must be set such that the IP Addresses it can
talk to are within range of the IP addresses of the NM
devices.

worked Audio System Control for more details.

84 device to keep your sanity when multiple units are used on
the same network. This is particularly useful when using
Disco. There are 96 different ASCII characters available for
each of the 8 characters available in the Name field. So, feel
free to use lower and/or upper case letters, numbers, punctua-
tion marks, et cetera, in the device name.

Parameter Range

IP Address 0.0.0.0
Name

IP Address

To assign an IP Address using the NM 84 front panel, edit

Important : In systems using a computer with NM devices,

The

Config: IP address Name
0 .0 .0 .0 NM 84

page sets the NM 84s IP address and Name.

to

0.0.0.0

See the RaneNote, Emerging Standards for Net-

Name

parameter provides a place to name each NM

to enable CobraNets Discovery

that the IP

through
8 characters max; 96 possible
characters per field thus permitting

4.97 x 10
is more than the number of particles
in the universe.

255.255.255.255

86

names, which Im told,

Configuration Edit Page

Optimizing Mic Preamplifier
Performance

There are seven stages of signal processing for each of the
8 Mic Inputs, plus Metering. For best results, it is very
important to set each stage correctly as follows:

1) Input Pad

Controlled by the

Mic Mode (0 dB) or

Never change this parameter during a live performance.

2) +48 volt Phantom Power

Controlled by the

On or Off.

Defeated in

Never change this parameter during a live performance.

3) Mic Preamplifier with coarse Gain

Controlled by the

+15, +30, +45, +60 dB

-5, +10 dB

The Gain setting is derived by subtracting the Pad value
from the mic preamplifier gain.
In

Mic Mode, 15-0 = 15, 30-0 = 30, 45-0 =

In

Line Mode

Do not adjust the Gain parameter during a live perfor-
mance.

If changes must be made, reduce the setting of the
Trim parameter by at least 15 dB (see #6 below), make the
change and then increase the Trim as required.

4) Hi and Low Cut Filters

Controlled by the

Off

: no filters. Full 40 Hz to 20 kHz bandwidth.

LCut

inserts a 160 Hz Low Cut filter.

HCut

inserts a 7 kHz High Cut filter.

L/H

inserts both the Low Cut and the High Cut filters.

The Filters may be changed during a live performance.

5) Limiter

Controlled by the

+18 dBu

The maximum signal level at the mic preamplifier output is
+18 dBu so this equates to a range of 0 dBFS to 48 dBFS.
The Limiter is a feedforward type that always monitors the
signal level at the mic preamplifier output. Therefore, the
Trim parameter (see #6 below) does not affect this thresh-
old setting.

performance.

to

Mode

parameter.

Line Mode (20 dB).

+48

parameter.

Line Mode.

Gain

parameter.

in

Mic Mode.

in

Line Mode.

45,

60-0 = 60.

, 15-20 = -5

Fltr

Lim

30 dBu

The Limiter may be changed during a live

and 30-20 =

parameter.

parameter.

threshold in 1 dB steps.

+10.

6) Fine adjust Trim

Controlled by the

+16

to

20 dB

Digitally controlled VCA with clickless integrated steps.

Use the Trim for all signal level adjustments during a live
performance.

Trm

parameter.

in 1 dB steps.

Manual-7

7) Signal Level Meter

The Mic Input Meters monitor the signal at the
the voltage controlled amplifier (VCA). Therefore, the
Meter indicates the signal level after the Trim and any gain
reduction due to Limiter operation. The average RMS
signal level is indicated in dBu. The signal level at the
Direct Outputs is 6 dB above that indicated by the Meter
(i.e. +18 dBu = +24 dBu at the Direct Output. The Meter
level is also proportional to the signal level to be processed
by the A/D converter for transport on CobraNet. +18 dBu is
equivalent to 0 dBFS (0 dBu is equivalent to 18 dBFS
etc.). It is very useful to know the signal level at the mic
preamplifier output when setting the coarse Gain parameter.
To do this, set the Trim parameter to 0 and the Limiter
threshold parameter to

Setting up the Mic Preamplifier

No source should be connected at this time!

Make sure no signal will reach an amplifier!

1. Select the correct

2. Set

+48

phantom power as required (

3. Estimate

4. Set the
clipping under worst case conditions (the clip point for the
preamplifier is +18 dBu).

5. Turn

6. Set Trim (

7. Set Filter (

8.

Make sure no signal will reach an amplifier!

9. Connect your source.

10. Set the Limiter (

11. If you can light the red

12. Remember, if you overload the Mic Input stage, the Trim
(

13. After the Input gain is set to prevent clipping under worst
case conditions, reduce the Trim (
tive level and set the Limiter (

14. Repeat for each source in the system.

15. You are now ready for a sound check.

16. Remember, use the Trim (
adjustments during a live performance,
parameter. In a system with marginal gain-margin-stability,
adding an additional 15 dB of gain could result in nasty,
screaming oscillations. If you find that you do not have
enough gain range with the Trim level during a live
performance and must increase the Gain setting, be sure to
reduce the Trim by at least 12 dB before stepping up the
input Gain. You may then adjust the Trim as required.

The list looks long, but the idea is simple.

1) Make sure the Input cannot overload.

2) Use the

build custom system control interfaces. While giving the end
users access to basic trim controls and memory recall func-
tions, they may be denied access to parameters that would
defeat your hard work.

the maximum signal level your source can produce.

Gain

parameter to a level that will not allow

Mute Off

Trm

) to

Fltr

) as required.

Trm

) and Limiter (

Trm

and

The use of ActiveX controls allows the system designer to

+18

.

Mode (Mic

0 dB.

Lim

) to

Lim

Lim

parameters to set and maintain levels.

or

Line

).

Mic Mode

+15

(3 dB below clipping).

Limit

indicator,

) settings are useless!

Lim

Trm

) parameter for all level

reduce the

Trm

) level to a conserva-

) threshold as required.

not

the

output

only).

Gain

Gain

of

Extra credit reading:

ment and control of SPL, the NM 84s Limiters may be used
for AGC. To provide AGC, set the Limiter (
about 10 to 15 dB below your required operating level and
then use the Trim (

In addition to protection of equip-

Lim

Trm

) for make-up gain.

) to a level

Important Big Picture Concepts

There are several imperative concepts which must be
known to effectively understand the NM 84 and its CobraNet
technology. A few of these are discussed below. Reading the
rest of this manual and a thorough visit to

www.peakaudio.com/cobranet

NM 84 Memory scheme.

Memories, including the NM 84, follow a common scheme:
The LCD display (or software screen for PC-controlled
devices) shows the current settings of the device. Sixteen
Memory locations (or some number, depending on the
product) exist from which the current device settings are
stored and recalled. The current settings are considered
Memory zero; some people like to think of Memory zero as
working Memory. All device editing is performed using
Memory zero  even though we never display the number
zero. There are, therefore, actually 17 Memories  1 through
16 and zero.

Any changes made to the device are
Memory zero. Should there be a power interruption, the
contents of Memory zero are recalled upon power up from
their previous, pre-power-down settings. Thus, work in
progress is never lost and the device comes up with the same
settings with which it went down.

.

Once you are happy with the current settings in Memory
zero, they can be stored to one of the 16 Memories. To display
or edit a previously stored Memory, recall it into Memory
Zero. See the Memory Edit section on page Manual-6 for
more details.

Control data transmission

of audio Bundles available in CobraNet, additional network
data space is allocated in CobraNet for control data transmis-
sion. This non-Bundle space, if you will, is where the NM 84
transmits the Serial (RS-232) data and Memory data for the
MRP. This control data is transported asynchronously over
CobraNet (not isochronously like the audio data), although
with a theoretical maximum of 9 Mbits/sec there is little need
to worry about control data arrival times. This is only 468
times faster than 19200 serial control data!

CobraNet Bundles.

the over 65,000 Bundles available (using Peak Audios
CobraCad software, all 65,000 Bundles are accessible).
CobraNet divides the tens of thousands of Bundles into three
different Designations or types for the transport of audio data
over the network. The table on the next page explains the
differences between the three types of CobraNet Bundles.
There are advantages and disadvantages in using each. The
Network Examples section after the table discusses applica-
tions for the various Designations.

are highly recommended.

All Rane products that contain

immediately

. In addition to the thousands

The NM 84 can access up to 999 of

stored in

Manual-8

rebmuneldnuBnoitangiseDnoitpircseDsegatnavdAsegatnavdasiD

)ffO(0

)00$:xeh(

552hguorht1

1000$:xeh(

)FF00$hguorht

hguorht652

972,56

0010$:xeh(

)FFEF$hguorht

lluNnoissimsnarT

eldnuBtsacitluMllA.tsacitluM

eldnuBtsacinU-tniop,.e.i(tsacinU

gnivasdnaoiduagnitumroftcefreP

desunU.delbasid

.htdiwdnabkrowten

.ffO,.e.i,lennahc

forebmundetimilnunaswollA

secivedteNarboC

&timsnartnac

hguorhtatadeviecer

.demusnoc

.seldnuBtsacitluM

].atadtsacitluMllaeviecer

onhtiwnoissimsnartrepsreviecer

htdiwdnabkrowtenlanoitidda

dnateNarboClla,krowtenteNarboCanO[

,sbuhretaepersahcus,secivedteNarboC-non

.krowtenehtno

rebmunmumixamdexifonsierehT
atad)tniop-ot
.noissimsnart

htiW[

PMNSsuoiresemos

seldnuBtsacinU,krow

tsacitlumsaputesebnac

naemtonseodsiht-

tiodotdeenrevell'uoy

yhwos

lasisihT.hguoht

].tsixeseldnuBtsacitluM

.stroptibM

.skrowtendehctiwsnoseldnuBfo

atadteNarboCdnaatadretupmoC

ylbailerdnayltneiciffeeromnac

yltaerG.krowtenemasehtnotsixe

.eldnuB

tuphguorhtatadkrowtensevorpmi

ylnosiatadecnisycneiciffedna

tondn

atniopottniopmorfdessap

01swollA.ecivedkrowtenyreveot

eNarboCybelbawolla

sevirrarevenoiduadetuM

sidnanoitanitsedynata

.raehotelbissopmiylraen

secruosersemusnoC

-krowten)htdiwdnab(
tsacitluM23ylnO.*ediw

repdewollaseldnuB

gnisunehwNALV

.sehctiwsdeganam

stroptibM01llaspmawS

dexiF*[

gnisuseldnuB8fomumixam

tonoD.skrowtenbuhretaeper

teNarboCdnaatadretupmocxim

].krowtenretaeperanoatad

s'ecivedenodnestonnaC

enonahteromotoidua

gnisutuohtiwecivedrehto

tnednepednidnocesa

swolla48MNehT[

ebotslennahCoiduA8emaseht

tnereffid4otpunodettimsnart

mumixamehtsihcihw-seldnuB

].secivedt

Table 1. CobraNet Bundles

Bundle Transmission conflicts. Do not transmit onto the

same Bundle from two different CobraNet devices.

causes the loss of the data sent from the second device.

Firmware primer.

The NM 84 contains two pieces of
internal firmware. One is the CobraNet firmware for the
CobraNet interface, the second is the NM 84s own internal
Rane firmware for the front panel interface, et cetera.

The Rane firmware revision number is displayed in the
NM 84 LCD display on the
Rane firmware version (e.g.,
Rane firmware was compiled (e.g.,

top

line during power up. Both the

Version 1.01

) and the date the

Mar 21, 2000

played. Displaying the additional date is a good way to ensure
Y2K compliance. To update the Rane firmware, you must
replace an internal chip.

The CobraNet firmware version is displayed on the
line of the LCD display during power up (e.g.,

2.6.4

).

Interoperability between various CobraNet devices

requires matching CobraNet firmware versions.

Disco utility provides the means to download new CobraNet
firmware into the NM 84. You must obtain Disco and the
required binary CobraNet firmware files separately. There is a
unique firmware file for each model of CobraNet device;
contact Rane for the latest CobraNet firmware if needed.

Doing so

) is dis-

bottom

CobraNet rev

CobraNets

A on Network Hardware

. Before running out to your
nearest computer retailer for networking equipment, check out
the latest list of equipment blessed by Peak Audio at

www.peakaudio.com/cobranet/tested_products.htm

. (As a of
interest, a look through price lists will show you that the price
of a non-managed switch has come down close to the price of
a repeater hub.

You would be wise to spend the extra bucks
and go for the switch, as it will make your network more
flexible and expandable

.)

Four basic network hardware devices exist for use in
CobraNet network designs. The simplest, least expensive and
previously most common are called

repeater hubs

, which send
all incoming data out all of their network ports. Thus repeater
hubs are always multicast (broadcast) devices  all data goes
everywhere. Use repeater hubs only when you have a dedi-
cated CobraNet network (no computers) and when all audio
channels are needed at all CobraNet node locations. If, for
audio security or other reasons, your application requires
certain channels to be accessible only in a certain area of the
network, you cannot use repeater hubs (use switched hubs).
Also, you cannot use repeater hubs in your network if you
need to share computer data and CobraNet data on the same
network. Repeater hubs are devices for freshmen, Network

Manual-9

eciveDerawdraHkrowteNsegatnavdAsnoitatimiL/segatnavdasiD

etupmocroretupmocaecalptonnaC

noatadr

gnisuatadteNarboChtiwkrowtenemaseht

sbuhretaepeR

yeht,.e.i;xelpudflahetarepO

timsnarttonnac

eviecer&

001a,suhT.ylsuoenatlumis

tibM001sikrowtentibM

niyreV

.sedonteNarboC

.)yawagniogylekiltub(evisnepxe

krowtenteNarboCdetacidedanehwtcefreP

llataderiuqersiatadoidualladnadedeensi

po

.ediw-krowten

en

sihtdiwdnabkrowteneht,krowt

8fomumixamdexifasierehT.sbuhretaeper

krowtenbuhretaeperanodettimrepseldnuB

.

tsumsecivedlla,skrowtenretaepernO

flahnidnaetaratademasehttaetare

retemaidkrowtenyebotsuM.edomxelpud

aotdeddaerasbuhretaepersA.snoitcirtser

.secivedkrowtenssorcaderahs/dedivid

aerasehctiwssA

eht,krowtenaotdedd

emoS.sesaercnihtdiwdnabs'krowten

)deganamnu(sehctiwS

gnilbanexelpudllufetarepO

mis

dnatimsnartsuoenatlu

tibM001,suhT.eviecer

(

hcaenitibM001eraskrowten

retnidna)sehctiwsdeganam

.)evahsbuhretaeperekil(

replatottibM002;noitcerid

!trophctiws

cateNarboCsuht

].noitareporeporprongisedrofdnatsrednuro

,.e.i(serutaefecnarelottluafedivorpsehctiws

rehtootsecaf

seigolonhcetkrowtenro)rebif,.e.i(aidem

snoitcirtserretemaidkrowtenoN.)MTA,.e.i

desab-hctiwsgnisU[

,snoisilloctcetedotdeens'teNarboCsevomerskrowten

-hctiws.svretaeperhtiwyltnereffidst

wonkottnatropmitonsisihthguohtla—skrowtendesab

roferomsrallod

retaepernahtevisnepxeeromylthgilsylnO

artxewef)yllaretil(ehthtrowllewsiti;sbuh

.buhretaeperanahthctiwsa

scitsongaid,puteselbixelfylemertxetimreP

hctiwSdeganaM

ekilerasehctiwsdeganaM

merasehctiwsdeganam

yeht;sdioretsnosehctiws

puteselbazimotsucynamreffo

rutaef

.se

elbuortronoitarugifnoc-er

hguohtlA.seitilibapacgnitoohselbuortdna

nahtevisnepxeero

seitilibapaceseht,sehctiwsdeganam-non

krowtennehwsevlesmehtrofyapnahterom

.segatnavdarieht

metsysynamrofesnepxeehthtrow

tub,sehctiwsdeganam-nonnahtyltsoceroM

oteuds

signitoohs

.putesgnirudylralucitrap,deriuqer

Table 2. Network Hardware

101 designs. As with many technologies, repeater bus have
had their day and may soon be a thing of the past.

The second kind of network hardware devices are called
switched hubs which are only a little bit more expensive than
repeater hubs. Using switches for your network greatly
increases the efficiency of the network and allows computer
data to be shared on the network. Switches automatically
view the IP address (destination) of all incoming data and
only send the data out the single required port for delivery,
therefore, switches are unicast (point-to-point) devices.
Switches are the more common network hardware devices
used for CobraNet networks. Switched hubs are like the
Junior or Senior class of the network world.

A third type of network hardware is a managed switch.
Similar to a switch  but the next step up the rung  managed
switches can be user-configured in several ways: you can
create Virtual LANs (VLANs) and change the network
architecture among various VLAN setups; you can set the
managed switch up to prioritize the incoming data so audio
data has higher priority than computer data, for example. With
such capabilities, you can see that managed switches are not
simple, Networking 101 devices  theyre more like the
Ph.D. candidates of the network world.

The fourth network hardware device to introduce is called
a media converter. These are devices that convert the electri-

cal signal from a set of copper wires (e.g., CAT 5 cable) to the
light signal of the fiber optic world. Use media converters
when the distance between network nodes exceeds the 100
meter limitation of copper cable.

Delay Times.

There is an inherent delay between when
audio enters and exits a CobraNet network. For the NM 84,
the delay from when analog audio enters the device until it
appears at the analog output of another NM 84 on a typical,
small network is specified by three numbers. They are
CobraNets fixed 5.33 milliseconds and the A/D and D/A
propagation delays  all of which are specified separately on
the NM 84 Data Sheet. This allows calculating delay times
across the network. The A/D time gets you onto the network;
the network delay is fixed between any CobraNet devices; the
D/A time is the time between the arrival of the CobraNet
audio and the analog audio exiting from the Monitor Outputs
when theyre configured to monitor Network audio. (See the
Peak Audio FAQ web page about the maximum number of
switch hops and delay times through network hardware
devices.)

Your application dictates whether this propagation delay is
acceptable or not. Most CobraNet applications wont have to
worry about this, but just to provide some insight, heres two
applications that may not like this delay. For example, a
theater with an elevated center cluster that provides coverage

Manual-10

for listeners in the initial, center seats may not find this delay
acceptable. Assuming that no propagation delay is added
through other digital signal processing or a digital console
(this may be the case), the additional network delay of 6.5175
feet  assuming NM 84s on and off the network  may place
the arrival time of the direct sound versus the acoustic arrival
outside the Haas effect time. This would make the propagation
delay unacceptable for this application. If youre implement-
ing a mic snake type of application and are including the
monitor audio for stage members on the network, be sure to
not exceed an acceptable delay time; a delay time not much
more than 10 milliseconds (or hopefully less) is probably
acceptable for monitor applications. Decide for yourself.

That being said, there are upcoming technologies (i.e.,
vaporware) that may cut this network propagation time in half
or more. But, like most vaporware, wed have to kill you after
we told you about it. So, when this
well let you know. This way, we wont have to kill you now.

Cables.

installing CAT 5 network cable and connectors can be
challenging and deceiving given that 100 megahertz data is
being transported. Plus, the connector termination is not
intuitively obvious; get it wrong and youll spend hours
blaming equipment when its the cables all along. (

because Ive spent a full day and a half suspecting equipment
when the cables were to blame. And yes, the cables had tested
fine with a continuity tester, but a continuity tester is nowhere
near good enough a test for the required 100 megahertz data
were talking about here.

attention beyond that normally paid by us audio guys who are
now trying to implement these newfangled audio networks.
Do yourself a favor and visit Peak Audios website where
they have a great primer on Network Cabling.

http://www.peakaudio.com/cobranet/network_cabling.htm.

Finding or training people to deal with network cable and
network troubleshooting is a worthwhile investment if your
future includes networked audio systems.

Remember that the network hardware devices chosen for
your network go hand in hand with the Bundles required to
deliver audio for a given application. Multicast networks/
Bundles can be transported over repeater hubs or over
switches; Unicast networks/Bundles require using switches.
You cannot transport unicast data over repeater hubs.

Although the Network Hardware (Table 2) and the
CobraNet Bundle (Table 1) are similar, they are listed sepa-
rately since, for example, multicast data can be transmitted
over repeater hubs or switches. Thus listing them separately
allows you to determine which approach is best for your given
application.

When observing the indicators on switch ports for
CobraNet devices, Rane NM devices appear as full duplex
devices. (Rave devices  available from our friends at QSC
Audio  appear as half duplex; this may change however, so
check with QSC.)

Unlike simpler analog audio cable, choosing and

) This cable stuff requires special

really

becomes available,

I know this

A Few Words About Networks

The opening primer in the Quick Start about designing a
network makes it sound so easy  and it is, relatively  but its
like using three sentences to say

building

new to learn. Networks and Ethernet may be new to audio
folks, but theyre old news to computer types. Here are a few
good places on the Internet for more information on these
subjects:
 Ranes main network help links page:

 Network Design:

 Johns Closet - A down-to-earth set of networking how-

 Ethernet Tutorial - A wonderful tutorial in plain English

 Informit.com - Free online books about programming

 Network Design Tutorials & Other Resources - An indus-

 Ethernet Information - Network Basics / Cabling:

. Like many technologies, there is always something

www.rane.com/ethernet.html

www.peakaudio.com/CobraNet/Network_Design.html

The folks at Peak Audio are, obviously, an invaluable
resource for CobraNet information. Do not underestimate
their interest in the success of your designs or their willing-
ness to help with network design or the myriad questions
that arise.

tos:

www.johnscloset.net

from Lantronix:

www.lantronix.com/training/tutorials

include lots of Web stuff

trial-strength link list of networking topics:

www.alaska.net/~research/Net/nwpages.htm

www.windowsnetworking.com/j_helmig/basics.htm

design a sound system for a

Manual-11

Network Examples

There are two ways to transmit CobraNet audio across a

network. An example for each transmission method follows.

The application dictates which of the two methods to use.

Some applications may require both methods simultaneously.

Multicast Network example [a.k.a. broadcast] requir-
ing simpler repeater hubs

One way to transmit audio over the network is to allow all
of a devices audio channels to be transmitted to all devices.
This is called
using the more familiar term: broadcast. Thus, when you
transmit audio using one of the
through 255), the audio is broadcast to every device on the
network.

This broadcasting of all channels everywhere is required
for applications such as paging when emergency audio must
be delivered to every node. When users at each node need
independent access to all available audio channels, use
Multicast Bundles. If your application is a large music
complex with many audio channels and all the audio channels
are required in all rooms or nodes, use a multicast network by
selecting Multicast Bundles 1-255 for audio transmission.

One advantage when using Multicast Bundles is that an
unlimited number of receivers (CobraNet devices) are allowed
for a single transmission with no additional network band-
width being consumed. This is just like radio broadcasts: one
transmitter, unlimited receivers.

Another advantage is the lower cost and complexity
network that is required to implement the audio system using
Multicast Bundles which are implemented utilizing simple
Ethernet repeater hubs, which are quite inexpensive. This
makes this Multicast application and system a Networking
101 example  inexpensive and easily implemented.

The disadvantages of Multicast Bundles include the loss of
bandwidth network-wide, since every device and every
network cable contains the same quantity of data. All
multicast data takes up the same amount of bandwidth
throughout the entire network. Another thing to be cautious of
is that multicast CobraNet data will swamp any 10 megabit
(10Base-T) data ports on the network.

Modern computers with 100 Mbit PCI Ethernet interfaces
(100Base-T) are quite capable of ignoring this multicast traffic
until their network connection becomes saturated. However, if
the computer is connected to the network via
10 Mbit Ethernet, that link will easily saturate. In any case, it
is not CobraNet which suffers under these conditions, it is the
computers.

The final disadvantage using multicast transmission is the
inability to
CobraNet data on the same network. This is not to say that it
is impossible, it indeed works. However, the problem is that
the network bandwidth required by the computer data is ever-
changing and not controlled or monitored by the CobraNet
devices. Thus, when the computer data suddenly and unpre-
dictably requires more bandwidth than is available, the entire
network bogs down creating computer data collisions which
slow down the computer network, and simultaneously creates

multicast

reliably

in network lingo and can be thought of

Multicast Bundles

share computer network data and

(Bundles 1

Manual-12

audio dropouts, pops or ticks. Not fun, or necessary.

Oftentimes however, computer data must be shared on the
network or not all audio channels are required at every node.
This is where unicast networking comes in.

Unicast Network example [a.k.a. point-to-point]
using more flexible switches

A second way to send audio over the network uses a
different scheme called
use unicast when you require only certain locations on the
network to receive certain channels. For example, in a
campus-sized church complex, it may be useful to send all
channels from the live band mics to the front of house (FOH)
mixer, monitor mix location
the left-center-right (LCR) audio feed to the overflow building
across the street only needs three channels. The stereo FM
broadcast room only needs a stereo mix and the video truck
which is used only every other week may require all channels.

In the above case, it is not required, overly complex, and
most importantly, expensive to send all channels to all
locations. Thus, a unicast (point-to-point) network to feed the
mic channels from the stage to the four required locations 
FOH, monitor, recording studio and video truck  is required.
Therefore, using Bundles starting at 256 or above, sends the
audio over Unicast Bundles which forces the use of network
switches (not repeater hubs) which support unicast data.

For the LCR and stereo FM broadcast feeds, you could use
hard-wired cable runs which may be less expensive. Or, use a
single CAT 5 cable, three CobraNet devices and a couple of
dedicated repeater hubs and utilize a single Multicast Bundle
(1 through 255) to transmit all 5 audio channels to both the
remote LCR and FM locations from the front of the house.

Now lets make things fun and assume, since this church
pays no taxes, that their infinite budget (

days

) requires an audio system in the churchs on-site hotel

and gymnasium. Oh, how fun.

The churchs hotel, gymnasium and attached convention
center requires a dozen stereo channels of background music
as well as 4 paging audio feeds. Additionally, the LCR and
stereo feeds from the church are fed into the gymnasium and
convention center for more overflow on Christmas, Easter and
when Father Guido Sarducci is in town.

Including the 12 stereo background feeds on the network,
allows the church complex access to these background music
sources for intermissions and open houses.

I think you can see where this is going. By using a
combination of multicast and unicast networking, you can
easily use CobraNet technology to efficiently distribute many
audio channels to and from many locations and save consider-
able money on cable, conduit, labor and the re-configuration
time needed to accommodate the wide variety of audio
distribution needs in large and small facilities.

CobraNet network designs must not exceed 32 Multicast
Bundles per VLAN. A VLAN (virtual LAN) is an advanced,
Networking 401 term associated with managed switches
used on only the most advanced systems. Managed switches
allow point-to-point virtual LANs to be defined by the
network designer.

unicast

and

 or point-to-point. You must

to the recording studio. But

so common these

Software and Applications

ActiveX and Software issues

Microsoft ActiveX controls (defined in the next section)
are of concern to the pro audio community. This technology
allows designers of computer-controlled sound systems to
create common front-end software control panels that operate
different manufacturers units, without having to know
anything about their internal code or algorithms. This is
powerful. When more manufacturers jump on the ActiveX
bandwagon, systems designers will no longer be limited by
the products offered by a single, platform-specific (i.e., closed
architecture) manufacturer.

What is ActiveX anyway?

ActiveX is a Microsoft-developed software technology
released in 1996. ActiveX, formerly called OLE (Object
Linking and Embedding), is loosely based on the Component
Object Model (COM), but provides substantially different
services to developers. At this point, you might think:
WHAT!?^* But keep reading! An ActiveX control is a unit of
executable code (such as an .EXE file) that follows the
ActiveX specification for providing software objects. This
technology allows programmers to assemble reusable software
controls into applications and services. However, software
development using ActiveX technology should not be
confused with Object-Oriented Programming (OOP). OOP is
concerned with creating objects, while ActiveX is concerned
with making objects work together. Simply stated, ActiveX is
a technology that lets a program (the ActiveX control) interact
with other programs over a network (e.g., the Internet or
Ethernet), regardless of the language in which they were
written. ActiveX controls can do similar things as Java, but
they are quite different. Java is a programming language,
while ActiveX controls can be written in any language (e.g.,
Visual Basic, C, C++, even Java). Also, ActiveX runs in a
variety of applications, while Java and Javascript usually run
only in Web browsers. ActiveX controls can be used in web
pages and within visual programming languages such as
Borlands Delphi, Sybases PowerBuilder, Microsofts Visual
Basic and even in tools such as Adobes GoLive,
Macromedias DreamWeaver and National Instruments
LabVIEW.

In English, for our pro audio applications, ActiveX control
objects are the sliders, buttons, indicators and other graphical
screen entities. The objects have properties such as slider
position and slider range and on or off for buttons and
indicators, etc. Once the screen objects are chosen and placed,
further ActiveX controls can then be used to link the objects
properties to other ActiveX controls. Thus, allowing linking
an ActiveX slider to the ActiveX control for a devices level
control. Then moving the level control graphic slider subse-
quently varies the audio level and vice versa.

Each ActiveX control is made up of Properties and Events.
ActiveX control Properties are values associated with the
control, which might include such things as level settings,
mute condition and meter readings. ActiveX control Events
tell the computer something significant has happened, such as
a switch closure, button press or clip detection.

ActiveX allows the manufacturer to create an object (a
piece of software code) which fully describes a device, while
hiding the implementation details such as protocol from the
programmer. By hiding the communication details, there is no
longer a need for different manufacturers to agree on proto-
col. This lack of a protocol standard means that cooperation
between manufacturers is not required. It allows each manu-
facturer to choose the best protocol for their devices.

For example, no longer would you need to know that the
17th byte of a 32-byte status message meant that the units
second output channel was muted. With an ActiveX control,
you might simply refer to the devices output 2 mute status as
Device1.Out2Mute. See the RaneNote Emerging Standards
for Networked Audio System Control and Controlling
Audio Systems with ActiveX Controls over CobraNet and
other Ethernet-based Networks, both downloadable from the
Rane website Library.

Implementing ActiveX controls

An example might help clear this up. A few assumptions
are that a computer is used to control an audio system over an
Ethernet network and that something on the computers screen
controls some function of the system. The basic idea is to
place controls on the computer screen and link them, using
ActiveX, to a parameter in the system. Whats important here
is that only the controls required by the computers end user
need be displayed. Additionally, more detailed interfaces
(hidden or password-protected web pages) can then be created
to provide any level of system parameter access desirable
from complete system control, to a lone system power button
or anything in-between. No longer are systems limited to the
number of security levels provided by vendors software, nor
are you limited to controlling a single system parameter per
screen control. For example, you can link multiple ActiveX
controls to a single screen object, thus adjusting EQ level
simultaneously with master level control and limiter threshold.
You can also program actions when certain events occur, such
as triggering audio playback or turning a system off at a
certain time or adjusting delay time as the temperature
changes.

You can control different parameters inside the same
device from different computers on the network as well as
controlling the same parameter from multiple computers. This
is one of the major advantages of networks  multiple control
locations will automatically be updated when changes are
made by any control location.

Microsoft FrontPage 2000 ActiveX Example

Many use Microsofts FrontPage 2000 to create user
interface web pages for computer-controlled systems. These
web pages may or may not be accessible over the Internet.
Once you master the ActiveX concept, using FrontPage with
ActiveX provides literally an infinite number of programming
possibilities. More information about the NM 84s ActiveX
controls and the ActiveX controls for Ranes RW 232 devices
is found in the sections on the next page.

Manual-13

NM 84 ActiveX Example

The short version of the FrontPage 2000 procedure used to
setup a web page with ActiveX controls for a Rane NM 84
devices parameters goes as follows:

Insert a Rane NM 84 ActiveX control in a new web page.
(This software/control ships with the unit or can be found on
our website. Running this NM 84 setup procedure registers
the Rane NM 84 ActiveX control with the computer used to
create the web page. Otherwise, no special icon or folder is
created after running the setup, so save time by
for the NM 84 software/control other than from within
FrontPages ActiveX list.) Set the inserted NM 84 controls
Properties for your application. Generally, from FrontPages

ActiveX Control Properties

unique
this control to the specific NM 84 device by entering the NM
84 devices
tab. The NM 84 control also must be assigned an update rate
which is found on the
good default value might be 5 which provide an update
every half second. Dont get overzealous with this update rate
since its a function of many things and can negatively effect
the speed at which controls and parameter changes take effect.

from the vast list of available ActiveX controls. If you cant
find a control that suits your fancy, further ActiveX controls
can be found on the Internet as shareware, bought from
ActiveX providers often in packages or created from scratch
for complete customization. Adjust the size, orientation and
placement of the control for optimum ergonomics being sure
to consider the user, the application and the requirement for
further controls on this same page. Keeping the number of
total controls on any one page low is very wise. See why in
the September, 2000 AES preprint by Ranes Stephen
Macatee and Devin Cook titled

With ActiveX Controls Over CobraNet And Other Ethernet-
Based Networks

(or button), uniquely
tab. Then in the
and minimum value to match the NM 84 devices parameter
that youll link to this slider. Sometimes youll find that youll
need to adjust these maximum and minimum values here (or
in the Script language discussed next) to properly display or
be compatible with the parameter being adjusted. For ex-
ample, the Mic_Trim ActiveX control has a minimum value
of 0 and a maximum of 36, but the actual displayed range
of the Trim control is -20 to +16 dB in 1 dB steps. Thus, there
are 36, 1 dB steps. Also, often the control link may be
backwards such that the maximum value may correspond to
the lowest slider position. Fix this when updating the
control by subtracting the controls maximum setting from the
desired setting within FrontPages VBScript language.

parameter, use Microsofts VB Script language by associating
the sliders Name with the specific NM 84 Control Name.
Youll find the list of valid NM 84 ActiveX Control Names at
the end of this Manual.

Name

in the

IP address

Next, insert an ActiveX slider, button or what have you

.

In the

ActiveX Control Properties

Parameters

To link the slider to the desired NM 84 internal device

window, this involves providing a

Object Tag

in the

NM 84 SNMP Control Setting

tab for the control. Then, link

NM 84 SNMP Control Setting

Controlling Audio Systems

window for the slider

Name

the control in the

tab, set the controls maximum

not

looking

tab. A

Object Tag

To track slider or system changes and update either the
web page, the NM 84 device, or both, well need to use
Microsofts Visual Basic Script language. This is where the
programming comes in. Yes, it does say
Remember when you could do your job without the need to
program anything except the time on your wind up watch?
Some programming tasks here are things like initializing the
controls with valid information usually by reading the NM 84
devices current settings, then updating the on-screen controls
so they match the device. You also need the Script software to
scan for any changes and make updates accordingly. It is also
wise to be sure that any requested changes to parameter values
are within the proper numerical range, thus avoiding strange
and unpredictable behavior. This is usually called bounds
checking by programmers. Since these web page and
network technologies allow multiple control locations, be sure
your code handles this. For example, NM 84 device param-
eters can be changed from the NM 84s front panel, from the
web page itself, from another copy of the same web page
being run elsewhere on the network, or changes can also be
made from contact closure memories. Take this into account
when writing the update settings code by scanning indepen-
dently for changes to the devices settings and changes to the
web page controls. Then update things so the device settings
and the web page controls always match. The Rane has
example code with comments.

programming

.

Manual-14

Computer IP Setup

If youre using a computer with the NM 84, it must be set
for network operation to allow it to speak using TCP/IP
protocol. (TCP stands for Transmission Control Protocol.) If
your computer is already set up for network operation you can
move on in your life and skip this section.

Windows 95/98 PC Network Communications Setup

As you go through the following procedure your computer
tells you (on more than one occasion) that it needs to reboot
before changes take effect. Just go along with it when this
happens. Yeah, its a big waste of time but this is an owners
manual, not an editorial page  so just do it, OK?

1. Insure you have a functional Ethernet adapter (NIC or

Network Interface Card) installed in the PC. If installed, its
operation may be checked by right clicking on 

puter

 followed by a left-click on the selection 
and again a left-click on the 


System Properties

to the left of 
adapters. A malfunctioning adapter is indicated by either a
yellow question mark or a red X. There are several
troubleshooting aids available in Win-dows Help to assist
you in making the network adapter functional.

2. Once you have a correctly operating Ethernet adapter, TCP/
IP is easy to configure. To begin, open 


Start > Settings



Configuration

such as your network card and possibly dial-up networking.
Below these is a list of network protocols previously
configured for the system. If TCP/IP has been configured
and bound to the Ethernet adapter, you will see an entry
resembling 

Adapter.

there, go through step 3 first.

3. To add TCP/IP to the LAN Adapter, click the 
in the Network dialog. A list of network component types
displays. Choose 
turers displays. Click on 
right-hand window, then OK.

4. To be a part of a TCP/IP network, your computer (and each
network device including the NM 84) needs a unique IP
address of its own. If not already open, open 

Control Panels > Network
NameOfAdapter PnP LAN Adapter

Then choose 


Specify an IP address

an existing network, you must now obtain a valid address
from the network administratorif you have one. If not,
you may use an address out of the internationally accepted
private network block of addresses, which is

192.168.nnn.nnn where nnn represents any number
between 0 and 255. A good choice might be

192.168.100.100 just because its easy to remember if you
ever need to know it again. Set the 

255.255.0.0 for most installations. These two settings allow
a network with addresses in the range of 192.168.0.0
through 192.168.255.255. Click the OK buttons as many

TCP/IP -> NameOfAdapter Pnp LAN

 If this shows on the list, skip to step 4. If its not

 dialog box. Click on the plus (+) sign

Network Adapters

, then 

 tab shows a list of configured devices,

Protocol

Properties > IP Address

Device Manager

 to view the configured

My Computer

Control Panel > Network

, then 

Microsoft

. Highlight the 

 option. If your computer

Add

. A list of manufac-

, then 

 by clicking on it.

. Click on the

Subnet Mask

My Com-
Properties

 tab of the

Add

 button

TCP/IP

 in the

Settings >

TCP/IP ->

is

 to

 or

. The

part of

times as they appear to extinguish all the network setup
dialog boxes.

Once youve set networking on a Win95/98 computer, youll
notice it wants a user name and optional password each time
it boots. To eliminate this nuisance, go back in to

Panel > Network

selection from

Logo

n then click OK again. Oh, and guess what? Your
computer will want to be rebooted again for the change to
take effect. Good news, though, it wont ask for a user name
and password this time.

and change the

Client for Microsoft Network

Primary Network Logo

s to

Control

Windows

Glossary of Terms

As with any technology, new terms are thrown about like a



hot Mr. Potatohead at a 5 year olds birthday party. The
CobraNet website (
valuable resource for such jargon and includes a Terminology
page for CobraNet terms. Here are a few just to keep things
going.

Asynchronous

a clock or semaphore, proceeding independently. Email and
computer file transfers are examples of asynchronous data
streams.

Audio Channel

single channel of audio in a CobraNet network; the capital
letters. (The term formerly known as

Broadcast
Broadcast addressing

ing. Whereas it is possible, in some cases, to indicate
intended recipients of multicast data, broadcast data is
unconditionally received by all devices within a network.

Bundle

audio over an Ethernet network, CobraNet places up to 8
Audio Channels in Bundles. (The term formerly known as

Network Channel

Concentrator

interconnect such as a Patch Panel. Concentrator is less
technically concise than Hub.

CobraNet

combination of hardware, software and protocol which
distributes many channels of digital audio over Fast
Ethernet. CobraNet supports switched and repeater Ethernet
networks. On a repeater network, CobraNet eliminates
collisions and allows full bandwidth utilization of the
network. CobraNet uses standard Ethernet packets and
network infrastructure.

CobraNet node

ance with the CobraNet specification for transmission and/
or reception of digital audio and associated sample clock.

CobraNet port

specifically, the RJ-45 connector on a CobraNet device.

 See Broadcast addressing.

 A group of up to 8 Audio Channels. To transport

 A Peak Audio technology, CobraNet is a

www.peakaudio.com/cobranet

 Not synchronized by a shared signal such as

 This is an ambiguous term, but defines a

Sub-channel

 A special case of Multicast address-

.)

 A Repeater Hub, Switching Hub or passive

 Any network device which is in compli-

 The same as CobraNet node, but more

) is a

n

.)

Manual-15

Conductor

supplies the master clock. A conductor arbitration proce-
dure insures that at any time there is one, and only one,
conductor per network. The conductor transmits beat
packets at a regular interval. The time interval between beat
packet transmission is the mechanism of clock delivery.
The conductor is also responsible for generating transmis-
sion permissions based on forward reservations received in
reservation packets. The transmission permissions are
published in the beat packet.

Crossover cable

network devices to connect directly together without the
need for a hub. The receive and transmit pairs must be
swapped within the cable.

Since a normal (non-crossover) network cable physically
looks like a crossover cable, one of three practices are
suggested: clearly label all crossover cables so they are not
confused with normal standard ethernet cables. Wire two
female wall plate jacks back to back with the proper
swapping and use this adapter as a 2 port hub. Another
useful adapter uses a standard RJ-45 at one end and a
female wall jack at the other cross-wired. Making these two
adapters short helps avoid confusing standard network
cables from crossover cables.

cobranet/network_cabling.htm.

Fully Switched Network

Switching Hubs. With the elimination of Repeater Hubs,
the collision condition is removed from a fully switched
network.

Hub

used to refer to either a Repeater Hub or a Switching Hub.

Isochronous

equal times; recurring at regular intervals. An isochronous
data stream is characterized by the fact that data delivered
late is unusable. Live audio and video are examples of
isochronous data streams.

Media Converter

media types on each port. Media converters can convert
between CAT5 Cable and Fiber.

Multicast

 The CobraNet device on the network which

 A special network cable that allows two

One End Cable the Other End

TR+ pin 1  pin 3 RCV+
TR- pin 2  pin 6 RCV-
RCV+ pin 3  pin 1 TR+
RCV- pin 6  pin 2 TR-

http://www.peakaudio.com/

 A network built entirely from

 Hub is not a technically concise term. The term can be

 Uniform in time; of equal time; performed in

 A two port Repeater Hub with different

 See Multicast addressing.

Multicast addressing

to a group of, or all devices on a network. All devices
receive multicast addressed data and decide individually
whether the data is relevant to them. A Switched Hub is
typically not able to determine appropriate destination port
or ports for multicast data and thus must send the data out
all ports simultaneously just as a Repeater Hub does.
Multicast addressing is to be avoided whenever possible
since it uses bandwidth network wide and since all devices
are burdened with having to decide whether multicast data
is relevant to them.

Network Channel

Bundle is a Peak Audio term, so call them.)

Packet

Performer

Repeater Hub

Repeater Network

Sub-channel
Switched Network

Switching Hub

Unicast
Unicast addressing

 A series of bits containing data and control informa-
tion, source and destination addresses and formatted for
transmission from one node to another.

 All units except the conductor operate as a
performer. A performer must re-synthesize a sample clock
based on arrival times of received beat packets. A per-
former may transmit isochronous data packets only if given
transmission permission to do so by the conductor.

signal arriving in any port is electrically regenerated and
reproduced out all other ports on the hub. A repeater hub
does not buffer or interpret the data passing through it. If
data signals arrive simultaneously from multiple ports, a
collision condition is recognized by the hub and a special
jam signal is transmitted out all ports.

Repeater Hubs. Repeater networks share the same band-
width among all connected DTEs.

 Old term now called Audio Channel.

Switching Hubs. It is possible, even common to build a
network from a combination of interconnected Repeater
Hubs and Switched Hubs.

examines addressing fields on data arriving at each port and
attempts to direct the data out the port or ports to which the
data is addressed. Data may be buffered within the Switch-
ing Hub to avoid the collision condition experienced within
a Repeater Hub. A network utilizing Switching Hubs
realizes higher overall bandwidth capacity since data may
be received through multiple ports simultaneously without
conflict.

 See Unicast addressing.

specific network device. A switching hub examines the
unicast address field of the data and determines on which
port the addressed device resides and directs the data out
only that port. Delivery of an email message is an example
of unicast data addressing.

 Data which is Multicast is addressed

 Old term now called Bundle. (Hey,

 An Ethernet multi-port repeater. A data

 A network built with one or more

 A network built with one or more

- A Switching Hub, or simply "Switch",

 Data which is unicast is addressed to a

Manual-16

Memory Recall Port

The MEMORY RECALL PORT (MRP) provides contact
closure control to recall any of the 16 Memories. Eight of the
Memories are recalled with individual switch closures to a
single terminal (see the Normal section of Table 1). Memories
in multiple units may be recalled by either connecting the
MRP terminals in parallel or by transmitting the MRP contact
closure over the network. See the Memory Edit Page section
of this manual.

Rane Firmware version 1.01 functions as follows: Only
momentary switches should be used since only single closures
are recognized. The NM 84 MRP is
therefore, changes to the switch states will not be updated
until the MRP conditions are changed when the power is on.
If more than one terminal is grounded at a time, only the first
closed switch is recognized. Subsequent switches are ignored
once the first switch is and remains closed. If multiple
switches are closed, once a single switch remains closed will
that memory be recalled.

However, certain combinations of terminals may be
grounded to activate Paging or Binary modes (see table). A
Binary mode allows access to all 16 Memories. For ex-
ample, connect the four contacts of a binary switch, plus the
additional Binary mode closures shown in the Table. Paging
mode provides an easy way to configure a system which uses
a single switch (such as a mic or key switch) to toggle
between two sequential Memories (See table). When wiring
contacts,

only use Normal, Paging or Binary mode  do not

switch between modes.

not

read after power up,

1 2 3 4 5 6 7 8 edoM tluseR

10000000 1

0 1000000 2

00 100000 3

000 10000 4

0000 1000 5

NORMALPAGINGBINARY

00000 100 6

000000 10 7

0000000 18

0 0 0 0 0 1 1 1 1

1 0 0 0 0 1 1 1 2

0 1 0 0 0 1 1 1 3

1 1 0 0 0 1 1 1 4

0 0 1 0 0 1 1 1 5

1 0 1 0 0 1 1 1 6

0 0 0 1 0 1 1 1 7

1 0 0 1 0 1 1 1 8

0 0 0 0 1 1 1 1 9

Memory

Switch

Mic

Switch

Paging
Mode

87654321C

MRP Wiring

MRP Binary Control
1 = switch closed (between COM and 1,2,3,etc.)
0 = switch open

1 0 0 0 1 1 1 1 01

0 0 0 0 1 1 0 1 1

10 0 0 1 1 0 1 2

0 1 0 0 1 1 0 1 3

1 100 1 1 0 1 4

0 0 1 0 1 1 0 1 5

10 1 0 1 1 0 1 6

0 1 1 0 1 1 0 1 7

1 1 10 1 1 0 1 8

0 0 0 1 1 1 0 1 9

10 0 1 1 1 0 1 01

0 1 0 1 1 1 0 1 11

1 1 0 1 1 1 0 1 21

00 1 1 1 1 0 1 31

10 1 1 1 1 0 1 41

0 1 1 1 1 1 0 1 51

1 1 1 1 1 1 0 1 61

Manual-17

Control Name: Rane Corporation NM 84 SNMP Active X Control

Description: SNMP Control of a NM 84

Design Time Parameters:

IP Address NM 84s Device Address
Update Freq How often (in 100ms steps) the NM 84s status is checked

Runtime Parameters:

condPriority Conductor Priority ( 0 = Never Conductor, 32 = Default )
Conductor (Read Only) return TRUE if the NM 84 is currently the conductor
Online (Read Only) returns TRUE if the NM 84 is currently operational

: for Idx 0->7 corresponds to Input 1-8

Mic_Mute(Idx) TRUE/FALSE for Mic Mute setting
Mic_Phantom_Power(Idx) TRUE/FALSE for Mic Phantom Power setting
Mic_Line_Mode(Idx) TRUE/FALSE for Line Mode setting
Mic_Mic_Gain(Idx) (0 = 15dB, 1=30dB, 2=45dB, 3=60dB) for Mic Gain setting
Mic_Line_Gain(Idx) (0 =-5dB, 1=+10dB) for Line Gain setting
Mic_Trim(Idx) (0 =-20dB, 1=-19dB..36=0dB) for Trim setting
Mic_Filter(Idx) (0 =Off, 1=Low Cut, 2=High Cut, 3=High/Low Cut) for Filter setting
Mic_Limiter(Idx) (0 =+18dB,1=+18,48=-30dB) for Limiter setting

Mic1_Mute Equates to Mic_Mute(0)
Mic1_Phantom_Power Equates to Mic_Phantom_Power(0)
Mic1_Line_Mode Equates to Mic_Line_Mode(0)
Mic1_Mic_Gain Equates to Mic_Gain(0)
Mic1_Line_Gain Equates to Mic_Line_Gain(0)
Mic1_Trim Equates to Mic_Trim(0)
Mic1_Filter Equates to Mic_Filter(0)
Mic1_Limiter Equates to Mic_Limiter(0)

Mic2_Mute Equates to Mic_Mute(1)
Mic2_Phantom_Power Equates to Mic_Phantom_Power(1)
Mic2_Line_Mode Equates to Mic_Line_Mode(1)
Mic2_Mic_Gain Equates to Mic_Gain(1)
Mic2_Line_Gain Equates to Mic_Line_Gain(1)
Mic2_Trim Equates to Mic_Trim(1)
Mic2_Filter Equates to Mic_Filter(1)
Mic2_Limiter Equates to Mic_Limiter(1)

Mic3_Mute Equates to Mic_Mute(2)
Mic3_Phantom_Power Equates to Mic_Phantom_Power(2)
Mic3_Line_Mode Equates to Mic_Line_Mode(2)
Mic3_Mic_Gain Equates to Mic_Gain(2)
Mic3_Line_Gain Equates to Mic_Line_Gain(2)
Mic3_Trim Equates to Mic_Trim(2)
Mic3_Filter Equates to Mic_Filter(2)
Mic3_Limiter Equates to Mic_Limiter(2)

Mic4_Mute Equates to Mic_Mute(3)
Mic4_Phantom_Power Equates to Mic_Phantom_Power(3)
Mic4_Line_Mode Equates to Mic_Line_Mode(3)
Mic4_Mic_Gain Equates to Mic_Gain(3)
Mic4_Line_Gain Equates to Mic_Line_Gain(3)
Mic4_Trim Equates to Mic_Trim(3)
Mic4_Filter Equates to Mic_Filter(3)
Mic4_Limiter Equates to Mic_Limiter(3)

Manual-18

Mic5_Mute Equates to Mic_Mute(4)
Mic5_Phantom_Power Equates to Mic_Phantom_Power(4)
Mic5_Line_Mode Equates to Mic_Line_Mode(4)
Mic5_Mic_Gain Equates to Mic_Gain(4)
Mic5_Line_Gain Equates to Mic_Line_Gain(4)
Mic5_Trim Equates to Mic_Trim(4)

Mic5_Filter Equates to Mic_Filter(4)
Mic5_Limiter Equates to Mic_Limiter(4)

Mic6_Mute Equates to Mic_Mute(5)
Mic6_Phantom_Power Equates to Mic_Phantom_Power(5)
Mic6_Line_Mode Equates to Mic_Line_Mode(5)
Mic6_Mic_Gain Equates to Mic_Gain(5)
Mic6_Line_Gain Equates to Mic_Line_Gain(5)
Mic6_Trim Equates to Mic_Trim(5)
Mic6_Filter Equates to Mic_Filter(5)
Mic6_Limiter Equates to Mic_Limiter(5)

Mic7_Mute Equates to Mic_Mute(6)
Mic7_Phantom_Power Equates to Mic_Phantom_Power(6)
Mic7_Line_Mode Equates to Mic_Line_Mode(6)
Mic7_Mic_Gain Equates to Mic_Gain(6)
Mic7_Line_Gain Equates to Mic_Line_Gain(6)
Mic7_Trim Equates to Mic_Trim(6)
Mic7_Filter Equates to Mic_Filter(6)
Mic7_Limiter Equates to Mic_Limiter(6)

Mic8_Mute Equates to Mic_Mute(7)
Mic8_Phantom_Power Equates to Mic_Phantom_Power(7)
Mic8_Line_Mode Equates to Mic_Line_Mode(7)
Mic8_Mic_Gain Equates to Mic_Gain(7)
Mic8_Line_Gain Equates to Mic_Line_Gain(7)
Mic8_Trim Equates to Mic_Trim(7)
Mic8_Filter Equates to Mic_Filter(7)
Mic8_Limiter Equates to Mic_Limiter(7)

: for Idx 0->3 corresponds to Monitor 1-4

Out_Local(Idx) TRUE/FALSE for Monitor Local setting
Out_Mic_Index(Idx) (0=Off,1=Input 1,,8=Input 8) for Monitor Local Mic setting
Out_Bundle(Idx) Bundle (a.k.a. Network Channel) to Receive
Out_AudioChannel(Idx) (0..7) Network AudChannel to Receive

Out1_Local Equates to Out_Local(0)
Out1_Mic_Index Equates to Out_Mic_Index(0)
Out1_Bundle Equates to Out_Channel(0)
Out1_AudioChannel Equates to Out_AudChannel(0)

Out2_Local Equates to Out_Local(1)
Out2_Mic_Index Equates to Out_Mic_Index(1)
Out2_Bundle Equates to Out_Channel(1)
Out2_AudioChannel Equates to Out_AudChannel(1)

Out3_Local Equates to Out_Local(2)
Out3_Mic_Index Equates to Out_Mic_Index(2)
Out3_Bundle Equates to Out_Channel(2)
Out3_AudioChannel Equates to Out_AudChannel(2)

Out4_Local Equates to Out_Local(3)
Out4_Mic_Index Equates to Out_Mic_Index(3)
Out4_Bundle Equates to Out_Channel(3)
Out4_AudioChannel Equates to Out_AudChannel(3)

TXAB_24Bits TRUE/FALSE for NetTx A/B 24 Bit Format Mode
TXCD_24Bits TRUE/FALSE for NetTx C/D 24 Bit Format Mode
TXAB_Split (0=1/7,,6=7/1) for NetTx A/B AudChannel splitting
TXCD_Split (0=1/7,,6=7/1) for NetTx C/D AudChannel splitting
TXA_Bundle NetTx As Bundle
TXB_Bundle NetTx Bs Bundle
TXC_Bundle NetTx Cs Bundle
TXD_Bundle NetTx Ds Bundle

©Rane Corporation 10802 47th Ave. W., Mukilteo WA 98275-5098

TEL [phone] FAX [phone] WEB www.rane.com

108213

Manual-19