User Manual
Table Of Contents
- Copyright
- About Audinate
- Introduction
- Installing Dante Controller
- Dante Basics
- Discovery and auto-configuration
- Device Channels
- Differentiating between input and output channels
- Device Names and Channel Labels
- Routing Audio
- Clock Synchronization
- Latency
- Device Lock
- Dante Control and Monitoring
- Starting Dante Controller
- Using Dante Controller
- Network View
- Status Bar
- Network View Tabs
- Channel Groups
- Clock Status Monitoring
- Clock Status Monitor
- Automatic Notification of Device Errors
- Device View
- Device View Tabs
- Multicast Transmit Flow Configuration
- Using Dante Controller with Dante Domain Manager
- Presets
- Troubleshooting
- Fanout
- Messages on Startup
- Computer Configuration Checklist
- Troubleshooting Dante IP Address Configuration
- Troubleshooting Switch Configuration and Cabling
- Index
Dante Controller User Guide
Copyright © 2018 Audinate Pty Ltd. All rights reserved.
-20-
n A channel that puts audio data onto the network is known as a transmitting, Tx or output channel.
n A channel that takes data off the network is known as a receiving, Rx or input channel.
Device Names and Channel Labels
In Dante, devices and audio channels are identified by names and labels, not 'magic numbers'. Device
names and channel labels can be customized.
n Dante routing is performed using the device names and channel labels. A receive channel can be sub-
scribed to the name of a transmit channel at a device.
Example: “Analog L@my-transmitter” describes a channel labelled “Analog
L” on a device named “my-transmitter”. Device names must be unique on a
Dante network. Channel labels must be unique on the device.
n If a device or channel is renamed, Dante routing considers it to be a different device or channel. If a
new device or channel is then given the old name, Dante routing will route from the new device in
place of the previous device.
Example: The power supply on “stage-box” fails and “stage-box” needs to be
replaced. The old “stage-box” is removed, and a new box is plugged in and named
“stage-box”. Dante receivers previously subscribed to the old “stage-box” will
now automatically restore their subscriptions to the new “stage-box”.
n Device names must be unique on the network. If you attempt to rename a device using Dante Con-
troller to a name that is already in use on the network, Dante Controller will notify you and reject the
name change.
Example: There is an existing device on the network called “MY16-slot1”. If user
attempts to rename another device to “MY16-slot1” Dante Controller will notify
you that the name is already in use. The device will not be renamed.
n If a new device is added to the network with a name that already exists, a name conflict is detected.
One of the devices will adopt a temporary placeholder name, by appending a space and (2) to its old
name. This device will not be able to transmit audio until it is manually renamed, and some con-
figuration options will be disabled for that device in Dante Controller.
Note: A device that has been renamed with (2) appended (e.g. “MY16-slot1 (2)”) will not be able
to transmit audio until it is renamed. The device name must be changed by the user to be a valid non-
conflicting name before the device can become fully functional. A device that has failed with a name
conflict will retry its configured name if it is rebooted. If the other device has been removed or
renamed, the previously failed device will resume normal operation.
Rules for Names and Labels
n All Dante names and labels are up to 31 characters in length.
n Name and label comparisons are case-insensitive: “Guitar” and “guitar” are treated as the same
label.
n Unicode and non-roman characters are not supported.
n Device names should follow Domain Name System (DNS) hostname rules. Legal characters are A-
Z, a-z, 0-9, and '-' (dash or hyphen).