Skip to main content

DDM Release Notes

Updated

Below you can find release notes for current and previous versions of Dante Domain Manager:

DDM v1.8.1.13113 Release

Release Date: 1/7/2025

Dante Domain Manager (DDM) 1.8.1 is a patch release that delivers several improvements.

  • Log retention is now capped at 30 days - balancing traceability with disk space usage efficiencies
  • Simplification of logged latency and clocking warnings
  • Improved robustness with Dante Via

Note: DDM 1.8.x will be the last version with support for pre-v4.x firmware [legacy] devices. Notice of this is provided on the Domain Details page.

DDM 1.8.x is provided on a Rocky 9 platform.

Important: DDM installations at version 1.5 or earlier cannot be updated to v1.8 via the online update feature in the DDM user interface. For installation instructions, please see Upgrading DDM from v1.5.x or Earlier - Installation Guide.

What's New:
New features since v1.8.0:

  • Log retention is now capped at 30 days - balancing traceability with disk space usage efficiencies
  • Simplification of logged latency and clocking warnings
  • Improved robustness with Dante Via

See the DDM user guide for more information about DDM features.

See the Managed API User Guide for more information about the API.

Hosting of Dante Domain Manager in AWS was introduced in DDM v1.7.x. See the Deployment Guide for AWS for more information about AWS hosting of DDM.

Notes:
See Dante Domain Manager Support for documentation and other resources.

Bug Fixes:

  • DDM-1011: Dante Via TX channels cannot be resolved when Via is enrolled in DDM
  • DDM-1017: Pre-emptive clocking and latency warnings are raising customer concerns too early
  • DDM-1020: Audit log entries from device configuration messages with invalid utf-8 strings are written to the database
  • DDM-1022: Log retention of 90 days too long and may lead to insufficient disk space

Known Issues:
Pre-existing known issues

  • DDM-811: After installation or disbanding a HA cluster the network interface may be disabled. Workaround: Configure the network interface on the appliance menu to be static or dynamic, then reboot the appliance.
  • DDM-430: Selecting a different number of records to show in the audit log fails. The second attempt at selecting a different number of records to show will succeed.
  • DDM-432: The branding feature is available only when the Main node is active. It is not available for the backup (auxiliary) node. The branding feature will be restored once the Main node is again active.
  • DDM-428 / DDM-429: Long API key descriptions may overlap with other page elements. Workaround: Restrict the API key description to approx. 35 characters, inc. spaces.
  • MIL-4635: High latency settings for a device, that are only available with Dante Domain Manager, remain when the device is unenrolled. Workaround: Manually change the latency to one that is better suited for local unmanaged network operation.
  • DDM-977: After High Availability failover, Dante Controller is unable to connect to the new active node. Workaround: The new node takes a few minutes to fully establish. You may need to wait for the connection between Domain Manager and Dante Controller to timeout (~5 minutes); then it should connect successfully.

 

DDM v1.8.0.12081 Release

Release Date: 2/4/2025

Dante Domain Manager (DDM) 1.8 is a maintenance release that delivers a range of improvements:

  • High priority security updates
  • Hypervisor support extended to Proxmox
  • Support for LDAP private certificates
  • Additions to GraphQL API: Device Rename & Domain Add, Remove, and Rename
  • Improved diagnostic tools for customer support

Note: DDM 1.8 will be the last version with support for pre-v4.x firmware [legacy] devices. Notice of this is provided on the Domain Details page.

DDM 1.8 is provided on a Rocky 9 platform.

Important: DDM installations at version 1.5 or earlier cannot be updated to v1.8 via the online update feature in the DDM user interface. For installation instructions, please see Upgrading DDM from v1.5.x or Earlier - Installation Guide.

What's New:
New features since v1.7:

  • High priority security updates
  • Hypervisor support extended to Proxmox
  • Support for LDAP private certificates
  • Additions to GraphQL API: Device rename, Domain rename

See the DDM user guide for more information about new DDM features.

Hosting of Dante Domain Manager in AWS was introduced in DDM v1.7.x. See the Deployment Guide for AWS for more information about AWS hosting of DDM.

See the Managed API User Guide for more information about the API.

Notes: See Dante Domain Manager Support for documentation and other resources.

Bug Fixes:

  • DDM-736 / ETS-4578: Licensing issues may not be fully logged
  • DDM-758:Devices may show 'offline' when switching between High Availability nodes
  • DDM-779: Cloud installations are not able to update via the UI due to SSH keys removal
  • DDM-894 / ETS-4962 / ETS-5183: Devices that use peer group functionality are not supported in DDM 1.7
  • DDM-896 / ETS-5012: In edge cases some domains cannot be deleted
  • DDM-901 / ETS-5474: The pending static enrolment status is not fully explained
  • DDM-902 / ETS-5044: DDM 1.7 is connecting to public CentOS NTP servers
  • DDM-907 / ETS-5077: DDM is unable to support more than 196 domains
  • DDM-925 / ETS-5275: After High Availability failover devices are offline in DDM but online in Dante Controller
  • DDM-929 / ETS-5075 / ETS-5176: The LDAP timeout of 2 seconds may be too restrictive for complex networks
  • DDM-952 / ETS-5275: Logging of initial device connection state incorrectly indicates an error
  • DDM-953 / ETS-5298: There are no details of how high latency is for latency too high warnings
  • DDM-965: Frequent logging for metering and access control messages causes excessively large logs
  • DDM-976 / ETS-5554: Invalid manufacturer UTF-8 characters may cause system crash
  • DDM-978 / ETS-5310 / ETS-5550: Sharing media between domains for high channel count devices can cause devices to go offline and/or the connection with Dante Controller to fail

Known Issues:
Pre-existing known issues

  • DDM-811: After installation or disbanding a HA cluster the network interface may be disabled. Workaround: Configure the network interface on the appliance menu to be static or dynamic, then reboot the appliance.
  • CLOUD-1303: Legacy devices cannot be configured via the GraphQL API. Workaround: Continue to configure legacy devices via Dante Controller.
  • DDM-430: Selecting a different number of records to show in the audit log fails. The second attempt at selecting a different number of records to show will succeed.
  • DDM-432: The branding feature is available only when the Main node is active. It is not available for the backup (auxiliary) node. The branding feature will be restored once the Main node is again active.
  • DDM-428 / DDM-429: Long API key descriptions may overlap with other page elements. Workaround: Restrict the API key description to approx. 35 characters, inc. spaces.
  • MIL-4635: High latency settings for a device, that are only available with Dante Domain Manager, remain when the device is unenrolled. Workaround: Manually change the latency to one that is better suited for local unmanaged network operation.
  • MIL-5452: Enrolled legacy devices cannot be configured for preferred leader, external word clock or unicast delay using Dante Controller. Workaround: A pre v4.x Dante firmware device does not have the necessary communications to permit this. Please select another device as the preferred leader.
  • DDM-977: After High Availability failover, Dante Controller is unable to connect to the new active node. Workaround: The new node takes a few minutes to fully establish. You may need to wait for the connection between Domain Manager and Dante Controller to timeout (~5 minutes); then it should connect successfully.

 

DDM v1.7.1.6083 Release

Release Date: 27/2/2024

DDM 1.7 is provided on a Rocky 9 platform, and OpenSSL has been updated to v3.0.

Bug Fixes: 

  • ETS-4041: DMM browser login expires earlier than the timeout value
    Known Issues:

New known issues

  • DDM-811: After installation or disbanding a HA cluster the network interface may be disabled. Workaround: Configure the network interface on the appliance menu to be static or dynamic, then reboot the appliance.
  • CLOUD-1303: Legacy devices cannot be configured via the GraphQL API. Workaround: Continue to configure legacy devices via Dante Controller.
  • ETS-5183: Customers using RTS ODIN or QSC Core devices with failover to redundant sister devices are not fully supported in DDM 1,7. Workaround: Continue to use DDM 1.5. Scheduled for fix in DDM 1.8.
  • ETS-5077: Exceeding 196 domains causes domain manager service failure. Workaround: Do not exceed 195 domains. Scheduled for fix in DDM 1.8.
  • ETS-5157: Changing the OU (Organisation Unit) for a user block login via LDAP. Workaround: Click FORGET USER for affected users
  • ETS-5044: Default NTP servers are communicating with CentOS servers, despite the migration to Rocky. Scheduled for fix in DDM 1.8.
  • ETS-5012: under certain circumstances a domain can get into a state where it is not possible to delete it. Scheduled for fix in DDM 1.8.

Pre-existing known issues (from DDM 1.5)

  • DDM-430: Selecting a different number of records to show in the audit log fails. The second attempt at selecting a different number of records to show will succeed.
  • DDM-432: The branding feature is available only when the Main node is active. It is not available for the backup (auxiliary) node. The branding feature will be restored once the Main node is again active.
  • DDM-428 / DDM-429: Long API key descriptions may overlap with other page elements. Workaround: Restrict the API key description to approx. 35 characters, inc. spaces.
  • MIL-4635: High latency settings for a device, that are only available with Dante Domain Manager, remain when the device is unenrolled. Workaround: Manually change the latency to one that is better suited for local unmanaged network operation.
  • MIL-5452: Enrolled legacy devices cannot be configured for preferred leader, external word clock or unicast delay using Dante Controller. Workaround: A pre v4.x Dante firmware device does not have the necessary communications to permit this. Please select another device as the preferred leader.

 

DDM V1.5.0.2 Release

Release Date: 12/4/2023

Dante Domain Manager 1.5 brings a critical new set of capabilities to Dante networks in the form of the Dante Managed API. The Dante Managed API provides simple programmatic control and reporting of managed Dante networks for use with touch panels, monitoring, automation and support tools.With the Dante Managed API, channel subscriptions can be monitored and changed from third-party systems, and devices can be brought into and out of Dante Domains as part of a workflow design. Third-party monitoring systems can query Dante Domains and devices for status and support needs, enabling complete integration with other products.New features since v1.4.x

  • Dante Managed API

See the DDM user guide for more information about new features.Bug Fixes

  • N/A (feature release only)

New Known Issues

  • DDM-430: Audit log pagination change fails on first attempt
  • DDM-432: The custom branding feature is only available on the main DDM node
  • DDM-428: Long API key descriptions may overlap with other page elements

Pre-existing Known Issues (from DDM 1.4.x)

  • MIL-4635: High latency settings are not cleared when leaving a domain without clearing config
  • MIL-5452: Enrolled legacy devices cannot be configured for preferred leader, external word clock or unicast delay using Dante Controller

 

 

DDM V1.4.1.1 Release

Release Date: 6/12/2022

Dante Domain Manager v1.4 is a recommended update., with numerous security improvements, updates to core components, management of security updates for the DDM package OS and support for Dante AV devices.New features since v1.3:

  • Support for Dante AV
  • Improved security for audit log tables
  • Improved username authentication mechanisms
  • Improved password authentication mechanisms
  • Improved SSH authentication mechanisms
  • Upgrade to Meteor 2.7.2
  • Upgrade to MongoDB 4.4.15
  • Operating system security updates management (Administration Menu)
  • Dashboard alert when Operating System updates are available
  • A reminder to back up DDM before updating
  • Configuration backups can be downloaded from the Administration Menu
  • Feature to prevent Windows update causing offline devices in Hyper-V
  • Launch Dante Controller from the Domain page

Bug Fixes: 

  • CS-18: Source IP in Audit Logs of Dante Controller is incorrectly logged as 127.0.0.1
  • CS-221 / ETS-3178: DDM may hang when an encrypted private key is uploaded
  • CS-336: Username and Name column headers in LDAP test query are reversed
  • CS-518 / ETS-2978: DDM device manager segmentation fault can cause issues with Dante Controller connection
  • CS-529 / ETS-3211: LDAP users do not get dashboard alerts
  • CS-594: 'Allow unknown message' feature is not available (DDM has an explicit allow list, and new to market products may be blocked)
  • CS-629: Custom role configuration can cause incorrect availability of device enrol button
  • CS-746: Hyperlink in DDM UI to User Guide (Network Security) pointing incorrectly

New known issues

  • None

Pre-existing known issues (from DDM 1.3.2)

  • MIL-4635: High latency settings are not cleared when leaving a domain without clearing config
  • MIL-5452: Enrolled legacy devices cannot be configured for preferred leader, external word clock or unicast delay using Dante Controller

 

 

DDM V1.3.2.1 Release

Release Date: 24/3/2022

V1.3.2.1 is a maintenance release of the Dante Domain Manager.New Features and Improvements in 1.3

  • CS-152 - Users can now log in using their email address (as well as their username).
  • CS-106 - Update to nginx 1.20.1
  • CS-73 - Administrators can now generate DDM core logs, if requested by Audinate Technical Support, to help in fault diagnosis.
  • CS-91 - DDM now supports a pass-through mode between Dante devices or controllers, allowing custom messages created by manufacturers of Dante-enabled products to pass. By default this is off.

Resolved Issues in 1.3.2.1

  • ETS-3246 - Log file format conversion exception during boot sequence could cause Device Manager Service to fail

Resolved Issues in 1.3.1.7

  • CS-101 - Restore configuration from backup may fail when the audit log is large
  • CS-102 - Whilst running, network diagnostics can cause the DDM to become unresponsive
  • CS-103 - Open VM tools has issues with NTP leading to instability
  • CS-119 - Shared audio Tx channel configuration update from "all domains" to "selected domains" may fail
  • CS-124 - Valid device subscriptions can become unresolved
  • CS-125 - Excessive logging of failovers in audit log
  • CS-131 - Hostnames cannot be used for SNMP endpoint
  • CS-141 - Peer Group ID failover incorrectly logged
  • CS-148 - Clocking issues when devices are powered on before DDM
  • CS-152 - LDAP test query returns "missing" for the name attribute
  • CS-155 - SNMP process has memory leak
  • CS-157 - Devices with control features lose access control during migration from pre 1.2.2 configurations
  • CS-4 - DDM device manager service can crash under certain circumstances
  • CS-51 / MIL-5707 - AES67 is disabled during device enrolment (creating AES67 flows after enrolling a device with v4.2 firmware into an AES67 domain fails)
  • CS-67 - Dante interface may be incorrectly identified as invalid

Known issues

  • MIL-4635 - High latency settings are not cleared when leaving a domain without clearing config
  • MIL-5452 - Enrolled legacy devices cannot be configured for preferred leader, external word clock or unicast delay using Dante Controller

 

 

DDM V1.2.2.1 Release for Linux

Release Date: 14/9/2021

V1.2.2.1 is a maintenance release of the Dante Domain Manager.New Features and Improvements in 1.2

  • KAS-339 - DDM can be licensed or updated via a proxy server
  • NIMBUS-594 - Upgrade appliance to CentOS 7.2009 (Fresh installs only)
  • NIMBUS-815 - Security fixes for Nginx 3rd party component
  • NIMBUS-647 - Updates for Meteor 3rd party component
  • NIMBUS-558 - Updates to other system packages
  • NIMBUS-590 - Shared virtual audio devices now support multicast flows
  • NIMBUS-621 - Allow pasting of TLS certificate and private key in the UI
  • NIMBUS-622 - Custom user roles can be created
  • NIMBUS-674 - License Server and Update Server connectivity tests now test HTTPS, in addition to ping
  • NIMBUS-720 - Downloading logs now includes the appliance system logs (/var/log/messages)
  • NIMBUS-728 - The Appliance menu provides an emergency "Exit HA Cluster" option
  • NIMBUS-731 - Improved logging and tracing for device manager, to aid support and diagnosis
  • NIMBUS-768 - Audit log entries are now displayed to the second

Fixed issues since v1.2.1

  • CS-44 - Modifying shared channels for devices shared between domains fails after adding an additional domain to the shared media group.

Fixed issues since v1.2.0

  • NIMBUS-949 - Updating / Restoring a configuration could have issues if configured for LDAP

Fixed issues since v1.1.1

  • MIL-5727 - Devices still attempt to connect to devices with unicast clocking after the other device is removed from a domain
  • MIL-5723 - LDAP / Local User tabs on user page not working in Internet Explorer
  • MIL-5720 - open-vm-tools was uninstalled whenever the additional packages menu is opened in the appliance menu
  • MIL-5715 - The display name of a logged-in LDAP user is incorrect when a personalization option is modified
  • MIL-5494 - Domain selection is lost in the enrollment wizard when a device goes offline
  • KAS-364 - Restarting during initial setup could make the user interface unavailable
  • NIMBUS-559 - Clearing the Audit Log can cause it to grow indefinitely
  • NIMBUS-541 - Device Manager service fails repeatedly with non-existent network interface
  • NIMBUS-918 - Software update fails on a redundant only node after disbanding a High Availability cluster

Known issues

  • MIL-4635 - High latency settings are not cleared when leaving a domain without clearing config
  • MIL-5452 - Enrolled legacy devices cannot be configured for preferred master, external word clock or unicast delay using Dante Controller
  • MIL-5707 - Creating AES67 flows after enrolling a device with v4.2 firmware into an AES67 domain fails. Workaround: disable and enable AES67 on the device, or reboot

 

Related to

Related articles