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.
-21-
n Device names cannot begin or end with a hyphen.
n Device names must be unique on the network.
n Tx channel labels may use any character except '=' (equals), '.' (full stop or period), or '@' (at).
n Tx channel labels must be unique on a device. Tx channel labels do not need to be unique on the net-
work, as they are always qualified by device (channel@device).
n Rx channel labels follow the same rules as Tx channel labels.
Routing Audio
Routing Terminology
n Device: A device means a Dante-enabled device, and more specifically that component of the audio
equipment that implements the Dante interface. A Dante device typically has Tx and Rx channels
and other routing-related properties.
n Transmit (Tx) channel: A transmit channel transmits audio from the audio hardware onto the net-
work.
n Receive (Rx) channel: A receive channel receives audio from the network and sends it to the audio
hardware.
n Flow: Dante audio routing creates flows. Each flow carries several channels of audio from a trans-
mitter to one or more receivers. Unicast routing creates flows to single receivers. Multicast routing
creates flows that can be received by multiple receivers. Multicast flows are assigned IDs enabling
them to be identified in Dante Controller.
n Unicast routing: Unicast flows are point-to-point from a single transmitter to a single receiver.
Unicast flows typically have room for 4 channels of audio.
n Multicast routing: Multicast flows are one-to-many from a single transmitter to any number of receiv-
ers. Use Dante Controller to choose which channels are to be multicast. Unlike unicast routing, mul-
ticast flows consume network bandwidth even if there are no receivers, but do not require additional
bandwidth to add more receivers.
n Subscription: A subscription configures a receive channel to receive audio from a transmit channel
on another Dante device.
n Subscription status: For a receive channel, subscription status indicates whether it is subscribed,
whether it is receiving unicast or multicast audio, whether the subscription is OK, or whether an error
has occurred.
Subscription
Dante routing is performed by associating a receiving (Rx) channel with a transmitting (Tx) channel. This is
called subscription.
Example: Route Tx channels 1 and 2 (labeled “Audio L” and “Audio R”) on the device labeled
“Source” to Rx channels 3 and 4 on the device labeled “Dest”.