Harrison Labs V2.0.2 manual Monitoring

21.0 Monitoring

Monitoring

"Monitoring" is the process of hearing the prerecorded tracks (and/or yourself) while the transport is playing. There are several options that control how Mixbus should monitor the inputs of each track.

Audio Hardware Does Monitoring

This option is best used with audio interfaces that have the ability to monitor the inputs to the interface. Some inter- faces come with a software application to control this while others may have a knob or button on the interface to allow direct monitoring. Additionally, other interfaces may need to be configured using the operating system’s vol- ume control application.

Mixbus Does Monitoring

This setting is also known as “software monitoring”. With this setting, when Mixbus is recording audio it will route the inputs of the record-enabled tracks through the tracks instead of playing back the previously recorded audio. This is best used on systems that work well with very low buffer sizes (256 at 44 or 48KHz or 128 at 96KHz). Very small buffer sizes are used to minimize the monitoring latency.

JACK Does Monitoring (Linux Systems Only)

On some systems JACK is able to directly route the audio inputs to the audio outputs. This combines the low-laten- cy of hardware monitoring with the features of software monitoring.

Tape-Machine Monitoring

This mode applies when using Mixbus or JACK to control the monitoring.

Mixbus Monitoring Modes Chart

The chart on the next page shows how the monitoring interacts with various settings in Mixbus.

Section 21.0 - Monitoring 44 Mixbus User Guide