Audio · software
d&b audiotechnik ArrayCalc troubleshooting
The d&b audiotechnik ArrayCalc problems live-event techs bring to Ask Roadie most (also called AC12, ArrayCalc 12, ArrayCalc V12, d&b ArrayCalc). 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 ArrayCalc errors & problems
What techs run into most, and what's usually behind it. The step-by-step fix for your exact software is in Ask Roadie.
- Step-by-step fixGet the fix →
ArrayCalc says failed to save project / crashes loading project
Likely cause: Vendor-fixed bugs; latest build contains all fixes.
- Step-by-step fixGet the fix →
ArrayCalc won't start on Windows / Vulkan error / blank 3D view
Likely cause: Older/integrated GPUs and remote-desktop sessions often lack Vulkan, so the V12 renderer can't initialise.
- Step-by-step fixGet the fix →
can't open ArrayCalc file / project from newer version won't load
Likely cause: Each release can extend the project schema, so older builds refuse newer files.
- Step-by-step fixGet the fix →
check for updates says no update / in-app updater not finding new version
Likely cause: Older updater builds had detection bugs.
- Step-by-step fixGet the fix →
DS100 in R1 not initialising / audio problems after DS100 firmware 3.0
Likely cause: The project's I/O configuration must match the device firmware's channel count.
- Step-by-step fixGet the fix →
no amplifiers in my ArrayCalc project after adding speakers
Likely cause: Workflow changed in V12 to the graphical Patch plan.
- Step-by-step fixGet the fix →
predictions changed after updating ArrayCalc / GR LEDs at different level
Likely cause: Model data and algorithms changed, not a fault.
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 ArrayCalc
- 1. Pick the d&b audiotechnik ArrayCalc. 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.