Apollo Software Manual v7.0 - zZounds.com

Using Apollo with a DAW (without Console)When used with a DAW but without the Console application (or Console Recall plug-in),the DAW controls all signal I/O routing, software monitoring, and DSP-accelerated UADPowered Plug-Ins processing.Note: Apollo, like other UAD devices, can only load UAD Powered Plug-Ins whichare specifically designed to run on UAD DSP accelerators. Host-based “native”plug-ins cannot run on the UAD DSP.Using a DAW without Console is a typical workflow during mixdown, where low-latencymonitoring is not required and buffering latency is not an issue because the tracks arealready recorded. When recording new tracks, the DAW+Console workflow (following section)is recommended.In this scenario, Apollo functions as two “separate” devices: an audio interface, and aUAD-2 DSP accelerator:1. Audio Interface – The DAW accesses and routes Apollo’s audio interface I/O viathe Core Audio or ASIO device drivers. Audio I/O latency is determined by the I/OBuffer Size setting.2. UAD-2 DSP Accelerator – The DAW controls Apollo’s internal UAD-2 DSP via UADplug-ins in VST, RTAS, or Audio Units format that are loaded within the DAW.Buffering is used for UAD plug-ins because data from the DAW must be shuttledover FireWire or Thunderbolt to/from Apollo’s DSP.Accessing Apollo’s I/O in a DAWSpecifying the audio interface deviceTo access Apollo’s I/O within a DAW, the DAW’s audio engine must be configured to useApollo as the audio interface device. Specific instructions vary by DAW; consult the DAWdocumentation for specifics. The I/O Buffer Size setting, which determines the overallDAW I/O latency, is usually set in the same window.See “Setting the I/O in the audio software application” on page 71 for an example.Apollo Software Manual75Chapter 5: Working With Apollo