• In AMP (advanced multiprocessing) mode, turning on a UAD plugin may cause the computer to hang when using certain ASIO drivers. This does not occur in regular MP mode.
  
  At the time of this writing, some drivers we've tested which induce this problem include MOTU ASIO (PCI and Firewire), the Mobile I/O, and also RME when set to "Alternate ASIO Mode" (there may be others as well).
  
  
• When AMP mode is enabled, the host CPU load for UAD plugins will approximately double. In some cases, the host load can be higher, for example when using a small ASIO buffer size. If you need to use ASIO buffer sizes lower than 512 samples, AMP mode is generally not recommended. Note: This only applies to AMP mode (not "regular" MP mode).
  
  
• Cubase appears to occasionally have random audio dropouts on faster machines when MP or AMP mode is active, even without any UAD plugins active (although activating plugins does seem to exacerbate the problem). This may also depend on the ASIO driver.
  
  
• In order for UAD keyboard shortcuts to behave as expected, the user preference Edit>Preferences>Key Commands>"Plug Ins receive key commands" should be selected.

Emagic Logic Audio

In Logic Audio versions prior to 6.1.1, issues can occur when UAD Powered Plug-Ins are used where their input is derived from any source in a "live mode". This includes record-enabled audio tracks, selected Audio Instrument tracks, or any busses or outputs that receive input from such sources. Since version Logic Audio version 5.2.0, a workaround is available that allows you to insert UAD plugins on any object, regardless of its "live mode" status. For more information click the "Support Report" button in the May issue of the UA Webzine at http://www.uaudio.com/webzine/may/index.html.

Workaround (Logic v5.2.0 – v6.1.0 only): Before inserting a UAD plugin on any object (including all audio tracks, Audio Instrument tracks, busses, and outputs), do the following:

Insert a Logic I/O Helper plugin. This is available within the plugin insert menu at Logic>Helper>I/O.


In the I/O plugin editor window, select a valid input and output channel (not "---", which is the default).


Disable the I/O plugin.


Important: Insert the I/O Helper BEFORE inserting a UAD plugin!

• Logic Audio may run all UAD Powered Plug-Ins at unusually high latencies. UAD latency is determined by the larger of the hardware buffer size and the Process Buffer Range setting within Logic (the current latency is displayed in the UAD Meter System Information window).
  
  
  • In Logic Audio 4.x, uncheck the "Larger Process Buffer" option to minimize internal latency.
    
    
  • Logic Audio since version 5.2 has the "Process Buffer Range" option. Smaller values may decrease internal latency, but will increase the host CPU load slightly as well (latency is determined by the larger of the hardware buffer size and the Process Buffer Range setting so reducing the Process Buffer Range may not reduce latency).
    
    
• Logic Audio does not release UAD DSP resources when UAD plugins are bypassed, or when the "freeze" function is used on tracks with UAD plugins.
  
  
• UAD plugin settings presets may not reload correctly if the preset is saved to a location other than Logic's default save location.
  
  Workaround: Save UAD plugin presets only to Logic's default save location in the preset save dialog.

BIAS

(Peak)Use version 2.63 or higher for optimum performance.


(Peak) In versions below 3.0, subfolders within the VSTplugins folder are not supported. Move the individual UAD plugin files that are inside the Powered Plug-Ins folder (inside the Vstplugins folder) up a level to the root of the Vstplugins folder.


(Peak) Selecting RealVerb Pro presets using Peak’s preset pull-down menu (at the bottom of the plugin window) causes all preset edits in the bank to be reset to their factory defaults.

Workaround: Use the preset menu built into the Realverb Pro interface instead of the Peak preset menu.


(Peak, Vbox) Text entry is not supported.


(Peak) Plugins are instantiated in stereo mode on monophonic files. Only the left channel is processed and returned, which may cause unexpected results.

Workaround: Convert the mono file to stereo, or use the mono(m) version of the UAD plugin.


(Deck) Using UAD plugins inside Vbox is not recommended in Deck. Instead, use UAD plugins directly, without being contained inside Vbox.

TC Spark

• If you get clicks in the output when adjusting a UAD plugin parameter (after releasing the mouse from dragging the control for the parameter), turn off "Undo/Redo on Plug-In parameter" in FXMachine preferences.
  
  
• In versions prior to 2.6, when mixing down to a new file you may experience dropouts if more than one UAD plugin is active in the FXMachine.
  
  Workaround: Place all UAD plugins in a single Spark FXMachine sub-plugin inside the master FXMachine.
  
  
• In version 2.6 and higher, when mixing down to a new file you may experience dropouts if the buffer size is greater than 2048 and you have UAD plugins contained within an FXMachine sub-plugin (as described in the previous bullet).
  
  Workaround: Use buffer sizes smaller than 2048 when mixing down, OR, do not place any UAD plugins inside Spark FXMachine sub-plugins.