Apollo Thunderbolt Software Manual Working With Apollo 31
Using Apollo Concurrently with a DAW and Console
Console is used concurrently with a DAW when low-latency monitoring and/or recording
of Apollo’s inputs or mix buses with (or without) Realtime UAD Processing is desired.
This workflow completely eliminates the I/O buffering latencies associated with software
monitoring.
In this scenario, Console is used to control all input monitoring and Realtime UAD
Processing when recording, and the DAW’s software monitoring feature should be
disabled.
Software Monitoring versus Hardware Monitoring
Software monitoring (listening to live inputs via the DAW mixer) has discernible latency
due to audio interface I/O buffering. Hardware monitoring via an audio interface’s
internal DSP mixer (e.g., Apollo’s Console application) does not have discernible latency,
because the live audio is internally routed directly from the inputs to the outputs without
DAW I/O buffering (see Latency Basics for detailed explanations).
Monitoring with Console
The primary function of Console is monitoring of Apollo’s inputs during live performance,
with (or without) Realtime UAD Processing. When used with a DAW, Console is used as a
monitor mixer that functions separately from the DAW’s software monitoring mixer.
Disable Software Monitoring in the DAW when using Console
When Console is used for live input monitoring with a DAW, the DAW’s software
monitoring feature should be disabled. If it isn’t, phasing and/or doubling of the
monitored signal(s) will occur, because the input signal is being heard twice – first from
the low-latency DSP mix (Console) and shortly thereafter from the higher latency software
mix (DAW).
Important: To eliminate doubled signals, disable software monitoring in the DAW
when Console is used to monitor Apollo’s inputs. Refer to the DAW documentation
for specific instructions on how to defeat software monitoring in the DAW.
To Next Page
Loading...
Need help?
General
