Audinate Dante Preset Creator troubleshooting

Common Dante Preset Creator errors & problems

What techs run into most, and what's usually behind it. The step-by-step fix for your exact software is in Ask Roadie.

• AES67 or SMPTE ST 2110-30 settings did not carry across with the preset

  Likely cause: Dante-native subscriptions and RTP/AES67 flows are separate objects in the preset schema.

  Step-by-step fixGet the fix →

• Apply Preset dialog will not let the preset apply - a role or device shows a dark grey / black LED

  Likely cause: Duplicate device names or duplicate static IPs would break name resolution and IP routing on the Dante network, so Controller refuses to apply rather than render the network unusable.

  Step-by-step fixGet the fix →

• Applying a preset wiped subscriptions that were not in the preset

  Likely cause: Rx subscriptions are treated as a complete picture of the receive side, whereas Tx flows are treated as additive-unless-specified.

  Step-by-step fixGet the fix →

• Device rename appears to hang or time out during preset apply

  Likely cause: The intermediate-name mechanism only works if the final name is genuinely free at the end of the sequence; a stray device holding that name outside the preset stalls the swap until the 40 second monitor gives up.

  Step-by-step fixGet the fix →

• Devices rebooted and audio dropped when a preset was applied to a live network

  Likely cause: Those parameters change how the Dante interface itself is initialised, so the device has to restart its audio engine.

  Step-by-step fixGet the fix →

• Intermittent "internal error" when applying a preset with RX Flows or TX/RX channels to IP Core Zynq HC devices

  Likely cause: The error is transient in Controller's apply sequence rather than a bad preset, so a repeat pass normally completes; splitting the elements shortens each transaction.

  Step-by-step fixGet the fix →

• Load preset error traced to a Tx channel label in the XML

  Likely cause: The bug is in label parsing on load; removing or shortening the label removes the trigger, and the 32-character convention keeps labels inside what every Dante device accepts.

  Step-by-step fixGet the fix →

• Loading a preset fails with "error reading version from presets"

  Likely cause: Dante Controller explicitly supports legacy preset files but not forward-compatibility.

  Step-by-step fixGet the fix →

• Need to configure a Dante network before the gear is on site / rack build is not done yet

  Likely cause: Preset files are plain XML and are device-agnostic, so a preset built with no hardware present can be matched to physical devices at apply time.

  Step-by-step fixGet the fix →

• Preset applied but one parameter (usually sample rate) was rejected on a substitute device

  Likely cause: Preset Elements are individually selectable at apply time precisely so a partial match can still be used.

  Step-by-step fixGet the fix →

• Preset will not load when it contains Codec or Clock Priority parameters

  Likely cause: The parse failure is in Controller, not the file, so either a newer parser or removing the offending block gets the rest of the preset in.

  Step-by-step fixGet the fix →

• Roles from the preset auto-assigned to the wrong devices

  Likely cause: Because auto-assignment keys on name first, two racks with the same naming convention will cross-assign.

  Step-by-step fixGet the fix →

Not on the list? Describe it your way, or paste the error code off the display. Ask Roadie works the problem with you until it's fixed or you have a clear next move.

More Audinate gear

Other audio gear