UAD Plug-Ins

Welcome to UA Support
How can we help?

Apollo Solo USB General Usage Notes

Console Application

Important: 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 a DAW, perform sample rate changes within the DAW settings (instead of the Console Settings window).

For important information related to sample rate changes with Windows WDM system audio, see this article.

 

UAD Resource Usage

Apollo Solo USB uses DSP and memory for its internal DSP mixer. Therefore, the UAD Meter & Control Panel program will show some DSP and memory usage even when UAD plug-ins are not in use.
 

UAD Presets

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 Solo USB for stable operation?

The audio interface hardware I/O portion of Apollo Solo USB 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 program to take advantage of Apollo Solo USB’s unique Realtime UAD Processing feature, where DAW I/O hardware buffering does not apply at all.

 

Comments