GLMedia — DiGiCo: mute and auto-mute record
Proposed tests. All results remain to be completed.
Event / type / date / technician and person responsible for test:
Exact console / software / rack / firmware / license / patch:
Applicable documentation and edition / original file and copy:
PA / IEM / wedge / recording destination / agreed level:
Return state / responsible operator / recovery file:

VOCAL PATH
Receiver model / observed RF / observed audio / console input:
Input / destination / signal before / signal after / listening / evidence:
MUTE, HARD and CG MUTE indicator states before and after:
Exact action and control sequence on the model used:
Do not infer audio solely from RF or fader position.

GOAL PER CUE
Cue | input | intended open or muted state | intended members | evidence
___ | _______ | _____________________________ | __________________ | _________
Global Scope / individual Recall Scope / Safe screenshots:
Saved states / initial condition / group states:

COMPARISONS
Test | single change | observed members | observed states | listening | return
______ | ____________ | __________________ | _________________ | _______ | ______
1. Manual editing on a test channel.
2. Recall with documented initial conditions.
3. Second pass with the agreed scope change.
4. Channel with multiple membership: all groups and states.
5. Forward / return / cue jump: compare with written goals.

CLOSURE
Recovery performed / who / result / screenshot / time:
Differences / pending / person responsible / next test:
Was it extended to all show inputs and destinations? To be completed.
Test status: proposed / performed / repeatable / pending:
Someone else’s inquiry does not establish this setup or GLMedia validation.