Dante Module Firmware Decides How a Device Boots

Audinate published two updates to the Dante Module Configuration Tool in the space of a week. Version 2.12.0.2, built on 4 November, carries a Dante Pro S1 firmware update to v4.2.27.3, firmware updates for the DIO AES3 and DIO BT interfaces, and a new capability described as an enable pulse on SAI missed interrupt for Pro S1. The version before it, 2.11.0.1 on 30 October, moved Brooklyn 3 to firmware v4.3.3.5 and added an unmute-on-boot-without-network option for the same module. Earlier releases in the same series added a validation rule that prevents identical multicast and unicast port numbers, and fixed a user partition upload fault and an OEM filter bug.

The unmute line looks administrative and is not. A Dante endpoint normally comes up muted until a controller establishes a subscription, which is the correct behaviour on a shared network: nothing makes noise until someone asks it to. But a stand-alone device - a paging amplifier in a plant room, a powered speaker at a bar, a monitor feed in a booth - has no controller and therefore stays silent forever, which generates a support ticket that reads like a hardware failure. Unmuting on boot without a network solves that case and creates the opposite risk: in a room where the DSP applies gain, delay and EQ after power-up, a device that passes audio before the processor is ready can deliver full-scale signal to the amplifiers. The right answer differs per product, and it has to be written in the manual rather than discovered.

The SAI reference is the serial audio interface between the module and the host processor or converter - the I2S or TDM bus where the samples actually travel. A missed interrupt there means a channel that stops updating while the network side still looks healthy, which is one of the hardest faults to diagnose on site because every dashboard says the stream is fine. The enable-pulse capability gives the host a defined response rather than a stuck channel. An OEM validating a new board should deliberately disturb the audio clock - hot-plug the converter, change sample rate mid-stream, hold the reset line - and confirm what the module does, because the field will eventually do all three.

The port validation rule is the quiet one. Identical multicast and unicast port numbers on the same module is a classic self-inflicted network fault: the device appears online, subscribes, and then behaves unpredictably as traffic is delivered to the wrong socket. Rejecting the configuration at the point of entry removes a whole class of commissioning calls. For anyone buying an embedded module rather than a finished box, the practical request is the firmware branch and its release-note history, not just the chip name. Amtune publishes the Dante audio module and AES67 audio module firmware baseline with each product, including the default boot state, so the integrator knows whether the device opens muted or live before it is installed.