Dante Factory Reset vs Clear Config: Recover a Device Safely

TL;DR — Factory Reset is a destructive recovery action that can erase Dante names, channel labels, clock settings, static addresses, redundancy mode, sample rate, latency, and routes. Supported devices may offer Clear Config, which clears the same configuration while optionally retaining IP and redundancy settings. Export the baseline first, use the narrowest action, reboot as required, rebuild deliberately, and pass full route, clock, network, and audio acceptance before service.

Know the reset boundary

A Dante interface stores configuration that other routes and crews depend on. Resetting it is not a generic troubleshooting refresh. It changes routing identity and may remove the exact evidence needed to diagnose the original failure.

Exact availability and host-device behavior vary by product. Read the manufacturer's current documentation before acting, especially when the Dante interface is embedded in a console, processor, amplifier, or stage box.

What can be erased

Audinate's Controller guidance lists user device and channel names, clock configuration, static IP addresses, redundancy configuration, sample rate including pull-up or down, latency, and existing audio routes among the settings cleared by Factory Reset. Clear Config targets the same set but may let you keep IP and redundancy settings.

That means a reset can simultaneously change discovery, identity, clock domain, media compatibility, network mode, and every subscription. It should not be the first response to one failed route or a sample-rate mismatch.

Use the subscription errors guide for a route-specific fault and the sample-rate mismatch guide for format recovery.

Choose the narrowest recovery action

Reboot when state is temporary and configuration is trusted

Use a controlled reboot only after saving events and confirming that a restart is an approved vendor action. Observe whether the containing product also needs a power cycle or host restart. A reboot that temporarily hides an intermittent fault is not a repair.

Use Clear Config when supported and retention is intentional

Clear Config is useful when the configuration must be rebuilt but retaining network reachability and redundancy mode reduces recovery risk. Select the retention option only when the existing IP and redundancy settings are known correct. Keeping a bad static address or wrong port mode preserves the fault.

Use Factory Reset for a full known-state rebuild

Choose Factory Reset when product guidance or controlled recovery requires all Dante settings to return to defaults. Plan for rediscovery, renaming, network configuration, clock and format settings, route recreation, and a complete acceptance test.

Prepare before clearing anything

1. Record the incident, event time, symptoms, and last known-good state.
2. Save or export a reviewed Dante Controller preset where appropriate.
3. Capture device and channel names, subscriptions, sample rate, latency, clock settings, IP addresses, redundancy mode, firmware, and physical switch ports.
4. Identify who owns the device, network, routes, and downstream audio acceptance.
5. Confirm an access path after reset, including the expected default addressing behavior.
6. Define the rollback or replacement plan if the device does not return.

The Dante Controller presets guide explains selective save, mapping, application, and rollback. A preset is a recovery aid, not permission to apply unknown settings blindly.

Rebuild in a controlled order

1. Reset and reboot according to the product

Run only the selected action and record its time. Some devices can reboot automatically after Clear Config; others require a manual reboot. Do not disconnect power during a documented update or recovery process.

2. Restore network identity first

Rediscover the device on the intended primary and, when used, secondary networks. Apply the approved addressing and redundancy mode. Confirm Controller is using the correct interface and that the two redundant networks remain separate.

3. Restore names, format, clock, and latency

Apply the accepted device name and channel labels, then sample rate, encoding where exposed, clock ownership, and receive latency. Verify each change before proceeding because format or clock-domain mismatch can make routes unavailable.

4. Rebuild routes deliberately

Load a narrow reviewed preset or recreate subscriptions from the accepted patch. Map roles carefully if hardware or names changed. Confirm every receiver uses the intended transmitter rather than judging success from a mostly green matrix.

5. Prove the complete signal path

Pass identifiable audio to every critical destination. Check subscription state, clock stability, primary and secondary link status, packet errors, latency evidence, multicast behavior, and event logs. Test an approved failure and recovery path before returning the device to service.

Reset recovery checklist

• Incident evidence and current configuration are captured.
• The selected action is the narrowest supported recovery.
• IP and redundancy retention are intentional, not automatic.
• A reviewed preset or written rebuild map exists.
• Post-reset discovery works on every intended network.
• Names, format, clock, and latency match the accepted design.
• Every required subscription and physical output passes audio.
• Packet, latency, multicast, and clock evidence remain healthy under load.
• Failure, restoration, and persistence after reboot are tested.
• The new known-good state, owner, and rollback are documented.

Document the recovered device

Record the reason, operator, reset type, retention choice, device and firmware, before-and-after configuration, preset used, route map, test load, acceptance result, remaining defects, owner, and date. Replace the old baseline so the next technician does not restore stale names or routes.

In Techrider.live, keep the recovery record beside the digital patch and network notes. Invite collaborators to edit the same rider, save the accepted revision, inspect history, and export a current PDF for the venue or touring team.

FAQ

What does a Dante factory reset delete?

It can clear user device and channel names, clock settings, static addresses, redundancy configuration, sample rate and pull-up or down, latency, and all existing audio routes.

What is Clear Config in Dante Controller?

On supported devices, Clear Config removes the same core Dante configuration as a factory reset while optionally allowing IP and redundancy settings to be retained. A reboot is required for the cleared state to take effect.

Does resetting a Dante device delete routes?

Yes. Factory Reset and Clear Config can remove existing subscriptions. Capture or export the accepted route map before reset and verify every rebuilt destination afterward.

Can Dante Clear Config keep IP settings?

Supported devices may offer that option, which also retains Dante redundancy settings. Keep them only if they are known correct and match the recovery plan.

How do I restore a Dante device after a reset?

Rediscover it, restore network identity, names, format, clock, and latency, then map and rebuild routes. Pass real audio and verify clock, links, errors, latency, failover, and persistence before returning it to service.