Filter by Topic
  • Analog IFB
  • Analog Intercom
  • Dante
  • Dante Clocking
  • Firmware Updates
  • Live-Link
  • Model 208
  • Model 380
  • Model 391
  • Model 48D
  • Model 5401
  • Model 5422
  • Models 214/215/216
  • ST 2110


14-Nov-2018 Dante Firmware Updates

Dante Ultimo Subscription Issue Corrected!

 

 

In a previous Tech Note (https://studio-tech.com/tech-notes/problem-with-dante-subscriptions-re-establishing/) an issue was described that impacted certain of our Dante products. In some cases Dante subscriptions (“routes”) would not re-establish upon a power cycle or when disconnecting and reconnecting to the Ethernet network. Over the past several months some of our customers have experienced this issue and we simply couldn’t offer a good solution. It was stressful for everyone involved and sometimes lead to less-than-optimal operation. But that changed as of yesterday when Audinate released a new version (4.1.4.2) of their Ultimo firmware.

Applicable to their Ultimo X2 and Ultimo X4 integrated circuits, this firmware corrects the issue of Dante subscriptions not always re-establishing correctly. Our initial testing of the new firmware confirms that it does resolve the issue. As a Dante licensee, Studio Technologies starts with the Audinate-provided firmware (in this case 4.1.4.2) and generates specific .dnt files for each of our Dante-supporting products. We have created 23 .dnt files for our various products and they are now available for download on our website. We have also submitted these files to Audinate’s database in preparation for the release of a new version of the Dante Controller software application. This forthcoming version will provide a streamlined method of updating Dante firmware.

Updating the Dante firmware in all Studio Technologies products to the latest is highly recommended! It’s simple and can be performed by way of each unit’s Ethernet interface. Details are provided in the user guide of all products. Contact technical support should additional details be required.

Hopefully we can now say “case closed” on this issue!

 

Menu