Apollo Twin USB - Known Issues

 

Removing RealVerb Pro causes Console to become unresponsive

Symptom

If RealVerb Pro is loaded in Console and Console’s preset manager is used to load a RealVerb Pro preset, subsequently removing RealVerb Pro may cause Console to become unresponsive.

Solution

Use either the UAD Toolbar (at bottom of plug-in interface) or the preset menu within the RealVerb Pro interface to load presets instead of Console’s preset manager.

Important: To avoid losing unsaved changes, save the Console session before removing RealVerb Pro from Console.

 

Close DAW before starting UAD plug-in Demo

Symptom

If a UAD plug-in’s trial period is starting by clicking its START DEMO button when a DAW program is open, errors and/or audio artifacts may occur.

Solution

Close all DAW programs before clicking the START DEMO button for any UAD plug-in.

Important: To avoid losing unsaved changes, save the DAW session and close the DAW program before starting any UAD plug-in demo trial period.

Note: If the DAW was open when a demo trial period was started and audio artifacts persist, power off then power on Apollo Twin USB.

 

Avid Pro Tools unresponsive at buffer sizes higher than 2048

Symptom

If Apollo Twin USB’s BUFFER SIZE is set to a value of 2048 or higher, Pro Tools becomes unresponsive when opened.

Solution

In the Console Settings > Hardware panel within the Console program, set the BUFFER SIZE value to 1024 or lower before opening Pro Tools.

 

Install hardware before software

For optimum results, connect and power Apollo Twin USB before installing the UAD Powered Plug-Ins software. Installing software first will not cause issues, however additional installation steps will be required.

For help with setup, watch the Apollo Twin USB getting started video.

Note: Installing the software after connecting and powering the hardware is different than the ordering indicated on the Getting Started URL card provided in the retail package.

  

Optical Input Channel Availability

The Apollo Twin optical port accepts either S/PDIF or ADAT input. Although S/PDIF and ADAT channel numbers and names are always displayed in the DAW, the optical inputs that are actually available for routing in the DAW depend on the DIGITAL INPUT setting in the Hardware panel within the Console Settings window.

ADAT inputs are unavailable in S/PDIF input mode, and S/PDIF inputs are unavailable in ADAT input mode.

 

Initializing the computer and Apollo Twin USB (Booting at the same time)

Symptom

If both the computer and Apollo Twin USB are initialized at the same time (for example, if power is applied to both at the same time and/or when power is applied to Apollo Twin USB as the computer is restarting), Apollo Twin USB may not be recognized when the computer is finished starting.

Solution

Power off then power on Apollo Twin USB again after the computer is finished starting.

Note: For optimum results, connect and power Apollo Twin USB before starting the computer and/or installing the software.

 

MIDI input device cannot be used concurrently with both Console and DAW

Note: This symptom is not caused by Apollo or Console. It is a function of the MIDI interface’s device driver and the Windows operating system.

Symptom

A MIDI input device is not recognized by the Console program when a DAW is open, or the MIDI input device is not recognized by the DAW program when Console is open.

Solution

Follow the steps below to allow the MIDI input device to be used with Console or the DAW.

To allow use of a MIDI device in the DAW program:

  1. If the DAW program is open, save the session then close the DAW program.
  2. In the Console Settings > MIDI panel within the Console program, set the DEVICE value to NONE.
  3. The DAW program can be now be reopened. Select the MIDI device in the DAW settings if it was not previously set.

To allow use of a MIDI device in the Console program:

  1. If the DAW program is open, save the session then close the DAW program.
  2. Select the MIDI device in the Console Settings > MIDI panel within the Console program.
  3. The DAW program can be now be reopened. Console will have exclusive use of the MIDI device until the device is deselected in the Console Settings > MIDI panel.

Background

A MIDI controller connected to a computer’s MIDI interface can be used to control specific Console features such as Console’s tempo and/or keyboard input for UAD plug-ins (for example, pitch control of the Eventide H910 Harmonizer). The same controller could be used to control features in a DAW such as virtual instruments, automation, etc.However, controlling both programs at the same time with a single MIDI input device is usually not possible.

If the MIDI interface’s device driver does not have multi-client support (most don’t), the MIDI device cannot be used to control more than one software program simultaneously. The first program that sees the MIDI device will have exclusive use of the device until it is released by the program.

DAW programs typically release the MIDI device when the program is closed. However, Console retains exclusive control of the MIDI device even after it is closed. Therefore the device must be released in the Console Settings > MIDI panel for it to be available to the DAW.

 

 

 

 


 

Was this article helpful?
1 out of 2 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk