Legacy Products

Can I use Symphony I/O with AD16x, DA16x, or Rosetta 200/800 when connected to Symphony64?

Yes, Symphony I/O can be used with Legacy interfaces if you’re using the most current release.  Please note the following instructions to do so:

  1. The rule for Symphony I/O connection is- “1 Symphony I/O per port”, so that means the supported configuration is 1 Symphony I/O on port 1 of the Symphony64 Thunderbridge or PCIe card and any Legacy interfaces on port 2 of the Symphony64 Thunderbridge or PCIe card. You can’t daisy-chain Symphony I/O’s, but you can daisy-chain Legacy interfaces.
  2. First, make sure your Legacy interface (AD16x, DA16x, Rosetta 200, Rosetta 800) have an X-Symphony option card properly installed with the current X-Symphony firmware (version 2.7)
  3. Connect your Symphony I/O directly to your computer’s USB ports- don’t use a hub. Power up the Symphony I/O.
  4. Download the latest Symphony I/O Release package from our website and follow these instructions.
  5. After the firmware has successfully updated, connect the Symphony I/O to the first port of the Symphony64 Thunderbridge or PCIe card using a PC-32 cable. Connect one end of the cable to the “main port” on the back of the first Symphony I/O and the other end of the cable to the 1st port (on the left) of the Symphony64 Thunderbridge or PCIe card.
  6. Connect the 1st Legacy device to the 2nd port of the Symphony64 Thunderbridge or PCIe card using a PC-32 cable. Connect one end of the cable to the “primary port” on the back of the 1st Legacy device and the other end of the cable to the 2nd port (on the right) of the Symphony64 Thunderbridge or PCIe card. Chain any additional Legacy devices using the “primary” and “expansion” ports.
  7. If you’re using multiple Legacy devices, send the Word Clock output of the 1st Legacy device to the Word Clock input of the 2nd Legacy device and so on, using BNC cables and t-connectors, if necessary.
  8. Send the Word Clock output of the Symphony I/O to the Word Clock input of the 1st Legacy device using a BNC cable.
  9. Make sure the Symphony I/O is set for “SYM AIM” (Symphony Audio Interface Mode) by pressing in and holding on the right side encoder on the front-panel until it brings you to the AIM menu. If it says “Symphony”, it’s already in SYM AIM… you can just push in on the encoder again to exit the menu. If not, scroll through the menu until it says “Symphony” and then push in on the encoder again. The unit will power down and restart itself in SYM AIM.
  10. Power up all the Legacy devices and make sure they’re set for “External Word Clock” as their clock source.
  11. Run the software installer included in the Release download. Restart the computer.
  12. After the computer restarts, open up “Audio MIDI Setup” (Applications> Utilities> Audio MIDI Setup). Select “Symphony64” in the left-hand device column. Make sure it’s selected as your computer’s default i/o. The speaker and microphone icons should appear next to it… if they don’t, click on the drop-down menu below with the “gear” icon and select both “Use this device for sound input” and “Use this device for sound output”.
  13. With “Symphony64” selected in Audio MIDI Setup, go to the center part of the Audio MIDI Setup window and set the “Source” drop-down menu to ‘Ports 1-2: 64Chs’. Quit Audio MIDI Setup and restart your computer.
  14. After the computer restarts, wait for the system to configure- the exclamation mark (!) icon on the front-panel of Symphony I/O will eventually go away and the Legacy units will switch to “Ext” clocking… After this happens, launch Maestro2 and confirm that all the interfaces show up properly. If a device is showing up as the wrong unit, such as a DA16x in Advanced routing showing up as an AD16x,  go to the “Device Settings” tab in Maestro2, highlight the device in the left-hand device column and then select “DA16x” in the “Device Type” drop-down menu. Quit Maestro and restart the computer. If an AD16x in standard routing is showing up as a Rosetta800, quit Maestro and restart the computer.

How do I calibrate my Rosetta?

The Rosetta, by default, is calibrated for -16 dBFS. To calibrate the Rosetta, press and hold the SoftLimit button until it begins to flash. Send a +4 analog tone into the analog inputs. The metering in calibration mode now reflects -21 dBFS to -11 dBFS. To calibrate to -12 dBFS, turn the A/D calibration trimpots. As the level increases one LED, which equals one dBFS, the over light will turn on indicating you have achieved the next level up in dBFS. Each LED you light up will cause the over light to come on and as you increase the gain the over LED will go off until the next LED is lit up. When you get to the desired level, stop as soon as the over LED lights up.

How do I switch between ADAT and S/PDIF optical?

By default, the Rosetta is set for ADAT optical. If you want to change it to S/PDIF optical, hold down the “Sample Rate (AES FMT)” button. On the Source to Digital Outputs, the ADAT and AES LEDs should be lit. Hit the “Source (SRC)” button to change it to “S/P OPT.” If you want to go back to ADAT, just do the exact same procedure again. Keep in mind that if you reset the Rosetta 200 by holding down the sample rate button when powering the unit on, it will reset the optical format to ADAT.

I can’t get SRC to work properly with an option card installed

It is not possible to use SRC with an option card installed in the Rosetta 200. When an option card is installed, it is not possible to set the Rosetta 200 to a different sample rate than the session sample rate of the DAW. This makes it impossible to send audio out of the DAW at one sample rate and then send it out one of the Rosetta 200’s digital outputs at a different sample rate using SRC.

X-HD Legacy Interfaces with Avid Pro Tools HDX PCIe

With the latest firmware update (v. 3.00), any X-HD equipped Apogee interface (X-Series or Rosetta Series) emulate an Avid HD I/O interface. This provides connectivity to Avid’s Pro Tools HDX PCIe system and compatibility with Pro Tools HD 10 and 11.


For more info, please see the X-HD Version 3.00 Release Notes.

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.