Audio · software
Waves SuperRack troubleshooting
The Waves SuperRack problems live-event techs bring to Ask Roadie most (also called SoundGrid, SuperRack SoundGrid, Waves SG). 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 SuperRack 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 →
Can I build/prep a session without a server connected?
Likely cause: Offline mode loads the SuperRack engine and plugin GUIs without requiring a DSP server inventory, so all session/session-building work can happen in advance.
- Step-by-step fixGet the fix →
Console snapshots do not fire the matching SuperRack snapshot (scene sync)
Likely cause: SuperRack listens to the console remote protocol; when the integration/protocol is enabled and versions match, snapshot events are mirrored bidirectionally so the rack stays locked to the desk cue.
- Step-by-step fixGet the fix →
Error: "The Waves SoundGrid Driver failed to initialize"
Likely cause: The ASIO/Core Audio SoundGrid driver can lose its registration after OS updates or version mismatches; re-running the bundled installer re-registers it against the current SuperRack build.
- Step-by-step fixGet the fix →
Immersive (surround/Atmos-style) racks — how, and what version?
Likely cause: Immersive racks require the V15 multichannel bus architecture plus the Immersive Wrapper to fan a mono plugin across the immersive bed; earlier versions only handle mono/stereo racks.
- Step-by-step fixGet the fix →
Intermittent audio dropouts specifically on macOS (Ventura or later)
Likely cause: SoundGrid relies on precise low-latency Layer-2 timing; macOS Ventura+ network-stack changes interfere with that timing, causing periodic buffer under-runs heard as dropouts.
- Step-by-step fixGet the fix →
LAWO integration: snapshots missing after closing and reopening SuperRack
Likely cause: The re-load re-reads the full snapshot list from the saved session rather than the partial state left after the reconnect, restoring the missing entries.
- Step-by-step fixGet the fix →
MIDI controller advancing snapshots is off by two (offset ahead)
Likely cause: With WINDOWS held in Recall Safe the recall engine skips the expected index steps, so each MIDI next/prev lands two snapshots away from the intended cue.
- Step-by-step fixGet the fix →
Redundant / mirrored server or dual-host setup not working reliably
Likely cause: Redundancy and mirroring copy processing/session state between identical nodes in real time; differing hardware generation, app version, or plugin builds produce incompatible state and prevent clean failover.
- Step-by-step fixGet the fix →
SoundGrid server not showing in host inventory (or appears as N/A)
Likely cause: SuperRack discovers DSP servers over the SoundGrid Layer-2 network; a bad link, unqualified switch, or stale inventory entry stops discovery.
- Step-by-step fixGet the fix →
What cabling and switch do I need for a reliable SoundGrid/SuperRack network?
Likely cause: SoundGrid is a real-time Layer-2 audio network; sub-spec cable, unqualified switches, or daisy-chaining introduce latency/packet issues that show up as dropouts or lost server discovery.
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 SuperRack
- 1. Pick the Waves SuperRack. 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.