Audio
DiGiCo 4REA4 troubleshooting
The DiGiCo 4REA4 problems live-event techs bring to Ask Roadie most (also called 4REA4 processing). 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 4REA4 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 →
A3232 network links are unstable, dropping out, or not linking
Likely cause: A3232 runs fixed 100Mbps and does not tolerate auto-negotiation; shielded solid-copper Cat5e within 100m keeps the link clean, especially where PoE is present.
- Step-by-step fixGet the fix →
APAD iPad app will not connect to the 4REA4 engine
Likely cause: The APAD app and the Controller talk over IP; a subnet mismatch or a version mismatch between app and firmware blocks the handshake.
- Step-by-step fixGet the fix →
Clock/sync problems, ticks or artifacts across DMI-connected devices
Likely cause: The 4REA4 derives its DMI clock from the MASTER (DMI 1) slot; a single defined master with everything else slaved prevents the double-clocking that causes ticks and dropouts.
- Step-by-step fixGet the fix →
Only odd network IDs work / two engines conflict on the loop
Likely cause: The Optocore/DiGiCo ID scheme pairs each primary (odd) with its mirror (even); using an even ID on a standalone engine collides with the reserved mirror slot.
- Step-by-step fixGet the fix →
Optocore still throws an error after pressing "Remap Optocore"
Likely cause: Optocore remap only succeeds when the output-card ownership map is identical on all consoles on the loop; mismatched Con Send ports or card ownership are the usual cause, not a firmware bug.
- Step-by-step fixGet the fix →
Showfile built in the offline editor passes no audio after loading on a console with a non-default network ID
Likely cause: The Con Send port must match the assigned network ID for other devices to receive that console's streams; the editor does not auto-correct it on load.
- Step-by-step fixGet the fix →
Want redundant audio transport on the 4REA4
Likely cause: The 4REA4 supports port-pair and wall-unit redundancy so a single cable/port failure does not drop audio, but only when the redundant partner is explicitly configured.
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 4REA4
- 1. Pick the DiGiCo 4REA4. 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.