DiGiCo Quantum 225

A channel label does not select the physical socket.

1. Check Audio I/O rack/port configuration and Audio Sync; then compare Main/Alt selection with the actual input socket and meters. Use the exact rack/link manual.
2. Verify a known source through one protected route. If missing, preserve socket map and status for support; do not assume any MADI/Optocore/Dante rack works with every installed option.

Record the expected Main and Alt sources before selecting another. If only one route fails, compare it with the approved map without changing the clock or repatching every rack; that would introduce additional faults that are hard to distinguish.

Control Groups control channels; they do not mix audio.

1. Draw the intended signal flow. The documented Merge Input can add a selected source to a bus; check enable, level and destination without feeding a bus back into itself.
2. In rehearsal, verify the result and processing alignment. If the design cannot be verified, keep the original routing and request system review; do not apply an arbitrary forum delay.

Check recall boundaries before firing it again.

1. Compare global and individual Recall Scope plus channel/CG Safes. Control Group Members covers names/membership; fader recall is a separate scope choice in the referenced version.
2. Test in the protected session copy. Snapshot Undo follows the previous recall scope and is not a complete-session recovery guarantee. If results differ, retain the backup and record version/scope for support.

For an event with several segments, list what should change and what must remain between presentations, including shared sources and destinations. We can assess snapshot preparation and rehearsal, simpler manual operation, or changeover assistance according to the program. The proposed check compares expected states before and after each transition and verifies the agreed return; a stored snapshot is not treated as a backup of the entire session.

Create a scene list and identify what must change at each transition. Recall Scope and Safes can limit snapshot recall; storing a scene does not mean everything should be recalled. Review shared rack parameters in particular. Rehearse transitions in a copy, checking what changes and what stays. If recall cannot be validated, retain a documented manual operation for that transition. We can evaluate show-file programming and an operator with the equipment.

Define what must remain available during each changeover: announcements, music, video, and production communications. Ask whether the guest engineer will use the prepared session or needs to load their own file; these are different scopes. We can compare an agreed session with rehearsed snapshots, adaptation of separate files, or an additional path for sources that must continue while the main console is prepared. A snapshot does not back up hardware or guarantee continuity when another session loads. To quote, send the running order, available files, continuing sources, and time between segments. Console, preparation, changeover operation, and verification of the agreed return can be included subject to resources and availability; an inaudible transition is not promised without validating the system.

Use it as a starting point, not proof of physical patching. Compare version, structure, racks, cards, Main/Alt, and destinations with the deployment; retain the original using Save As New File. A correct channel name does not confirm its socket. Share the available file and a provisional rider to assess adaptation, racks/links, and rehearsal. If I/O is still undefined, we can first quote preparation scope and compare a simpler configuration without promising file compatibility. Also identify the program you are using: the iPad app provides remote control; PC Offline software is used to work on a session without the console. Check the file model and version against the target software before editing. DiGiCo warns that SD Convert cannot make a newer session load into older console software. Opening a file on a computer does not verify audio, racks, or physical connections. We can include a file review and a test with the planned system before the event; you can discuss this preparation while the rider is still provisional.

Splitting an output delivers the same program; it does not create independent balances. List destinations: monitors with the required voices and instruments, the agreed camera feed, and the PA mix. Assess auxiliaries and matrices as appropriate; a matrix distributes existing mixes but cannot recover sources that never reach it. Confirm allocated buses, tap points, physical connections, and format with each receiving device. Rehearse planned control changes and check which destination changes. We can compare one-mix distribution, independent mixes, and patch preparation without adding unnecessary racks or processing.

Agree whether the camera needs a program mix, clean speech, or separate tracks; “audio for video” does not define that feed. For monitors, list mono/stereo mixes and the instruments each musician needs. Count available buses, physical outputs, and each receiver’s format separately before adding a rack. We can compare existing session resources, independent feeds, or a package with more resources if the rider requires it. A provisional destination list and known models are enough to prepare rental or purchase options, patching, testing, and operation; pending details remain subject to confirmation.

Define which console controls the preamp and which follows its changes using Gain Tracking. The manual’s DMI-MADI example uses 48 kHz and specific racks: only the controlling console uses their outputs. Do not extend it to every rack or link. During rehearsal, check gains and outputs at both positions; do not change ownership during the show. We can compare a shared rack, additional outputs, or a split with independent preamps. Send models, installed cards, and monitor requirements even with a provisional patch; the proposal will confirm compatibility and scope.

Record which microphones share preamps, who retains control, and which console feeds each output. Shared audio does not define responsibility for gain, phantom power, file recovery, or equipment removal after a set. If operations need independence, we can compare a shared rack with documented control/tracking, another supported allocation, or appropriate signal splitting with independent preamps. A tour using two Quantum 225 consoles and an SD-Rack does not validate every card or rack combination. Send models and installed options, mixes, recording needs, and changeovers; rental/purchase and system operation can be scoped with outstanding compatibility identified. Rehearsal should include planned changes and check destinations that must remain stable.

These are different requirements. A Control Group controls channels; by itself it does not create a new summed audio output. For a grouped feed, assess an audio bus with the required routing and processing. Decide whether recording needs a drum stem, individual tracks, or both; preserve the intended monitor mixes too. During rehearsal, move the agreed control and verify which destinations change and what is recorded. We can compare multi-channel control, stem delivery, or multitrack recording. Send known sources and destinations; the proposal will confirm resources, outputs, and preparation rather than infer them from an available fader.

For a recording quote, specify whether the file should follow room-mix changes, use a different balance or also provide each microphone separately. We can compare a stem prepared in the session with multitrack delivery and later mixing, confirming the interface, formats and recorder. Agree on listening to and playing back a sample before the show; a moving fader does not establish what was recorded.

Confirm the exact unit before accepting the rider. The official documentation consulted lists up to 72 inputs for Quantum 225 and 120 for Quantum 225 Pulse; it does not establish which expansion is enabled on the offered console. Count mixing channels, buses, and rack connections separately: adding connectors does not itself increase processing capacity. We can compare a Pulse with verified capacity, another compatible console, or an artist-approved reduction in sources. Send a provisional input list, mixes, and recording needs for a rental or purchase proposal with appropriate racks, links, and preparation.

The official Quantum 225 page lists 36 aux/subgroup buses; the Quantum 225 Pulse page lists 48. Verify the variant, version and enabled resources on the offered unit. Do not assume that a software expansion or card is included because it is mentioned as an option.

For rental or purchase planning, separate simultaneous sources, monitor mixes and camera or recording feeds. We can assess reallocating resources if it meets the rider, adding I/O when connectors are missing or quoting another configuration when processing is insufficient. Send the date, venue, provisional list, known racks and test time to start; the proposal identifies capacity, connections, file adaptation and operation, with compatibility items still requiring confirmation.

A virtual rehearsal can be assessed with compatible recording and return paths. The Quantum 2 guide documents Copy Audio and Listen To Copied Audio over MADI; confirm available ports, version, and interface on the Quantum 225 rather than assume any file or computer completes the system.

Prepare the track map and retain the operating session. Outside the show, verify channel correspondence and return to live sources. We can compare virtual rehearsal, a more limited in-person check, or the recording/preparation scope needed. Tracks do not test the microphones or the actual stage sound.

Not necessarily. Quantum 225 includes Nodal Processing; the SD/Quantum reference documents EQ and dynamics on a channel’s send to an auxiliary, with resources limited by model. It can treat that contribution in one specific mix: this differs from EQ on the entire bus or changing a shared headamp. Before programming, identify musician, source, auxiliary, and tap point; verify resources and the offered unit’s version. At rehearsal, check the affected mix and those that must remain unchanged, as well as snapshot scope. We can compare send adjustment, prepared nodal processing, or documented channel separation when appropriate. Tell us what each musician hears and the time available to quote preparation and an operator; enabling a feature alone does not guarantee feedback or preference issues will be resolved.