User manual
1 ' ) 8 3 8 ) ) 8 3 & 5
9
99
9
Hardware vs. Software Devices continued:
The second half of this equation, as mentioned above, is the audio transport. This transport is the
CobraNet network that carries audio from one location to another. In the past, and if you are
familiar with MWare, this was represented by a block with “wire nodes” on it that represent the
actual input and output points for the system. Within NWare these nodes a singular identities not
blocks and are called up by accessing the Flyoffs under the specific NioNode and within the CM-
1 sub folder. Once these CM input and output nodes are placed into the design view they can be
re-labeled for ease of reference. “Flyoffs” are further discussed in the Nion/NWare manual. What
is very important to note is that the hardware unit, the CAB itself, and the audio transport device
DO NOT necessarily match up. For example, it is possible to have one output Flyoff wired to
multiple CAB 4n units although generally, the input side is always a one-to-one relationship. In
figure 2 following, you can see a Flyoff configuration in NWare showing the CAB 4n ID and
Bundle Assignments when you open the CAB4n block including a simple input to output path via
an audio processing block. The LEDs for Link, Transmitter and Receiver indicate that an audio
data stream is successfully being received from a distant network location.
To summarize. It is very important to understand the relationship between the CAB hardware, it’s
associated software control and the CobraNet™ network, or “audio transport”. The blocks and
Flyoffs in this example flowing receive digital audio from, and carry digital to, distant CobraNet
network locations. This audio enters and exits the MediaMatrix system at these blocks. The wires
represent the digital audio path within the MediaMatrix system. The blocks labeled CAB 4n, the
yellow “Taxi”, represent the actual CAB hardware. There must be one of these for each
corresponding hardware piece. The hardware, via its control panel, can be “assigned” to any
network audio channel, called a “bundle”. This bundle is also assigned in the CobraNet transport
block. It is this bundle assignment that gets the audio from the CAB’s analog port and onto the
network. If this is confusing to you, stop and re-read this section. It is vital to your ability to
successfully implement a CobraNet audio system using MediaMatrix products. If you understand
it....kinda, but still need help, read on....you’ll see how it all fits together as you start hooking up
CABs and passing audio from point to point.