Symphony 64 ThunderBridge

Using Legacy interfaces (AD16x, DA16x, Rosetta) with Symphony64 card or Thunderbridge

Click here to download the latest Symphony Installer package

 

To update

  1. If youʼre installing this release over a previously installed version of Symphony 64/Maestro 1, you should run the Symphony64 Uninstaller before updating to the current Symphony Release installer. If youʼre installing this release over a previously installed version of Symphony I/O software, you should run the Symphony Uninstaller included with the current Symphony Release installer package. If youʼve installed both versions, you should run both uninstallers.
  2. Double-click the Symphony System Software Installer and follow the instructions provided by the installation application.
  3. No firmware updates are required – the Symphony IO Firmware Updater is for Symphony I/O users only.
  4. You will be required to re-start your computer once installation is complete.

After updating – After updating, verify that the Symphony Source setting (found in the Maestro 2 > System Setup tab and Audio MIDI Setup) is set to the appropriate Port setting:

  • If interfaces are connected only to Port 1, set Source to Port 1 Chs 1-32.
  • If interfaces are connected to both Ports 1-2, set Source to Ports 1-2 chs 1-64.

New Features – Legacy interfaces

  • The “A” icon that previously appeared in the Apple Menu bar has been removed – Look in Maestro 2ʼs Toolbar System Status display for system information.
  • To distinguish between an AD16X and DA16X when the interface is set to Advanced routing mode or a Rosetta 800 and 200, the setting Device Type is provided in Maestro 2 (Device Settings tab). This ensures that audio paths displayed in the Input and Output Routing tabs correspond to the actual hardware I/O. If neither a 16X Series in Advanced routing nor a Rosetta is connected, the Device Type drop down is not displayed.

Known issues – Legacy DA16X Interface

  • When a single DA16X is connected in Advanced routing mode, it will initially appear as an AD16X. Simply choose DA16X under Maestro 2ʻs Device Settings > Device Type drop down menu for the interface to be correctly detected.
  • When using Symphony I/O and legacy interfaces together, Routing tabs may not display the proper number of inputs and outputs. To work around this issue, restart the computer.
  • The AD16X may initially be detected as a Rosetta 800. Workaround – restart the computer.

Using Legacy Apogee Interfaces with OS X Lion & Maestro 2

  • Note that at the current time, the use of only 1 Symphony 64 card is supported regardless of the interface connected.
  • When connecting legacy Apogee interfaces to a Symphony 64 PCIe card or Thunderbridge, ensure that the interfaces are connected in a supported hardware combination, as listed below. With a Symphony 64 PCIe card or Thunderbridge, itʼs possible to connect one supported combination to each port.
  • When connecting both Symphony I/Os and legacy Apogee interfaces to a Symphony 64 PCIe card or Thunderbridge, connect the Symphony I/O to Port 1 Channels 1-32 port and legacy interfaces (in a supported combination) to the Port 2 Channels 1-64 port.
  • Legacy Apogee interfaces donʼt include Loop clock functionality (as found on Symphony I/O). Thus, when legacy interfaces are connected to a Symphony 64 PCIe card or Thunderbridge, the “Use Loop Sync” checkbox does not appear and Loop sync functionality is defeated on the Symphony I/O. Use one of the clock configurations described on pages 6-7 of the Symphony 64 Userʼs Guide v1.1.

Legacy Interface Supported Combinations

See the Symphony 64 Userʼs Guide v1.1 for connection diagrams

1 to 4 Rosetta 800s
1 to 4 Rosetta 200s
1 AD16X (standard routing) 1 AD16X (advanced routing) 2 AD16X (standard routing) 2 AD16X (advanced routing)

1 DA16X (standard routing) 1 DA16X (advanced routing) 2 DA16X (standard routing) 2 DA16X (advanced routing)

1 AD16X (standard routing) + 1 DA16X (standard routing)
1 AD16X (standard) + 1 DA16X (standard) + 1 AD16X (standard) + 1 DA16X (standard) 1 AD16X (advanced routing) + 1 DA16X (advanced routing)

1 Rosetta 800 + 1 AD16X (standard routing) 1 Rosetta 800 + 1 AD16X (advanced routing) 1 Rosetta 800 + 1 DA16X (standard routing) 1 Rosetta 800 + 1 DA16X (advanced routing)

1 AD16X (standard routing) + 1 Rosetta 800 1 AD16X (advanced routing) + 1 Rosetta 800 1 DA16X (standard routing) + 1 Rosetta 800 1 DA16X (advanced routing) + 1 Rosetta 800

1 AD16X (standard routing) + 1 DA16X (standard routing) + 1 Rosetta 800

Symphony I/O doesn’t show up in Maestro and exclamation mark (!) icon stays on

If you’re having an issue getting your Symphony I/O to show up properly in Apogee Maestro and the exclamation mark (!) icon stays on the front-panel, there are a few troubleshooting steps to check, depending on what Audio Interface Mode you’re using.

 

USB Audio mode

1. Confirm that your firmware and software is up to date and that the versions match. Click here and follow these instructions.

2. Confirm that your Symphony I/O is in ‘USB Audio’ mode by pushing in and holding on the right-side front-panel encoder and scrolling through the different modes until you get to ‘USB Audio’ and then push in on the encoder again to restart the unit in ‘USB Audio’ mode.

3. Confirm that you’re using the Apogee USB cable that was included with the Symphony I/O. Unplug USB cable and then plug back in to a different port and restart your Mac.

4. Power-cycle Symphony I/O.

 

Symphony mode (Symphony 64 PCIe or Thunderbridge)

1. Confirm that your firmware and software is up to date and that the versions match. Click here and follow these instructions.

2. Confirm that your Symphony I/O is in ‘Symphony’ mode by pushing in and holding on the right-side front-panel encoder and scrolling through the different modes until you get to ‘Symphony’ and then push in on the encoder again to restart the unit in ‘Symphony’ mode.

3. Launch Audio MIDI Setup (Applications> Utilities> Audio MIDI Setup). We recommend using Audio MIDI Setup instead of System Preferences Sound. Make sure that ‘Symphony64′ (PCIe or Thunderbridge) is selected in the left-side column. In the ‘Source’ menu on the right, choose the appropriate port selection depending on how many Symphony I/Os you have. If you have 1 unit, choose ‘Port 1: 32ch’… if you have 2 units, choose ‘Ports 1-2: 64Chs’. Quit Audio MIDI Setup and restart the computer.

4. If you’ve gone through the above steps and the exclamation mark (!) icon still remains on the front-panel, there is a chance that the PC-32 port on either the Symphony I/O and/or the Symphony 64 PCIe/Thunderbridge isn’t making a complete connection and needs to be cleaned with rubbing alcohol. Follow these instructions:

Disconnect the PC-32 cable (‘Symphony’ or ‘Digi-Link’ cable) and apply some rubbing alcohol (isopropyl) to the pins on the inside of the PC-32 cable’s connector end. Make sure to apply the alcohol to the top and bottom of the pins on the connector. Now plug in and unplug the cable to the ‘Main’ port of the Symphony I/O. Do this about 20 times, so the port gets clean. Now repeat this with the Main port on the Symphony 64 PCIe or Thunderbridge. After each port has been cleaned, reconnect the PC-32 cable, power-cycle the Symphony I/O, and restart your Mac.

When using Apogee interface with Cubase, Sonarworks, output volume level goes to max.

Symptom: When opening a session or selecting Apogee as the audio device, the output goes to full volume every time.

Solution: 

  • In Cubase, go to Devices > Device Setup > Control Panel > Core Audio Device Settings. Under Options, verify that set device attenuation to 0 dB is unchecked.

NOTE: In Cubase 10 and up, this setting is in Studio Setup > Control Panel

  • In Sonarworks, go to Systemwide settings and deselect the “Adjust output device gain checkbox.

How is this possible? All modern Apogee interfaces have input gain and output volume that are digitally controlled rather than an analog potentiometer that must be physically turned. The advantages of digital control are many:

  • Improved Sound Quality (turning the gain doesn’t cause a “scratchy” sound, and enables the advantages of our Step-Gain preamp technology)
  • Settings can be saved to presets that can be recalled later.
  • You can also control the output volume directly from the Mac’s Keyboard, Touchbar, or Volume icon in the Task Bar.

Cubase:  In Cubase this is called “Device Attenuation.”  The intent of this setting is to attenuate, or lower your volume, so you don’t get blasted.  When selecting any audio device with this setting turned on Cubase sets the device’s output volume to 0, since most simple sound cards have 0 as the lowest value.  Since your Apogee is rating the Outputs in digital decibels, where 0dBFS is the highest value, this setting will have the unfortunate opposite result, maxing out the volume.  Be sure to disable this setting to prevent getting blasted.

Sonarworks Reference 4:  This is a sound calibration software that many customers may have and forget is even running.  It has a setting to Auto adjust output device gain, or volume.

Please remember, many other softwares not listed here have these types of settings so be sure to check all the softwares on your computer!

Symphony I/O Release 5 System Requirements

Symphony I/O Release 5 Requirements

 

 Click here to download Symphony I/O Release 5

Symphony Audio Interface Mode

Requirements to connect Symphony I/O to Apogee Symphony 64 or Mobile PCI cards:

  • Apogee Symphony 64 Thunderbridge or Symphony 64 PCIe card (sold separately)
  • OS X 10.8.5, 10.9.5, and 10.10 and higher (64-bit and 32-bit kernel modes)
  • 2GB memory required, 4 GB recommended

 

Pro Tools HD Audio Interface Mode

A Symphony I/O based Pro Tools system consists of two independent computer connections: audio (to a Pro Tools HD PCI card) and software control (via USB to an Intel Mac running Maestro 2). In the case where PCI cards are installed in a PowerPC Mac or Windows computer, it’s possible to run Maestro from a separate Intel Mac, such as Mac Mini or MacBook.

Note:

Running Symphony I/O in Pro Tools HD mode on a PowerPC Mac requires an older firmware version. You can request this older firmware by emailing: betafeedback@apogeedigital.com. Only the 8×8, 16 Analog In/Digital Out, and 16 Digital In/Analog Out modules are compatible with versions of Pro Tools HD older than version 9. The 16×16 Analog In/Out and 2×6 modules are only compatible with Pro Tools HD versions 9 and above.

 

Requirements to connect Symphony I/O to Avid Pro Tools PCI Cards:

  • Avid Pro Tools HDX, HD Native or HD Core/Accel/Process card installed in a computer in accordance with the Pro Tools HD Compatibility Grids, available at www.avid.com
  • Pro Tools 8.1 (requires older Symphony I/O firmware), 9.0 or greater, 10.0 or greater, 11.0 or greater

Requirements to run Apogee Maestro software, to control Symphony I/O via USB:

  • OS X 10.8.5, 10.9.5, and 10.10 and higher (64-bit and 32-bit kernel modes)
  • Apple Intel Mac

USB Audio Interface Mode

 

Requirements to connect Symphony I/O as a USB audio interface:

  • OS X 10.8.5, 10.9.5, and 10.10 and higher (64-bit and 32-bit kernel modes)
  • Apple Intel Mac – 2GB memory required, 4 GB recommended

 

Standalone Audio Interface Mode

In Standalone audio interface mode, all audio connections are made using the standard analog and digital i/o found on the I/O Module(s). For software control, connects Symphony I/O’s USB port to a Mac.

 

Requirements to run Apogee Maestro software, to control Symphony I/O via USB:

  • OS X 10.8.5, 10.9.5, and 10.10 and higher (64-bit and 32-bit kernel modes)
  • Apple Intel Mac

Symphony I/O Firmware and Software Installer Release 5

 

Download Release 5 here.

 

16x and Rosetta series users, please consult the Legacy Interface Release Notes.

 

Who should update?

Users running or upgrading to OSX 10.10 Yosemite
New Users setting up their Symphony system for the first time
Users on 10.8.5 or 10.9.5 who would like the new Features and bug fixes
NOTE: Symphony Users who are currently running 10.8.4 or lower and don’t plan to update their OSX should not update to Release 5
New Features
Compatibility with Mac OS X Yosemite and Mavericks (10.10 and 10.9)
with continued support back to OSX 10.8.5
Up to 3 Selectable Speaker Sets can be toggled and controlled from Maestro
Command-click lets you enable multiple speaker sets at the same time
Dim functionality for Main Outputs and Headphone outputs
Sum To Mono functionality for Main Outputs and Headphone outputs
Various bug fixes

 

Before you update

  • Please note critical Maestro settings such as Trim levels before performing a firmware update.Parameters will be reset after installing new software.
  • Unplug headphones and mute speaker volume before updating firmware.

 

To update

 

After updating – After updating, verify the following settings;

  • Audio Interface Mode – press and hold the right hand encoder to verify that Symphony I/O is set to the desired audio interface mode.
  • If using the Symphony 64 card, verify that the Symphony Source setting (found in the Maestro 2 > System Setup tab and Audio MIDI Setup) is set to the appropriate Symphony 64 Port setting:

! ! If interfaces are connected only to Port 1, set Source to Port 1: 32ch.
! ! If interfaces are connected to both Ports 1-2, set Source to Port 1-2: 64ch.

  • Check that Output settings such as Speaker setting and level and headphone level and mute are set as expected.

 

 

 

How do I use the custom I/O labels in Logic?

For Logic 9 and lower:

With your Apogee devive selected as the input/output in Logic’s Audio Preferences, go to the “Options” menu and select “Audio” and then “I/O Labels”. Now you can select the custom Apogee labels for your device.

For Logic X and higher:

  • Go to Logic’s Mix menu at the top of the screen and select “I/O Labels…”
  • There are several columns: Channel, Provided by Driver, User, Long, & Short.
  • To use the labels provided by the Ensemble:
    • Click the button in the Provided by Driver column.
  • To enter your own custom label:
    • Click the button in the User column.
    • Double click the “-” in the Long column, type in a new name, then press Return on your Apple keyboard

Here’s a video showing this process: https://apogeedigital.com/blog/apogee-element-tutorial-enable-logics-io-labels

How do I set my software’s I/O buffer?

The I/O Buffer setting found in most audio software is one of the most crucial, but often ignored, settings in a Mac-based recording system. When choosing a buffer setting, a compromise between the latency through the application and the amount of computer processor power accessible to the application must be made.Latency– the slight delay between the moment you play a note and hear it in your headphones after conversion and processing.

A lower buffer setting results in lower latency but less available processing power. If the application can’t access enough processor power, processor overruns may occur, resulting in audible clicks and pops or error messages that interrupt playback and recording. A higher buffer setting, on the other hand, results in greater amount of accessible processor power (i.e. less chance of overruns) but increases the latency. Determining the best setting requires some trial-and-error in order to find the best compromise.

Keep in mind that as tracks and plug-ins are added to a software session, processor requirements increase. Thus, the buffer setting that works during the early stages of a session might result in processor overruns during later stages. The best strategy is to set the buffer to a lower setting during recording and accept certain limitations on plug-in usage, and then raise the buffer during mixing to utilize the computer’s full processor power when latency isn’t an issue. With the processing power of today’s Macs, you may find that adjustment of the buffer isn’t necessary, and you can leave it at a setting for low latency and still access a sufficient amount of processing power when adding tracks and plug-ins. If you do encounter clicks, pops or software errors, don’t hesitate to experiment with the buffer setting. Please consult the section on Working with GarageBand, Logic and Mainstage to determine how to se the I/O buffer setting is found in your audio application.