openmixer — generated API reference
    Preparing search index...

    Variable DRIVE_MIX_RANGEConst

    DRIVE_MIX_RANGE: {
        default: 100;
        defaultFrom: "desk";
        max: 100;
        min: 0;
        step: 0.1;
        unit: "%";
    } = ...

    The wet/dry, as a PERCENT — the unit a drive control is read in on every desk that has one.

    Deliberately not NORMALIZED_RANGE (which is unitless 0..1): a mix a surface must label "0.35" when the operator thinks in "35 %" is a control whose declaration is fighting its reader. The kernel divides by 100 where it resolves the atom, in one place.

    The come-up is 100 %, not the reverb's modest 30: a saturator's insert use is IN the path. The exciter curve seeds itself lower, in the controller, because that is a property of the TOPOLOGY and not of the travel.

    Type Declaration

    • Readonlydefault: 100
    • ReadonlydefaultFrom: "desk"
    • Readonlymax: 100
    • Readonlymin: 0
    • Readonlystep: 0.1
    • Readonlyunit: "%"