openmixer — generated API reference
    Preparing search index...

    Function tapModesFor

    • WHICH tap modes a surface may offer for a strip — the one place the member set is decided, so no host composes its own list (mixer-standard.md: variants are props, and a locally composed member set is the defect strip-fx-limits.ts exists to end).

      drive is present exactly while the strip's drive stage is ENGAGED — not merely while the strip is capable of one (operator ruling, 2026-09-15: "enabling in RTA belongs to RTA, enabling drive belongs to drive. If drive is enabled a computed displays in RTA"). A DISENGAGED stage costs the RT thread nothing by design (2026-09-14-native-drive-stage.md §4g), which means it captures no straddle rings, which means the pair's row publishes nothing: selecting that tap answered with a trace that never moved, and the operator read it — correctly — as the analyser stalling. So the chip is ABSENT while the stage is off rather than present-and-disabled: there is no reading to offer, and an offer the desk cannot honour is the defect this function exists to prevent.

      The parameter is named for what it now MEANS. It was hasDrive — a capability — and every caller passed one; a rename that left the word alone would have kept two truths in one argument.

      Parameters

      • driveEngaged: boolean

      Returns readonly ("drive" | "pre" | "post" | "both")[]