DiGiCo Quantum 326 troubleshooting

Common Quantum 326 errors & problems

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

• Cannot get the Optocore loop to sync/clock to an incoming AES/EBU or MADI signal

  Likely cause: The Optocore loop must be the timing reference for its own devices; DiGiCo explicitly does not allow the loop to be clocked from AES/EBU or MADI inputs.

  Step-by-step fixGet the fix →

• Clicks, pops or digital noise across MADI/AES/DMI connections

  Likely cause: Digital consoles must share a single word-clock reference; any device free-running at a slightly different rate produces periodic clicks as buffers slip.

  Step-by-step fixGet the fix →

• Mirrored (redundant) Quantum 3 consoles will not mirror or drop the mirror link

  Likely cause: DiGiCo redundant mirroring requires identical software on both engines so parameter sets stay in lockstep; a version mismatch is the most common reason a mirror will not lock.

  Step-by-step fixGet the fix →

• No audio on a channel or local output that should be passing signal

  Likely cause: On Quantum consoles a "dead" channel is most often a patch/ownership or dual-input (Main/Alt) selection issue rather than a hardware fault; Hard Mute in particular silences a path independently of the normal mute.

  Step-by-step fixGet the fix →

• Optocore device(s) missing from the loop / not appearing

  Likely cause: The diagnostics page is the authoritative view of what the loop actually sees; missing devices are almost always an ID clash, a speed/mode mismatch, or a rack on the wrong Optocore firmware.

  Step-by-step fixGet the fix →

• Optocore still throws an error after pressing "Remap Optocore"

  Likely cause: Optocore remap only succeeds when port assignments and output-card ownership are identical across all consoles on the loop; step 5 (output-card control) is where most techs get tripped up.

  Step-by-step fixGet the fix →

• Power / true-redundancy setup and moving the console safely

  Likely cause: The 52kg surface is a genuine two-person lift.

  Step-by-step fixGet the fix →

• Setting up redundant MADI on the Q326

  Likely cause: The 6 physical MADI ports are shared between capacity and redundancy; pairing them halves the interface count but gives automatic failover, which is the safer choice for a show-critical stage box.

  Step-by-step fixGet the fix →

• Showfile built in Offline Software will not connect to Optocore rack on a console whose network ID is not 1

  Likely cause: When a showfile authored on the offline editor (default ID 1) is loaded on a console with a different network ID, the console does not auto-correct the Con Send port, so the loop never establishes.

  Step-by-step fixGet the fix →

• Updating console software / recovering a console that hangs on boot

  Likely cause: DiGiCo ships console and offline software as matched versions; running mismatched versions causes showfile and mirroring problems, and a clean USB restore is the standard recovery path for a hung console.

  Step-by-step fixGet the fix →

• Waves SoundGrid (or Fourier Audio) card not passing audio

  Likely cause: The Waves path is an optional card, not standard; missing audio is usually an unfitted/unlicensed option, a SoundGrid network fault, or a clock mismatch between console and server.

  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 DiGiCo gear

Other audio gear