Dante Controller Presets: Save, Map, Apply, and Roll Back

TL;DR — A Dante Controller preset is an XML file containing selected routing and device-configuration parameters. Save a known-good baseline, choose only the devices and elements you need, then map preset roles to target devices and resolve every reported issue before applying. Because some settings can reboot devices or interrupt media, use a maintenance window, verify audio and clocking after application, and keep the original preset as the rollback point.

A preset is a portable configuration, not a blind restore

Dante Controller presets can capture routing and configuration for some or all devices on a network. They support backup, recurring events, lab-to-production deployment, device replacement, and applying one setting across several devices.

Presets are device-agnostic: saved devices become roles that can be mapped to the original hardware or a different target. That flexibility is useful, but it means an operator must review compatibility instead of assuming that loading a file recreates the network exactly.

Decide what belongs in the preset

A preset can include receive subscriptions, multicast transmit flows, channel names, device names, sample rate, clocking, interface addresses, redundancy, and other supported parameters. The exact set varies by device.

Saving everything is appropriate for a full baseline. A narrow preset is safer for a specific task: for example, apply only sample rate to a selected fleet rather than unintentionally replacing names, addresses, and routes.

Use the Dante device and channel names guide before treating identity fields as disposable configuration.

Save a known-good preset

1. Stabilize the network

Confirm all intended devices are visible, named correctly, clocked, and running the approved routes. Resolve red subscriptions and unexpected warnings first. A preset faithfully saves mistakes as well as good configuration.

2. Record the environment

Document Dante Controller version, device models and firmware, network purpose, show or room, date, and operator. Keep a plain-language inventory next to the XML file so the next engineer knows what it represents.

3. Choose devices and elements

Use Save Preset for a broad snapshot. For a scoped preset, open Advanced, select the required devices, then select only the parameter groups needed for the task. Give the file a semantic name such as venue-a-house-route-2026-10-06.xml, not final.xml.

4. Protect the baseline

Store the XML in controlled production documentation with a checksum or version history. Preset XML can be edited offline, but an edited file should be reviewed and tested as a new artifact rather than silently replacing the known-good baseline.

Apply a preset in four deliberate passes

When loading a preset, Dante Controller presents the application as a sequence: elements, roles, targets, and issues.

1. Select preset elements

Include only the routing or configuration categories required for this change. Excluding unrelated elements reduces the blast radius and makes rollback easier to understand.

2. Map device roles

Automatic mapping may reconnect a role with its originating device. For replacements, touring racks, or a lab-to-production move, manually map each role to the correct target. One role may be applied to multiple devices, but multiple roles cannot be applied to one device.

3. Review target devices

Confirm model, name, firmware, channel capacity, sample-rate support, interface mode, and physical location. A similar name is not enough. Flash or otherwise identify hardware where the device supports it.

4. Resolve issues before applying

Dante Controller reports incompatibilities such as unsupported settings. Treat every issue as a decision: correct the mapping, exclude the parameter, select a compatible target, or document why the warning is acceptable. Do not click through an issue list during a live show.

Expect reboots and media interruption

Some configuration changes can require a device reboot, including changes to redundancy, VLAN configuration, interface addresses, clock pull-up, sample rate, and RTP mode on supported products. Routing and multicast changes can also affect downstream receivers.

Schedule preset application before doors or in a maintenance window. Keep local access to critical equipment and know which settings may remove the computer from the network.

Validate and roll back

1. Save a fresh pre-change preset.
2. Capture current routes, clock leader, link state, and error baseline.
3. Apply only the approved elements and roles.
4. Wait for required reboots and rediscovery.
5. Verify device identity, sample rate, clock, subscriptions, multicast, and latency.
6. Pass audio through every required destination.
7. Exercise the approved redundancy or link-failure test.
8. If acceptance fails, restore the pre-change preset or the documented manual rollback, then retest.

The Dante network health guide provides the evidence to compare before and after a change.

Use narrow presets for global configuration

A preset can apply one selected parameter to many targets. Configure a representative device, save only the relevant element, load the preset, assign that role to the intended targets, and review issues before applying. This is safer than a full-network preset when the goal is only a shared sample rate or another supported setting.

Do not use global application to erase legitimate device differences. Confirm that every target supports the value and that the change belongs in the approved network design.

Preset checklist

• The network is healthy before the preset is saved.
• Controller version, firmware, purpose, date, and owner are recorded.
• Devices and preset elements match the actual change scope.
• Every role is mapped to a physically confirmed target.
• All compatibility issues are resolved or documented.
• Reboots and media interruptions have a change window.
• Pre-change and post-change routes, clock, and health are compared.
• Audio, failure recovery, rollback, and ownership are tested.

FAQ

What does a Dante Controller preset save?

It can save selected routing and device-configuration parameters for chosen devices. Supported elements depend on each device, so inspect the preset selection rather than assuming it contains everything.

How do I save a preset in Dante Controller?

Start from a verified network, select Save Preset, and use Advanced when you need specific devices or parameter groups. Save the XML with clear context and version ownership.

Can a Dante preset be used with different devices?

Yes. Presets store portable device roles that can map to other targets. Dante Controller reports compatibility issues, which must be reviewed before applying.

Can I apply only part of a Dante preset?

Yes. Select only the required preset elements and device roles. A narrow application is often safer than restoring unrelated names, addresses, clock settings, and routes.

Do Dante presets require devices to reboot?

Some applied settings can require a reboot, including certain redundancy, network-interface, sample-rate, clock, VLAN, and RTP-mode changes. Plan a controlled window and verify rediscovery and audio afterward.

Make repeatability part of the rider

A preset file answers how to reproduce a state; the rider should explain when, where, and by whom it may be applied. Keep the approved preset name, scope, target map, change window, rollback, and validation record in Techrider.live so collaborators can edit, save, and inspect history from the same maintained handoff.