Important (Apollo Twin DUO and QUAD only): UAD plug-ins within Console use DSP differently than when used within a DAW. To maintain the lowest possible input latency for Realtime UAD Processing, UAD plug-ins on a single Console input channel strip must fit on one DSP core (or two cores if Channel DSP Pairing is enabled). This is why the “DSP resources were exceeded” message can appear when stacking DSP-intensive UAD plug-ins within an input channel strip, even if the UAD meters indicate DSP resources are still available.For related information, review the Managing DSP Resources article.
- Session, plug-in, and I/O preset files saved within Console will not be saved if the "/" (forward slash), "\" (back slash), or "?" (question mark) characters are in the filename. Avoid these and other special characters when saving Console presets of any type.
Sample Rate Changes
- For optimum results when using Console without a DAW, perform sample rate changes within the Console application.
- For optimum results when using a DAW, perform sample rate changes within the DAW itself.
- For optimum results when Apollo's current sample rate is different from the sample rate set within a DAW session, change Apollo's sample rate within Console to match the sample rate of the DAW session before loading the DAW session.
UAD Resource Usage
- Apollo Twin uses DSP and memory for its internal DSP mixer. Therefore, the UAD Meter & Control Panel application will show some DSP and memory usage even when UAD plug-ins are not in use.
- When logged into the computer under an account that does not have administrator privileges, saving UAD preset files via the UAD Toolbar will result in an "Unable to save preset file" dialog. If this occurs, either log in with an administrator account, or use the DAW's preset management tools.
What is the lowest hardware buffer setting I can use with Apollo Twin for stable operation?
The audio interface hardware I/O portion of Apollo Twin can run at any hardware buffer setting that is stable within the DAW itself. Results may vary as a result of how much the DAW session stresses the computer system. This can be influenced by:
- Session track count and sample rate
- How many processor-intensive native plug-ins (such as virtual instruments, convolution reverbs, etc.) are in the session
- Processor type, speed, and overall power of the computer
Of course, for the lowest possible latency when monitoring live inputs, we recommend using the included Console application to take advantage of Apollo Twin’s unique Realtime UAD Processing feature, where DAW I/O buffering does not apply at all.
System sleep is compatible with the latest Apollo Thunderbolt software. However, disabling sleep when using DAW software is generally recommended. For optimum results when using Apollo Twin with DAW software, follow these guidelines:
- Disable sleep:
On Mac: Open the Energy Saver panel within System Preferences* and drag the “Computer Sleep” slider (if present) to “Never” (the far right position).
On Windows: Go to Control Panel > Power Options > Change Plan Settings and select "Never" from the "Put the computer to sleep" menu(s).
- Before sleeping the system, quit any DAW software using UAD plug-ins.
- If UAD-2 Satellite FireWire is connected, system sleep MUST be disabled. Sleep is not compatible with UAD FireWire devices (UAD-2 Satellite Thunderbolt is compatible with system sleep).
*To access System Preferences, click the Apple icon in the OS X Menu Bar (upper left of screen) then select the application from the drop menu.