Dante Firmware Bridges ST 2110-30 Without Domain Manager

A quiet but consequential firmware update has been rolling out through the Dante ecosystem in late October: next-generation Dante platforms can now join ST 2110-30 networks in unmanaged mode, with the RTP and PTPv2 parameters configured directly in Dante Controller rather than through Dante Domain Manager. The update notes published by manufacturers building on Audinate silicon list the details that matter to broadcast engineers - configurable PTPv2 domain number, DSCP values, priority settings and sync intervals, an expanded multicast address range covering the full 224.0.0.0 to 239.255.255.255 span for ST 2110-30 flows, and the ability to copy a configuration to multiple devices at once. Support begins on the Dante Ultra generation, starting with Brooklyn 3 followed by IP Core-Zynq, while older Brooklyn II, Broadway and Ultimo devices keep their existing AES67 and ST 2110-30 behaviour.

The significance is architectural rather than incremental. Until now the standard advice for putting Dante devices on a 2110 plant was to run them inside a managed Dante domain or to accept the limitations of unmanaged AES67. Unmanaged ST 2110-30 support moves the interop boundary: a Dante stage box or commentatory unit can now subscribe to linear PCM essence flows at 48 kHz with 44.1 and 96 kHz mapped to the AX, BX and CX conformance levels, sharing a PTPv2 grandmaster with the surrounding 2110 equipment. The dual-clock design stays intact - Dante devices still elect one of their own as a boundary clock and redistribute PTPv1 in a separate domain, which is what keeps the installed base of millions of Dante endpoints synchronised while the plant itself runs broadcast timing.

Three practical consequences follow for anyone planning a mixed plant. First, address planning gets easier but not automatic: with the full multicast range available, engineers can align ST 2110-30 flow addresses with the rest of the plant instead of squeezing into a narrow reserved block, yet IGMP and PTP still have to be documented per switch. Second, the feature split matters at purchase time - Pro-tier platforms such as Pro S1 and the Dante Embedded Platform receive the AES67 enhancements only, and no NMOS registration or connection management is included in the initial release, so a plant that relies on NMOS IS-04 and IS-05 still needs its controller layer. Third, firmware generations now diverge inside one site, and the mix of enhanced, unmanaged-legacy and Pro devices has to be captured in the commissioning document.

For OEM buyers the message is to specify the silicon generation, not just the protocol list. Amtune designs Dante and AES67 audio interfaces and modular Dante audio I/O plus AES67 audio modules for broadcast and install products, and we track which platform generation carries which feature set before recommending a part. When a customer's device has to sit on a 2110 plant next to Dante everywhere else, the module choice determines whether that is a configuration exercise or a gateway project. Platform roadmaps and sample requests at sales@amtune.com.