openmixer — generated API reference
    Preparing search index...

    Function outputEndpointFoldPort

    • The single MONO port a multi-leg endpoint FOLDS onto — the port every present leg names — or undefined when the endpoint's legs address distinct ports (a real per-leg destination).

      This is the shape of a fold (#284, the 2026-07-16 S-0808 blast). The operator ticked both the L and the R cell of MAIN on his stagebox's MONO channel 8; each tick is a leg, and the two legs named the SAME port. Two single-leg routes onto one port are raw-summed by PipeWire with no fold gain, so correlated/centre material lands ~+6 dB hot — "even at minimum vol it is too much". Both legs of one bus on one port is not two destinations: it is ONE fold destination, realised by a single native channels == 1 / OMX_ROUTE_FOLD route running omx_fold_gain(busL, busR, …) at MONO_FOLD_COEF. So {L:x, R:x} is the CANONICAL, round-trippable way to say "fold this stereo bus onto that one mono port" — the expression #142's per-leg model otherwise left the operator with no way to write.

      A LONE {L:x} is deliberately NOT a fold: #142/#275 ships per-leg routing so a stereo bus's L and R can feed SEPARATE physical outputs, and a lone leg is exactly that request.

      Parameters

      Returns string | undefined