DiGiCo and SuperRack: snapshots, saving and recall

Snapshots: missed recalls or settings lost after reloading

Separate snapshot triggering from whether settings survive saving and reloading. If either stage fails, record the console and Waves component involved before changing the session.

Identify the setup before changing ProLink or cabling

Record the model, full console software version, SuperRack build, plugins, operating system, Waves I/O and servers. Draw which connection carries audio and which carries control.

For Quantum338, Waves’ April 15, 2024 guide, Connect the network and Set up ProLink Console Remote distinguishes single-server and multiple-server setups. In a multiple-server setup, Waves I/O and servers connect to the same compatible external switch, along with the host and console. When assigning the console in Controllers, the expected status is Connected. Having a spare server on the equipment list does not establish that failover has been tested.

The Waves support article dated April 27, 2026, ProLink console remote vs. Legacy specifies SuperRack V14.30 and DiGiCo V1742 for ProLink. The SuperRack manual linked below gives a different DiGiCo version reference: later than 16.06.1609. Keep both references and confirm compatibility for the installed builds before choosing an update.

Quantum338: check the Waves snapshot recall scope

Manufacturer instruction: Waves, Snapshots integration doesn’t work says to include Waves in Snapshots → Global Scope and in Scope → Recall Scope for each affected snapshot. Remote control can be connected even when Waves is missing from the recall scope.

In DiGiCo SD & Quantum, Issue E, V1528+, §2.4, pp. 89–90 and 96–98, Current is the last snapshot fired; Selected may be a different one. The panel distinguishes Update Current from Update Selected and includes update Waves only when Waves is active. Check the target before updating. This edition is from February 2022; compare it with the installed interface.

Suggested test on a copy, with an agreed monitoring path: choose two clearly identified snapshots and a parameter that is easy to compare. Note the expected value for each, fire them from the console and record the active snapshot in both applications and the plugin value. If SuperRack does not change snapshots, keep screenshots of the scope and remote status. If it changes snapshots but not the value, record the rack, plugin and parameter: these are different observations for support.

A common mistake is updating a selected snapshot because its name is visible, assuming it is the one that just played. Check the target and value first; avoid applying the change across the whole show to fix one transition. Verify the result with the installed version.

SD12: check what was saved and what returns after loading

Waves, Integration Guidelines, May 18, 2022, session saving describes saving from the console to preserve the integrated session on the SuperRack computer. Then check that the saved revision recalls the expected values.

To prepare the test, keep both original files and work with an identified new revision. The DiGiCo manual, Issue E, §2.2, pp. 73–74 warns that Save Session overwrites the last saved session; Save As New File lets you keep it. Record the name, folder and date of both files before reloading.

First check that each snapshot recalls its expected value without closing the session. Then save the copy using the integration workflow for your version and record the resulting files. In a separate pass, reload that revision from the console and repeat the same transition. Record whether the snapshot changes, whether the parameter changes and whether it matches your notes from before saving.

If the value changes only after reloading, send support both screenshots and the pair of files. If the test works in a new session but fails in the show copy, keep both results; this does not yet identify the data causing the difference. One successful pass does not verify every cue.

Integrated Sessions: files and differences between documents

The SuperRack SoundGrid User Guide, pp. 120–122 and 144–146 documents the integrated-session folder and ProLink assignment. The cited 156-page edition does not identify a revision number. The paths in the table come from p. 146; some HTML articles repeat SoundGrid or use Waves Audio in the Mac path. Check the actual location on your host rather than creating folders by trial and error.

According to Waves, Loading and Saving Integrated Sessions and the empty-session troubleshooting section, the console looks for an integrated session with the same name. If none exists, it loads an empty session. Save what you were preparing before connecting: a newly loaded empty session does not mean the files were deleted.

Documented caution in the SuperRack manual, p. 122: loading a session can cause a dropout or click. Run the comparison outside show operation, with agreed destinations. Do not delete or move CurrentSPRK.dat or CurrentSPRK.dat-journal: p. 121 identifies them as recovery files.

Waves states that SuperRack’s Recall Safe and Scope screens are disabled in Remote mode. Interpret that behavior alongside the console’s scope; it does not automatically indicate a fault. Check version compatibility, the actual folder and whether each cue’s settings survive saving and reloading.

Test worksheet for a concert, festival or theater show

Complete the DiGiCo–SuperRack worksheet with the operator. Leave results blank until you run each pass. Change one variable at a time and record how to return to the initial revision; separate recall, saving and reloading.

Use the test alongside Quantum338 and FOH/monitor consoles (Spanish guide), continuity and backup planning and GLMedia audio systems. Run the checks during preparation and record the results for the actual setup.

Quantum3: prepare offline without assuming the editors are synchronized

Use a cue table to prepare names, order and plugin changes without a console. Do not assume the editors are synchronized: check the connection to the console before the event.

The SuperRack SoundGrid manual, p. 156, Working Offline allows session preparation with virtual devices through Offline Devices. Configure the planned I/O and racks in a copy. This prepares SuperRack; the cited sections do not establish that DiGiCo Offline 2025 simultaneously controls its snapshots. The SuperRack SoundGrid product page also describes a separate license for editor mode, which does not pass audio. Record the mode and build you are using.

Before preparing the whole show, make a copy with two easily distinguishable cues. For each, record the number, console name, SuperRack name and an expected parameter value. This table helps identify an offset or incorrect association when you reach the console. Leave the connection check outstanding until you fire the cues on the real system.

External ID, list order and filename: record three separate details

In Assigning Remote IDs to Snapshots, p. 132, Waves documents that External ID can be assigned when naming a snapshot or through its drop-down menu, separating list order from remote order. The manual’s example is MIDI; it does not verify the ProLink behavior of your setup.

For the integrated file, Waves, Loading and Saving Integrated Sessions, April 27, 2026 states that the console loads the SuperRack session with the same name and creates an empty one if that file is missing. Include both files, the revision and actual folder in the handover; review the path differences in the previous section before copying them.

The Quantum3 manual, Issue A, January 2020, software 1200+, §1.5, p. 16 distinguishes Save As New File from Save Session, which overwrites the previous file. Use another revision to preserve the initial handover. The manual’s edition alone does not establish compatibility with an editor identified only as 2025.

A common mistake is correcting only the visible name and overlooking the number or ID. If you insert or reorder a cue, mark the changed row and check that transition again. Keep the earlier table for comparison; do not change every association at once.

Offline handover: a short check before the show

Use two separate passes. First review the files and table without touching the event mix. Then, outside show operation, load the copy on the agreed equipment and fire both cues from the console. Record which snapshot appears and which value the plugin recalls. If the name matches but the value differs, keep both observations; this is not the same symptom as a cue that never arrives.

Complete the offline fields in the rehearsal worksheet. Leave results blank until you run the test. If the file changes after rehearsal, save another revision with the table, build and result so support has a reproducible case.

For a setup that processes plugins on the computer, also see SuperRack Performer: routing and snapshots. Identify the selected I/O and software in the handover for event audio.