openmixer — generated API reference
    Preparing search index...

    Variable CHANNEL_RECALL_SAFE_POLICYConst

    CHANNEL_RECALL_SAFE_POLICY: ResourcePolicy = ...

    What a committed write to this row means for the console's bookkeeping.

    Not persisted, deliberately. A recall-safe decision is live show state: the FOH engineer safes the vocal they are riding for the next three songs and clears it after. Restoring one from a session loaded days later would exempt channels from every recall with nothing on the surface having asked for it — the defect D9 already recorded for persisted SOLO, in a control whose whole purpose is that the operator knows what a recall will leave alone. So dirtiesSession: false: a safe changes no state a session carries, and touching one must not mark the show dirty or trip an autosave.

    It is likewise never inside a SCENE — that was true before this row and stays true. A scene that carried the mask governing its own recall would rewrite, on being recalled, the very decision that decided what the recall could touch.

    Not undoable. The same law solo, solo-safe and mute already hold: an undo must never flip a gig-safety latch mid-song. Recall-safe is stronger still — an undo that quietly unsafed a channel would be discovered at the next scene change, by the channel being overwritten.