rosetta

HDX or HD Native is not showing up in Pro Tools HD Playback Engine

If you have an Apogee Symphony I/O or Symphony I/O MkII (or a Rosetta/16x with X-HD card) and you’re using it in Pro Tools HD mode with an HDX card, HD Native card, or HD Native Thunderbolt and you’re not able to see HDX/HD Native as a possible selection in the Pro Tools Playback Engine, there are a few things to check:

 

  • If you’re using a Symphony I/O (mkI or mkII), confirm it is properly connected to the HD card/box and that the unit is in ‘Pro Tools HD’ mode.
  • Confirm that you have installed the ‘HD Driver’ for the version of Pro Tools you’re using (this is a separate install from the Pro Tools software). The installer is included in a separate folder in the Pro Tools installer package.
  • If you are using a current (12.6 and above) version or Pro Tools HD, you will need a ‘Digilink IO’ license to use 3rd-party hardware with your system. Click here for more information.

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

X-Firewire FAQ’s

The X-Firewire card is an option card that can be installed in supported Apogee converters. It turns the Apogee converter into an audio interface.

Q: What devices can use the X-Firewire option card?
A: The X-Firewire option card can be installed in the AD-16x, DA-16x, Rosetta-800, or Rosetta-200.

Note: Though mentioned in the Big Ben User’s Guide, X-Firewire is not supported in that product.


Q: What computer and operating systems can I connect to an X-Firewire equipped device?
A: You can connect an X-Firewire equipped device to any Mac computer from OSX version 10.3.9 and up, or a PC computer running 32-bit versions of Windows XP SP1 & SP2 (SP3 and later versions of Windows are not supported).


Q: How do I update the firmware?
A: Installation instructions are included with the firmware download file on our website (X-Firewire).

NOTE: There are different firmware versions depending in which product the X-Firewire card is installed. Make sure you download the correct one from our website.

-Special Note for AD-16x & DA-16x: Since these units can operate in a Standard or Advanced routing mode (Users Guide pg 8), each mode requires a different firmware version. See [this KB article] for more information on the Advanced Routing mode firmware.

The update is performed through the standard firewire connection to the computer.

    • On a mac, the firmware can only be updated via OSX 10.6.7 or earlier. If you are running OSX 10.6.8 or higher you will not be able to run the firmware updater application.
    • On a PC, you must have Windows XP SP2-32bit or earlier (SP3, 64-bit, and later versions of Windows are not supported).

Q: Will there be new software at some point that works with the newest version of OSX and Windows?
A: The X-Firewire option cards are discontinued & there is no further Apogee software development for it. That said: although there are some graphical (GUI) anomalies Maestro 1.9.13 appears to still be functional on newer versions of OSX.

NOTE: Currently, you can connect an X-Firewire equipped device to a mac computer and have it automatically work as an audio interface. This is because the X-Firewire card is class-compliant and doesn’t require the installation of additional software or drivers. This will continue to work as long as Apple maintains the Firewire CoreAudio Driver in their OS releases.

Signal showing up on wrong channels in Pro Tools with AD16x, DA16x, or Rosetta

This post describes a known issue and workaround with X-HD firmware version 3.0 and AD16x’s, DA16x’s, Rosettas.

 

Known Issue:

There is a known issue when using 2 or more units per port (and especially when the AD/DAs are in ‘Advanced Routing’) where the input/output channels can become misaligned and/or mirrored.

 

Workaround:

Toggling the sample-rate in Pro Tools by opening up sessions saved at different sample-rates and then going back to the session you were working on will usually get the units out of this state.

Updating X-HD Firmware for AD16x, DA16x, and Rosetta

To update an X-HD card, follow the instructions below in the EXACT ORDER

– Download the latest X-HD firmware updater app from our website. This contains both versions 3.0 and the older 2.07.

Download X-HD updater here.

– Make sure the updater app is not open.

– Disconnect the Interfaces from each other and the ProTools HD card(s)… this includes all the word-clock cables as well.

– Do a hardware reset of the Interface (for AD16x/DA16x- hold down the ‘down’ arrow button while powering up the unit. For Rosettas, hold down the ‘Sample-Rate’ button while powering up the unit).

– Make sure the Interface is set to ‘44.1k’, and clocked internally. The Rosettas will sometimes switch to 48k after powering up, so wait about 10 seconds after powering up a Rosetta and then manually switch it to 44.1k if it set itself to 48k.

– We recommend using only class-compliant MIDI interfaces, such as the Elektron TM-1. Connect the MIDI interface to the X-HD card. The LED on the X-HD should be green right now.

– Open the updater app and make sure you’ve selected ‘Avid Digital HD I/O’ and that the correct midi interface port is selected in the updater app (if you’re using ‘port A’, make sure ‘port A’ is selected)

– Run the updater. After a couple of seconds, you should see the LED’s on the X-HD card flashing red & green.

– After the update is finished, QUIT the updater app and power-cycle the Interface.

– Follow the same steps for each additional Interface.

– Reconnect everything and launch ProTools. The Apogee Interfaces should now be showing up as Avid Digital HD I/Os in the ProTools I/O Setup.

Differences in X-HD firmware versions

This post explains the differences in X-HD firmware versions and how the Apogee interfaces show up in different versions of Pro Tools, depending on the X-HD version.

X-HD version 3.0:

Download version 3.0 here.
All Apogee devices show up as digital Avid HD I/Os.

HD I/O’s are not compatible with any version of ProTools prior to HD9. We recommended using this X-HD firmware to users of HD-Native and HDX.

When an AD16x & a DA16x are daisy-chained in that order in Advanced Routing, the analog inputs of the AD and the analog outputs of the DA will both show up on ‘HD I/O- unit A’. The digital inputs of the DA and the digital outputs of the AD will both show up on ‘HD I/O- unit B’. This is so the hardware inserts work correctly- analog inputs line up with analog outputs.

The X-HD user’s guide on our website is current to version 2.07, but can be applied to version 3.0 if you replace “192 Digital I/O” with “HD I/O” and shows you all the different configurations and where the channels show up:

X-HD user’s guide

Known issue with version 3.0 firmware:

There is a known issue when using 2 or more units per port (and especially when the AD/DAs are in ‘Advanced Routing’) where the input/output channels can become misaligned and/or mirrored. Toggling the sample-rate in ProTools will usually get the units out of this state.

X-HD version 2.07:

All Apogee devices show up as 192 Digital I/O.

When an AD16x & DA16x are daisy-chained in that order in Advanced Routing, the analog inputs of the AD and the analog outputs of the DA will both show up on ‘192 Digital I/O – unit A’. The digital inputs of the DA and the digital outputs of the AD will both show up on ‘192 Digital I/O- unit B’. This is so the hardware inserts work correctly- analog inputs line up with analog outputs.

The X-HD user’s guide on our website is current to version 2.07 and shows you all the different configurations and where the channels show up:

X-HD user’s guide

Digidesign Digi192 units are not recommended for use with ProTools HD-Native, HDX, and software version HD 11 and up.

X-HD version 1.05

All Apogee devices show up as regular 192 I/O‘s.

Digidesign 192’s are not recommended for use with ProTools HD-Native, HDX, and any version of Pro Tools HD software from version 9 and up.

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!

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.