DiGiCo SD10T: cues, Auto Update and cast changes

Auto Update can propagate an adjustment to other cues sharing the relevant data. Before editing the EQ again, check whether it is enabled, which Alias the channel uses and which module you are changing. Two cues using the same channel do not necessarily share the same Alias or module settings.

Check Options > Theatre > Auto Update Exclusions and Cues > Scope > Group & Auto Update Scope. Exclusions and scope restrict which parameters update. Do not rely on the button state alone: when Option/All is configured for Cue Auto-Update, using it reverses the rule, including for excluded controls.

In the rehearsal copy, make a small, recognisable change and compare the chosen cues. If it appears somewhere unintended, stop updating and compare Aliases, modules and scope before continuing. Turning Auto Update off does not undo data already written; recover the saved copy if you need the previous state.

An assignment edited in Control Group Cues reaches the surface when the cue is recalled. First check which cue is selected for editing and which one is current; they need not be the same. Also check the Scope column: a cross prevents those membership changes from recalling.

Before using Assign or Clear, check Ripple Down. When enabled, it can extend the edit into following cues until a change of state is encountered. The guide warns that these assignments have no Undo. Test the cue during rehearsal and verify CG members before moving its fader during the performance.

If you changed a Channel Set after using it to assign a CG, the existing assignment does not update automatically. Check the affected cells and reassign the set where needed, with Ripple Down in the intended state. Verify membership without testing the fader with microphones open to the audience.

Selecting a Player changes the selection, but its settings take effect when a cue is recalled. In Layout > Players, check which Player is current and perform the test recall. Then check a parameter known to differ between the two versions, rather than relying only on the displayed name.

Before creating the first Player, set Options > Theatre > Single Player Update. It determines which modules retain performer-specific settings and which can share changes. The V4 guide states that this selection is fixed once Players exist. Do not delete Players from a performance session to try to unlock it.

A new Player starts with the settings and structure of the Player active when it is created. Check that starting point and recall the cues involving voice, costume or microphone changes. Selecting the correct Player does not replace gain and listening checks with the performer who will go on stage.

Use an Alias to organise a channel variation, such as a costume affecting microphone response. Open Aliases from Input Channel Setup and inspect Copy Settings and Update Changes for each module: copying the initial state and allowing later edits to be shared are separate choices.

For independent EQ, check that the EQ module does not inherit updates between the variations you want to separate. In Channel Cues, verify the Alias assigned to each cue. Before replacing an assignment, check Update Single, Update Group, Ripple Down or Update All; the scope is not always limited to the cue you are viewing.

Rehearse the transition by recalling a cue for each variation. Make a small EQ correction and check that it reaches only the intended situations. If another variation changes, investigate module inheritance and Auto Update before creating more Aliases: extra names alone do not guarantee independence.