Print This Page

Audinate Dante Firmware Version History

Important Notice

Please download the latest version.


New Feature

  • Now supports HA Remote control bridging through Dante network.


This release fixes following issues.

  • Multiple clock masters appearing in the Dante Controller
    Under certain Dante network scenarios, if the Dante-MY16-AUD was disconnected and reconnected to the network many times it was possible to see more than one Dante clock master in the Dante Controller.
  • Host Yamaha equipment displays Word Clock error if Dante network disconnected
    If the host Yamaha equipment was slaved to the Dante-MY16-AUD clock and the Dante network was disconnected, the host device would not be able to sync.
  • Dante-MY16-AUD does not subscribe to Lake LM26 multicast flows
    There was a problem that prevented the Dante-MY16-AUD from subscribing to multicast flows from the Lab.gruppen Lake LM26.
  • A Dante-MY16-AUD clock slaved to a Brooklyn II clock master would exhibit LRCLK phase shift
    If the Dante-MY16-AUD was slaved to Brooklyn II-based audio equipment running as Dante clock master, under certain conditions the Dante-MY16-AUD WCLOCK output was being delayed by about 0.2 to 1.0 ╬╝secs.
  • Audio issues when Dante-MY16-AUD network cables are rapidly disconnected and reconnected
    Repeated rapid disconnection and reconnection of Dante-MY16-AUD network cables would sometimes mean that audio flows would take an excessive amount of time to restart, or in some circumstances could completely fail to restart.
  • Missing interface IP addresses on device reboot
    An intermittent condition could prevent the Dante-MY16-AUD on reboot from acquiring an IP address for one of its network interfaces, or could interrupt the audio flows on the network.
  • Preferred master takes over immediately if it's reset
    When a preferred master clock device was newly reconnected to a network, it would immediately take over clocking (without syncing to the active clock master), which could cause a timing error.
  • Saving device configuration to Flash memory takes too long
    Changes in Dante Controller to audio network routing (subscriptions, flows, channel labels) and some device settings (sample rate, channel encoding, latency) were taking up to 17s to be saved to the device's onboard Flash memory, risking changes being lost if the device was powered down. These changes are now saved in under 3s.
  • Dante-MY16-AUD loses segments of audio on secondary network if primary is disconnected
    With audio running on the secondary network only (i.e. when the primary network is fully disconnected), audio on the secondary network would drop out for several seconds about every 5 minutes.



  • his version of Dante firmware is exclusive use for the Dante-MY16-AUD card. Never install this version to the other products.
  • If this version should be installed to the CL5, CL3, CL1, Rio3224-D, or Rio1608-D, it will result in malfunction of the Dante module.


This release fixes following issues.

  • Yamaha DME "Slot <n> Sync Error" error message: Under certain conditions, this error message would be displayed on a DME with a Dante-MY16-AUD card installed.
  • Dante Rx audio channel labels not restored after power cycle: Dante receive (Rx) audio channels that had been renamed would revert back to default names after power cycling the Yamaha equipment.
  • Dante Controller subscription status on sample rate change: After changing the sample rate on a device with active audio subscriptions, the Dante Controller subscription status icon would show "waiting" instead of correctly failing due to incompatible sample rates.
  • Setting and removing multiple PTP Preferred Master Clocks: If two Dante devices had "PTP Preferred" selected, and the one that was Master then had this setting cleared, the second device would not always automatically take over.
  • Introducing a new PTP Preferred Master device: If a stable Dante network with no PTP Preferred Master set had a new device introduced which was already configured as PTP Preferred Master, it could sometimes disrupt network time as it took over as Master Clock.
  • Very occasional Dante sync error: If the primary and secondary interfaces were rapidly and repeatedly plugged and unplugged, forcing rapid Master clock changes on the network, Dante sync could stop working on a device which would then need to be rebooted.
  • Dante Controller Master Clock display: When the Dante Master Clock changed on the Dante network, the Dante-MY16-AUD card would report unnecessary intermediate states leading the Dante Controller to confusingly display a number of Master Clock transitions.
  • SYNC LED behavior: SYNC LED now unlit if no cable is connected.

Return to Top