Audio
DiGiCo Quantum 5 troubleshooting
The DiGiCo Quantum 5 problems live-event techs bring to Ask Roadie most (also called Q5, Quantum5). Pick your symptom, or describe your own in plain words, and get the likeliest fix first, with the manual page when there is one.
Common Quantum 5 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.
- Step-by-step fixGet the fix →
Connecting Quantum 5 to Waves / SoundGrid for plugins or multitrack
Likely cause: SoundGrid I/O rides a dedicated DMI card/port; sample-rate agreement between desk and server is required or the SoundGrid network won't clock and plugins/record streams drop.
- Step-by-step fixGet the fix →
How to update Quantum 5 software and what the current version is
Likely cause: DiGiCo pairs console and offline-editor versions; mismatched versions can refuse or mis-load showfiles, so update both together and confirm the version on the master screen after updating.
- Step-by-step fixGet the fix →
Need core Quantum 5 channel/processing spec at a glance
Likely cause: These are the reference numbers you patch and plan a show around; knowing the ceiling prevents over-allocating inputs/busses in the offline editor.
- Step-by-step fixGet the fix →
Optocore loop will not lock / racks missing when connecting Quantum to SD/D racks
Likely cause: A firmware mismatch on the Optocore ring is a hard incompatibility, not a config error — the loop simply will not map old-format racks against a Quantum.
- Step-by-step fixGet the fix →
Physical footprint / power for transport and rigging planning
Likely cause: Weight and footprint drive case, truck and riser planning; redundant PSUs mean you should run both mains feeds (ideally on separate circuits) for show resilience.
- Step-by-step fixGet the fix →
Redundant Optocore system behaving intermittently / audio glitching randomly
Likely cause: Intermittent glitches on a redundant ring are usually the system flapping between main and backup around a marginal fibre; forcing it onto one leg both stabilises the show and localises the fault.
- Step-by-step fixGet the fix →
Remap Optocore still throws an error after pressing Remap
Likely cause: Optocore remap only succeeds when the port map and output-card ownership are identical on every desk on the loop; step 5 (card ownership) is where most techs get tripped up.
- Step-by-step fixGet the fix →
Session/showfile corrupted or console misbehaving after power loss
Likely cause: The desk writes session state on shutdown; interrupting that write is the main cause of corrupt showfiles, and booting to a default rather than your saved show is the single most common DiGiCo user error.
- Step-by-step fixGet the fix →
Showfile built in offline editor won't pass audio / wrong Optocore port after loading on console
Likely cause: The offline editor defaults to Network ID 1; the send-port string doesn't always rewrite on load, so the desk advertises the wrong node and the loop won't route.
- Step-by-step fixGet the fix →
Where to look first when the Optocore ring or I/O is misbehaving on a Quantum
Likely cause: Reading the diagnostics page first turns guesswork into a targeted fix by naming the failing node instead of blindly reseating fibre.
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.
How Ask Roadie helps with the Quantum 5
- 1. Pick the DiGiCo Quantum 5. It's already in the list.
- 2. Describe what you're seeing. In your own words, or the error code off the screen.
- 3. Get the likeliest fix first. Steps in order, the manual page when there is one, and a note when other techs have confirmed it.
- 4. Still broken? Tap 👎 and it keeps going from where you left off.