From cable to subscription
Instead of dedicating one analogue cable to each channel, a transmitter publishes named audio channels and receivers subscribe to them. Dante Controller is used to view devices, create routes and inspect clock, latency and network status.
Sample rates and encoding must be compatible. Clear device and channel names make commissioning and later service dramatically safer.
Clocking and latency
Dante devices use Precision Time Protocol to align their clocks to an elected leader. Receiver latency allows packets time to traverse the network before playback. If the setting is too low for the topology and traffic, late packets are discarded and audible glitches can result.
Use Controller’s clock and latency monitoring rather than assuming a route is healthy because audio is currently passing.
Switch and topology design
Use switches and configurations appropriate to the channel count and manufacturer requirements. Quality of Service prioritises clock and audio traffic on busy networks. Energy Efficient Ethernet can cause clock instability on unsuitable switches and should be handled according to current Dante guidance.
Primary and secondary Dante ports must not be connected to the same network when devices are in redundant mode. Redundancy duplicates media across two separate paths; it is not a casual daisy-chain feature.
Security, documentation and recovery
Control who can alter routes, record IP strategy and switch configuration, export the controller state, and label every port. Define the fallback if a switch, fibre link or networked amplifier fails. Firmware changes should be planned and tested, not performed casually before an event or client demonstration.
Specification checklist
Before you decide
- Create a channel and device naming standard.
- Confirm sample rate, latency and clock status.
- Use suitable managed network infrastructure.
- Keep redundant networks physically separate.
- Save controller, switch and recovery documentation.
Continue learning