Dante Sample Rate Mismatch: Fix Failed Audio Subscriptions

TL;DR — A Dante audio subscription requires compatible media formats. If transmitter and receiver sample rates differ, the route may be unavailable or report an incorrect-channel-format error. Sample-rate pull-up/down can also put devices in different clock domains. Inventory every endpoint before changing anything, choose one approved show format, change devices in a controlled order, allow required reboots, rebuild and verify subscriptions, then test clock, audio identity, redundancy, recording, and fallback at the real destinations.

A visible device is not necessarily a compatible audio endpoint

Dante Controller can discover devices that cannot exchange audio with each other. Discovery, control, media format, clock domain, and subscription state are different layers.

Do not treat every red subscription icon as a sample-rate problem. Hover or inspect the status message, then verify the precise boundary it names.

Choose one approved format before editing devices

The correct sample rate is the rate supported by the complete production path, not the highest number shown by one device. Consoles, stage boxes, interfaces, processors, amplifiers, recorders, broadcast systems, and virtual soundcards must all support the planned mode and channel count.

Build a format inventory:

Agree the show format with every destination owner before changing a live network. A unilateral console change can break processors, amplifiers, recorders, broadcast feeds, or virtual soundcheck.

The sample rate versus bit depth guide explains the wider format decision. Bit depth and sample rate are different parameters; matching one does not guarantee the other path is valid.

Separate ordinary sample rate from pull-up and pull-down

Sample-rate pull-up/down changes timing by a percentage, commonly for workflows tied to converted video frame rates. In Dante, enabling a different pull-up/down value can place a device in a different clock domain even when the base sample-rate label looks familiar.

Use pull-up/down only when the production has a specific synchronization requirement and every participating device is designed for that domain. Do not enable it as a troubleshooting experiment. Record the exact percentage, video reference, clock owner, affected devices, and return-to-normal procedure.

The Dante clock leader guide covers leader election and external references. A device can have the intended base rate yet remain incompatible because it belongs to another clock domain.

Change the network in a controlled order

1. Freeze and export the baseline

Record device and channel names, firmware context, current rates, pull-up/down, clock domains, leader, subscriptions, latency, redundancy, and show-file versions. Capture the exact error text.

2. Mute or protect destinations

Coordinate with the system, monitor, recording, and broadcast owners. Protect loudspeakers and feeds from format-change noise or unexpected route restoration.

3. Set the agreed endpoints

Change one defined group at a time, following each manufacturer's instructions. Some devices require a reboot or host-side setting. Confirm the device returns with the intended name, rate, and network mode.

4. Rebuild and inspect subscriptions

Do not assume old routes survived. Check every receive channel, subscription type, flow capacity, and error tooltip. Recreate only the approved routes.

5. Verify clock and audio identity

Confirm the clock domain and leader, then send distinct labeled signals through every critical route. A green subscription proves transport state, not that channel one contains the intended source.

6. Test dependent workflows

Verify recording session format, virtual soundcheck, broadcast outputs, processors, amplifiers, sample-rate converters, redundant paths, and analog fallback. The Dante latency guide covers the separate receive-buffer test.

Avoid destructive recovery shortcuts

Factory reset is not a first-line format fix. Depending on the device, reset or clear-configuration actions can remove names, channel labels, IP settings, redundancy mode, clock settings, latency values, and routes. Read the product-specific warning, export the current state, and use the narrowest supported change.

Also avoid changing every device at once. A staged change preserves evidence and makes the first incompatible boundary easier to identify. If a device cannot support the agreed format, choose a supported converter or fallback path rather than forcing an undocumented exception.

Put the accepted format in the Rider

A buildable handoff names the sample rate, pull-up/down state, clock domain, leader, external reference, every endpoint, device owner, reboot requirement, expected route impact, verification signals, recording format, redundancy test, and fallback.

In Techrider.live, align device and channel names with the input and output lists, invite the system and recording engineers to edit the same Rider, save the accepted format matrix, inspect history after a change, and export a dated PDF for load-in.

Dante format checklist

• Every endpoint's supported and current sample rate is known.
• One approved show format is agreed by all destination owners.
• Pull-up/down and clock-domain membership are explicit.
• Required reboots and route loss are planned before changeover.
• Every subscription and exact error status is rechecked.
• Clock, channel identity, recording, redundancy, and fallback are tested.
• The baseline and recovery procedure are saved.

FAQ

What happens when Dante sample rates do not match?

The incompatible transmitter and receiver channels cannot form a working audio subscription. Dante Controller may make the cross-point unavailable or report an incorrect-channel-format error.

How do you fix incorrect channel format in Dante?

Compare the endpoint formats, agree one supported production rate, protect destinations, change devices according to their manuals, allow required reboots, then rebuild and verify every subscription and audio channel.

What does mismatched clock domains mean in Dante?

It means the endpoints do not share a compatible timing domain. A differing sample-rate pull-up/down setting is one common cause. Inspect the domain and clock configuration rather than changing routes repeatedly.

Can Dante devices use different sample rates?

Different groups may operate separately, but an audio subscription requires compatible formats and clock-domain membership between its transmitter and receiver. The complete route must support the chosen production format.

Does changing Dante sample rate remove routes?

It can disrupt or invalidate routes, and some devices require a reboot. Treat subscriptions as unverified after any format change and inspect every critical receive channel before returning audio to service.

Make format changes recoverable

Create one Rider that records every endpoint, rate, clock domain, subscription, reboot, verification signal, owner, and fallback before changing a live production network.