Build an audio signal path

Hands-on: console → wireless → DSP → amps with Dante, AES, and XLR ports — same workflow as your first video diagram.

When to use this

Follow after Build your first diagram when you need to document the A1 path — wireless mics, console, DSP, and amplification — on the same connection-aware canvas.

Goal

Build a readable FOH audio chain: wireless receivers into a digital console, Dante or AES into a DSP, and DSP outputs into amplifiers. Label everything the way your A1 calls it on comms.

Create or open a diagram

  1. /diagrams → New Diagram (or open an existing show diagram)
  2. Name it clearly — e.g. Client — Gala — Audio

Add audio devices

  1. Toolbar → Device library
  2. Use the category filter and browse Audio (and related presets such as wireless receivers, consoles, DSP, and amplifiers)
  3. Click or drag devices onto the canvas in signal order left-to-right: Wireless Mic Receiver → Audio Console → DSP → Amplifier
  4. Double-click each device header to set instance aliases — e.g. WIRELESS, CONSOLE, DSP, AMP-L / AMP-R

Tip: Match aliases to rack tape and comms call signs — your A1 should recognize names instantly.

Wire the path

  1. Click an output port on the source device, then click the destination input
  2. Wireless analog outs → Console mic inputs (XLR or compatible audio types)
  3. Console Dante Out (or AES/EBU) → DSP Dante In (or AES In)
  4. DSP outputs → Amplifier inputs — use the port types your rig actually carries (Dante, AES/EBU, or analog)
  5. Shift + click a port if you must force-connect mismatched types with an adapter (use sparingly)

Tip: Always start from the source output — same rule as video cabling.

Review in Connections

  1. Toolbar → Connections
  2. Scan the cable list — each row shows cable ID, signal type, and source → destination
  3. Click a connection to open the Connection inspector (signal, cable type, length, label, run)
  4. Search cable IDs if the list is long (e.g. DANTE-001)

Save

  1. Header → Save Project or Update Project

Best practices

  • Document Dante/AES network paths on the same diagram or a dedicated network zone — label VLAN or hostname in device notes when it matters on site
  • Use per-port signal labels (double-click port name) for house left/right, subs, and fills — not just generic "Out 1"
  • Hide unused ports on busy faceplates so the A1 path reads cleanly in exports

Common issues

  • Connecting output to output — verify port direction (in vs out) on consoles and amps
  • Dante ports wired to XLR without Shift+click adapter — WireFlow blocks incompatible pairs by design
  • Device library shows generic names — always set canvas aliases before sharing with crew

Next

For multi-room shows, add a floor plan and site map zones. For handoff, see Share and export.