Bus Mixing / Routing

Bus tools treat a wide REAPER track as a collection of fixed-size source blocks. They mix those blocks without assuming that the channels form an ambisonic field.

Workflow

  1. Choose Group Matrix or Mixer Node Bus, then configure the REAPER track width, source-block size, and plugin pins.
  2. Route the result to the main speakers, a direct panner, a stereo or quad fold-down, or the intended downstream bus, then begin playback.
  3. Route complete blocks with matrix crosspoints or shape their levels with the node cursor.
  4. Verify block boundaries and channel identity before automating routes or node motion.
  5. Use an ambisonic bus processor instead when every source block is a complete ACN/SN3D field.

Group Matrix

Group Matrix 32/64 routes complete source blocks through a matrix. The 32-channel build supports stereo, 4-channel, and 8-channel groups; the 64-channel build supports 4-channel, 8-channel, and 16-channel groups. Every crosspoint moves the selected block together.

Group Matrix 64 with a dense route ceiling and an active moving pattern inside it.

Mixer Node Bus

Mixer Node Bus 128 represents source blocks as nodes around a movable cursor. Node radius, focus, influence, and position turn cursor motion into coordinated source gains, providing a relationship-based alternative to a conventional matrix.

Mixer Node Bus 128 with three spaced, overlapping nodes using different speaker geometries.

Routing Diagnostics

For channel-identity and level checks, insert Analyzer Meter 64, set ACTIVE to the bus width, and verify the expected lanes while checking the REAPER pin map. The former Passthrough Test has been retired because an identity processor added no diagnostic information of its own.

When every block is a complete third-order ACN/SN3D field, use Ambi Field / Bus Effects so all sixteen channels in each field remain locked.