Cart

Dante Connect

Release Date: 28th of July 2025

Welcome to the release page for Dante Connect, which introduces the benefits of Dante to cloud-based applications and workflows, and is designed specifically with Tier 1 Broadcasters in mind. Dante Connect seamlessly combines the robust capabilities of Dante Domain Manager with cloud-based production applications, providing you with a streamlined workflow. With Dante Connect, you can effortlessly manage and utilize concurrent licenses for Dante Virtual Soundcard and Dante Gateway, ensuring smooth integration and improved efficiency.

Your reseller will provide a DDM license, and information about instantiating DDM virtual machines in your cloud environment (currently supporting AWS and GCP). The AMI includes configurable Terraform scripts that will install and activate the other Dante Connect components.

Refer to the Dante Connect Deployment and Configuration Guide (link below) for more information.

The Dante Connect solution includes multiple components. Some component versions listed here are currently only available as part of the Dante Connect solution.

Dante Domain Manager

The GA version of DDM includes full support for Dante Connect. For downloads and additional resources, see getdante.com/product-support/dante-domain-manager/.

Dante Virtual Soundcard for Cloud VMs

DVS allows lossless synchronized audio to be transferred between cloud VMs, and connects audio channels to applications. You’ll need DVS v4.4 installed on each virtual machine in your cloud solution. You can install as many as you like – however, only those that have been activated will pass audio.

The latest GA release of DVS now supports Dante Connect.

Dante Gateway

Dante Gateway provides cloud clocking, and enables a low-latency local network or cloud region to work seamlessly with higher latency connections.

Dante Gateway supports 64 or 256 channels.

On-Premise Installation

For local deployments, download the Dante Gateway binary from:

Cloud Installation

For cloud-based deployments, Dante Gateway offers a streamlined installation process using Terraform.

  1. Ensure you have Terraform installed and configured for your cloud provider.
  2. Download the AWS Dante Gateway Terraform script from:
    https://github.com/audinate/terraform-aws-dante-connect
    or the GCP Dante Gateway Terraform script from:
    http://github.com/audinate/terraform-gcp-dante-connect

Dante Remote Monitor

Remote Monitor for Dante Connect is a web-based application that allows you to remotely monitor up to 32 channels of audio simultaneously from a Dante network running in the cloud. Remote Monitor can subscribe to Dante Virtual Soundcard (DVS) or Dante Gateway channels.

Refer to the User Guide (in Documentation) for information about using Remote Monitor.

Refer to the Dante Connect Deployment and Configuration Guide for installation instructions.

Download the Remote Monitor Debian installer from:

Download (right click > save as) the installation helper script from:

Dante Remote Contributor

Remote Contributor for Dante Connect is a web-based application that allows you to remotely contribute and monitor up to 16 channels of audio simultaneously from a Dante network running in the cloud.

Remote Contributor can be subscribed to by Dante Connect products in the cloud, such as DVS.

Refer to the User Guide (in Documentation) for information about using Remote Contributor.

Refer to the Dante Connect Deployment and Configuration Guide for installation instructions.

Download the Remote Contributor Debian installer from:

Download (right click > save as) the installation helper script from:

Dante Domain Manager v1.8.1

New Features

  • 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

Resolved Issues

Existing Known Issues (from DDM v1.7)

  • 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.

Dante Virtual Soundcard v4.5.0

Dante Gateway 1.1.1

Resolved Issues

  • DS-1583: Subscriptions would be lost when restarting Dante Gateway
  • DCO-108: Dante Gateway would revert to the default latency when the instance was restarted

Known Issues

  • DCO-48: Bulk Subscriptions might fail when using Dante Gateway 256ch. Workaround: Restart Gateway using systemctl restart dante-gateway

Dante Remote Monitor 1.0.1

New Features

  • Remote Monitor now supports Google Cloud Platform (GCP)
  • Remote Monitor Installation Helper script now supports generation of a self-signed certificate on installation

Resolved Issues 

  • DCO-117: On certain browsers, WebRTC sessions would randomly fail a few minutes after starting
  • DCO-123: Resolved a crash which would occasionally happen when starting or stopping Remote Monitor client
  • DCO-150: Security updates
  • DCO-108: Dante Gateway would revert to the default latency when the instance was restarted in GCP

Known Issues 

  • DCO-145: Firefox does not list all the audio devices available on the PC, and can sometimes lose all audio devices. Workaround: Chrome and Microsoft Edge are the recommended browsers for Remote Monitor.
  • DCO-127: When trying to connect too many channels at once, some WebRTC sessions may fail on certain browsers. Workaround: Restart the Remote Monitor client. If the issue persists after multiple attempts, use fewer channels. It is important to profile for your use case to determine an appropriate number of channels.
  • DCO-125: Sometimes when stopping the Remote Contributor client, connections do not get cleaned up successfully. In this case, the Start button will not become available for some time and the status will stay “Busy”. The connections will also be visible on the server “Deploy” page. Workaround: Refresh the Remote Monitor client web page, and the connections should be cleaned up quickly.
  • DCO-79: After an administrator’s login session expires, when the user tries to edit the configuration, they will be logged out. After logging back in, they are presented with an error message stating they do not have sufficient permissions. Workaround: This error message is spurious. No action necessary.
  • DCO-88: Remote Monitor configuration can be changed while the client is monitoring audio. This will break audio if the associated channel was in use at the time. Workaround: Do not edit the Remote Monitor configuration while it is in use.
  • DCO-72: If four or more channels are playing audio simultaneously, some web clients will have audio distortion when mixing the WebRTC streams. Workaround: Mix audio before sending the audio to the Remote Monitor.
  • DCO-76: Performance of Remote Monitor Client on mobile phones might be affected if you enable more than 10 channels simultaneously. Workaround: Works well with Chrome browser on PCs and Desktops.
  • DCO-87: The WebRTC playout will occasionally become distorted. Workaround: Refresh the webpage or use another browser.

Dante Remote Contributor 1.0.0

Resolved Issues 

  • N/A

Known Issues 

  • DCO-145: Firefox does not list all the audio devices available on the PC and can sometimes lose all audio devices. Workaround: Chrome and Microsoft Edge are the recommended browsers for Remote Contributor.
  • DCO-127: When trying to connect too many channels at once, some WebRTC sessions may fail on certain browsers. Workaround: Restart the Remote Contributor client. If the issue persists after multiple attempts, use fewer channels. It is important to profile for your use case to determine an appropriate number of channels.
  • DCO-125: Sometimes when stopping the Remote Contributor client, connections do not get cleaned up successfully. In this case, the Start button will not become available for some time and the status will stay “Busy”. The connections will also be visible on the server “Deploy” page. Workaround: Refresh the Remote Contributor client webpage, and the connections should be cleaned up quickly.
  • DCO-79: After an administrator’s login session expires, when the user tries to edit the configuration, they will be logged out. After logging back in, they are presented with an error message stating they do not have sufficient permissions. Workaround: This error message is spurious. No action is necessary.
  • DCO-118: When contributing audio to multiple channels simultaneously, the audio in the Dante channels may be several milliseconds out of sync with each other. Workaround: If multiple Dante devices simultaneously need contributed audio, they should subscribe to the same Dante channel.
  • DCO-88: Remote Contributor configuration can be changed while the client is contributing or monitoring audio. This will break audio if the associated channel was in use at the time. Workaround: Do not edit the Remote Contributor configuration while it is in use.
  • DCO-72: If four or more channels are playing audio simultaneously, some web clients will have audio distortion when mixing the WebRTC streams. Workaround: Mix audio before sending the audio to Remote Contributor.
  • DCO-76: Performance of the Remote Contributor Client on mobile phones might be affected if you enable more than 10 channels simultaneously. Workaround: Works well with Chrome browser on PCs and Desktops.
  • DCO-87: The WebRTC playout will occasionally become distorted. Workaround: Refresh the webpage or use another browser.

Audinate’s Support for Inclusive Language

To our customers: some of the terminology used in Dante products has been changed to align with modern usage. Specifically, areas related to Dante clocking now refer to “Primary Leader Clock”, “Leader Clocks” and “Follower Clocks” to describe the functions of each role more clearly.