CEA Audio Networking and Dante Protocol 2 — Questions and Answers
Question 1: What is AES67 and how does it relate to Dante?
- A proprietary Audinate protocol incompatible with Dante audio networks
- An AES standard for audio transport over IP networks; Dante can operate in AES67 interoperability mode to exchange audio with other AES67-compliant systems (Correct answer)
- A fiber-optic audio transport standard used for distances exceeding 100 meters
- A compression standard applied to reduce Dante audio bandwidth requirements
Correct answer: An AES standard for audio transport over IP networks; Dante can operate in AES67 interoperability mode to exchange audio with other AES67-compliant systems
AES67 is an open AES standard for high-performance audio transport over IP networks. Dante supports an AES67 interoperability mode, allowing Dante devices to send and receive audio to/from other AES67-compatible systems (such as Ravenna, Livewire+, and Q-LAN), enabling multi-vendor audio networking environments.
Question 2: In a managed Dante network, what is the purpose of configuring 'QoS' (Quality of Service) on network switches?
- To encrypt Dante audio packets for secure transmission
- To prioritize Dante audio traffic and PTP synchronization packets over lower-priority data traffic, ensuring consistent latency and preventing dropouts (Correct answer)
- To limit the bandwidth available to non-audio devices on the shared network
- To assign static IP addresses to Dante devices for consistent device discovery
Correct answer: To prioritize Dante audio traffic and PTP synchronization packets over lower-priority data traffic, ensuring consistent latency and preventing dropouts
QoS policies on managed switches mark and prioritize Dante audio and PTP synchronization packets with higher priority queues. This prevents audio dropouts when network congestion occurs from other data traffic (file transfers, video streaming) competing for bandwidth on shared infrastructure.
Question 3: What latency settings are typically available in Dante Controller, and what determines the appropriate setting?
- Only one fixed 1 ms latency is available; it cannot be adjusted
- Typically 0.25 ms, 0.5 ms, 1 ms, and higher; the appropriate setting depends on network quality, switch count between devices, and the acceptable monitoring latency for the application (Correct answer)
- Latency is set at the hardware device and cannot be adjusted from software
- Dante operates at a fixed 5 ms latency to ensure compatibility with all switch types
Correct answer: Typically 0.25 ms, 0.5 ms, 1 ms, and higher; the appropriate setting depends on network quality, switch count between devices, and the acceptable monitoring latency for the application
Dante Controller offers selectable latency settings (commonly 0.25 ms, 0.5 ms, 1 ms, and higher). Lower settings require higher-quality, more consistent network infrastructure (fewer switch hops, managed switches with QoS). Higher latency settings provide more buffering margin for less predictable networks.
Question 4: What is the 'Dante Virtual Soundcard' (DVS) application used for?
- A firmware update utility for Dante-enabled hardware devices
- Software that turns a standard computer's Ethernet port into a Dante audio interface, allowing the computer to receive and send Dante audio channels directly to/from DAW applications (Correct answer)
- A monitoring tool that displays real-time Dante network traffic statistics and clock sync status
- A backup recording system that captures all Dante audio streams to a local hard drive
Correct answer: Software that turns a standard computer's Ethernet port into a Dante audio interface, allowing the computer to receive and send Dante audio channels directly to/from DAW applications
Dante Virtual Soundcard (DVS) is a software audio driver by Audinate that enables any Windows or Mac computer with a standard Ethernet NIC to appear as a Dante device on the network. It presents Dante audio channels as ASIO/Core Audio inputs and outputs to DAWs and recording software without dedicated hardware.
Question 5: What network topology is recommended for large professional Dante installations to ensure redundancy and scalability?
- A ring topology with all devices daisy-chained for minimal cabling
- A star topology with a central managed gigabit switch, and a separate dedicated Dante network isolated from general IT traffic (Correct answer)
- A bus topology using a single CAT6 cable run to all devices in sequence
- A wireless mesh topology using 802.11ac access points throughout the venue
Correct answer: A star topology with a central managed gigabit switch, and a separate dedicated Dante network isolated from general IT traffic
A star topology with a central managed gigabit (or 10G) switch is recommended. Dedicating a separate VLAN or physical switch to Dante audio isolates audio traffic from data traffic, simplifying QoS configuration and reducing interference. Managed switches with IGMP snooping, QoS, and gigabit ports are required.
Question 6: What does 'clock master' selection mean in a Dante network, and what happens if there is no designated master?
- The clock master provides the PTP grand master clock that all other Dante devices synchronize to; if no device is manually designated, PTP elects one automatically using the Best Master Clock Algorithm (BMCA) (Correct answer)
- The clock master is always the device with the most audio channels; other devices cannot function without it
- Without a clock master, all Dante devices revert to free-running internal clocks, causing asynchronous playback
- The clock master must be a hardware GPS clock; software devices cannot serve as Dante clock masters
Correct answer: The clock master provides the PTP grand master clock that all other Dante devices synchronize to; if no device is manually designated, PTP elects one automatically using the Best Master Clock Algorithm (BMCA)
Dante uses PTP's Best Master Clock Algorithm (BMCA) to automatically elect a clock grandmaster if none is manually designated. While automatic election works for simple networks, in complex installations it is best practice to designate a stable device (such as a dedicated clock or a specific console) as the preferred clock master for predictable, consistent synchronization.
What is AES67 and how does it relate to Dante?