Audio
DiGiCo SD5 troubleshooting
The DiGiCo SD5 problems live-event techs bring to Ask Roadie most (also called SD5 console). 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 SD5 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 →
Audible ticks and pops in the audio
Likely cause: Digital audio glitches almost always come from clock mismatch or multiple masters; slaving everything to a single reference at a common sample rate removes the sample slips that cause ticks and pops.
- Step-by-step fixGet the fix →
Core specs / rating reference (weight, power, footprint) for planning transport, power and rigging
Likely cause: Manufacturer data sheet figures — use for truck/case loading, power drops (always feed the two PSUs from separate circuits for redundancy) and desk positioning.
- Step-by-step fixGet the fix →
Error that the SD5.exe application file is corrupted
Likely cause: The desk keeps a backup copy of the application; swapping to the known-good executable restores operation without a full reinstall.
- Step-by-step fixGet the fix →
Firmware / software update process and current version
Likely cause: Running console and offline editor at matched versions prevents session-load incompatibility; noting the current version lets a tech confirm whether a desk is up to date before a show.
- Step-by-step fixGet the fix →
How many channels / busses / racks can the SD5 run, and what feeds it
Likely cause: Confirms system capacity when speccing an input list and rack count; if a desk shows only 124 strips it has not had the Stealth Core 2 upgrade applied.
- Step-by-step fixGet the fix →
Lost all outputs at FOH / cannot regain control of outputs (Optocore emergency)
Likely cause: Output ownership on an Optocore loop is exclusive; clearing and re-broadcasting IDs resolves the contention where two desks (or a stale assignment) both claim the same output module, restoring FOH control.
- Step-by-step fixGet the fix →
Optocore cabling/ID rules and mirrored-desk gotchas
Likely cause: Optocore is a dual-redundant ring; crossing loops or reusing IDs breaks the ring logic.
- Step-by-step fixGet the fix →
Optocore errors from Snd/Rcv (Send/Receive) console conflicts on a shared loop
Likely cause: The error is an ownership/ID mismatch between the sending and receiving desks; re-broadcasting the output IDs re-syncs which console owns which module.
- Step-by-step fixGet the fix →
Session loaded but Waves (SoundGrid) plugins did not load
Likely cause: The Waves plugin instances/state live in the .mrdb; re-importing a good one re-establishes the plugin chain that failed to instantiate on the main session load.
- Step-by-step fixGet the fix →
Session timestamps wrong / DiGiCo time-of-day clock mismatched
Likely cause: The SD5 app derives time from Windows; a timezone mismatch between the two makes saved-session times wrong.
- Step-by-step fixGet the fix →
Startup session corrupted / desk will not load its startup show
Likely cause: The desk auto-loads startup.ses on boot; a corrupt startup file stalls or crashes the load.
- Step-by-step fixGet the fix →
Touchscreen unresponsive mid-show
Likely cause: Touch and mouse/keyboard are parallel input paths into the same GUI, so a dead touch layer does not stop control.
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 SD5
- 1. Pick the DiGiCo SD5. 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.