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

• 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

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.