openmixer — generated API reference
    Preparing search index...

    Variable RECORD_TAP_POINTSConst

    RECORD_TAP_POINTS: readonly TapPointId[] = ...

    THE TAP POINTS THE RECORDER CAN CAPTURE, in signal order — the catalogue subset the native lane walk takes a record capture of (recording-vsc §0.3, tap-points-per-template.md).

    These are catalogue ids, not a vocabulary of the recorder's own. §0.3 rules the taps to be "the template's declared set … configure, no new kernel", and the catalogue's own law is that a point named twice under two spellings puts the reconciliation onto every client that reads both. So input — the phrase §0.3 uses for the virtual-soundcheck tap — IS Post-Trim: the head-amp'd input with phantom, gain, polarity and the alignment delay applied and no channel processing, which is precisely what §2.1 declares and what the lane captures on that line.

    CAPTURED, not merely catalogued. Pre-EQ/Post-EQ/Top-Of-Ch are catalogued and the lane does capture them for a SEND, but the recorder writes no file at them: a take is a stem set plus a soundcheck source, and neither wants the two sides of an EQ as separate files. That is an under-offer, which a client can detect; the offer growing later costs nothing.