1. Install DPC latency checker. If you are experiencing, pops, clicks, and dropouts, this is the first step to take. Download this free utility and read the documentation carefully. After you run the utility, you may need to disable wireless, webcams, network cards, etc.

2. In Windows, go to System properties>Advanced>Performance and set to "Adjust to Best Performance."

3. If running FireWire from a laptop, you may need to purchase a third-party FireWire adapter. Some built-in FireWire chips do not perform well. If you are running more than one AudioFire, you may need to purchase an additional FireWire adapter.

4. Run the ASIO FireWire Analyzer (if you have an AudioFire product). It comes with every driver. Make sure you download the Readme as well as this contains the documentation for this utility.

5. Your buffer size may be too small or too high. Recommendations:

44.1K or 48K sample rate: buffer 128 <-> 256

88.2K or 96K sample rate: buffer 256 <-> 480

176.4K or 192K sample rate: buffer 512 <-> 960

6. Make sure your software and OS have the latest updates. Check for BIOS updates as well.

7. Trim your system down to the bare essentials. Initially, work with only one device. Do not add additional devices until your first device is running smoothly. Do not run any plugins. Add plugins only after everything else is running correctly.

3. What PC motherboards and chipsets are compatible with my Echo hardware? [top]

The vast majority of motherboards and chipsets are compatible with the AudioFire, PCMCIA, ExpressCard, and PCI-based interfaces.

For more information about rare problematic motherboards, see this Tech Note. For a list of motherboards that have proven incompatible please go here.

If you would like to participate in our Compatible Motherboard and Chipset Survey, please go here.

To find out the maker of your motherboard or chipset, we recommend using a utility called Sandra.

4. What if I am having performance problems with my dual-core or multi-processor motherboard? [top]

We have had some reports of performance problems with dual-core and multi-processor machines. If you are experiencing decreased performance with either a dual-core or multi-processor motherboard, you might want to try this patch from Microsoft. (However we recommend that you update to SP3 if you are running XP.)

5. What FireWire card do you recommend for my AudioFire? [top]

We recommend more recently manufactured FireWire cards with a Texas Instruments chipset. If you are encountering problems with the built-in FireWire in your desktop or laptop, we suggest that you try a PCMCIA or ExpressCard FireWire card and disable the built-in FireWire.

The following FireWIre chipsets have produced good results:

Texas Instruments: TSB12LV26

Texas Instruments: TSB43AB23

Texas Instruments: PTSB41LV03 (This is an older chipset and does not work well at 192K with our AudioFire 12.)

Agere: FW323-06

Agere: FW323:05

We have had mixed results with the following FIreWire chipsets. Newer cards with these chipsets have produced better results:

Via: VT6306

Via: VT63061

6. What if my FireWire performance has decreased since installing Windows XP SP2? [top]

If you noticed a decrease in your FireWire performance after installing Windows XP Service Pack 2, try downloading this patch from Microsoft. (However we recommend that you update to SP3 if you are running XP.)

7. Is there an ExpressCard version of the Indigo io and the Indigo dj? [top]

Yes, we now have an ExpressCard line: Indigo IOx and Indigo DJx. PC drivers are available for XP, Vista & Windows 7 (32-bit and 64-bit). Mac OS X drivers support version 10.4 or later. Snow Leopard's 64-bit mode is not supported.

8. Is my hardware compatible with an Echo product? [top]

Each of our product families requires a different hardware interface to the computer. The interface required by each product family is described below.

AudioFire family: AudioFIre 2, AudioFire 4, AudioFire 8, AudioFire 8a, AudioFire Pre8, AudioFire 12 -- requires a 400 Mbps FireWire interface. (But 800 Mbps to 400 Mbps adapters should work fine.)

Indigo family: Indigo io, Indigo dj -- Requires a PCMCIA (Type II CardBus) slot. (ExpressCard slots will not work!)

Indigo DJx and IOx require ExpressCard slots. (We do not recommend PCMCIA-to-ExpressCard adapters).

Echo 3G and Echo24 family: Layla3G, Gina3G, MiaMIDI - Requires a PCI slot.* (We do not support PCI-e at this time.)

*All PCI products are compatible with 5V PCI, 3.3V PCI and PCI-X.

9. Is my software compatible with Echo products? [top]

All our products come with Core Audio, WDM, Direct Sound, MME, ASIO and GSIF* support.

*GSIF is not supported in 64-bit Windows XP, Vista or Windows 7.

10. What converters are used in Echo products? [top]

All our products use high quality 24-bit oversampling converters from AKM or Cirrus Logic. These are the converters used in our current product line:

Indigo DJx - AK4396

Indigo IOx - AK4620B

AudioFire 2 (Newer models) - AK4620B

AudioFire 2 (Older models) - AK4620A

AudioFire 4 (Newer models) - AK4620B

AudioFire 4 (Older models) - AK4620A

AudioFire 8 - CS4272

AudioFire 8a (Newer model w/ ADAT) - AK4620B

AudioFire Pre8 - AK4620B

AudioFire 12 (Newer models: FireWire ports' beveled edges pointing down) - AK4620B

AudioFire 12 (Older models: FireWire ports' beveled edges pointing up) - CS4272

Layla3G - CS4272

Gina3G - CS42426

Indigo dj - CS4392

Indigo io - CS4272

MiaMIDI - AK4528

11. What are the different Echo driver "families"? [top]

In order to speed driver development, each of our products is grouped into a driver family. With this system driver updates are carried out on entire families of products rather than having to update each product separately. Also, the driver for all of our PCI products is based on the same core of programming code. In this way, when improvements are made to one family, they are easily carried over to the families.

This list shows which products are in each driver family:

AudioFire family (echo1394) - AudioFire 2, AudioFire 4, AudioFire 8, AudioFire 8a, AudioFire Pre8, AudioFire 12

3G family (echo3g) - Layla3G, Gina3G

Indigo family (echondgo) - Indigo dj, Indigo io, Indigo, Indigo DJx, Indigo IOx

Echo24 family (echo24) - MiaMIDI, Mia, Layla24, Gina24, Mona

EchoGals family (echogals) - Layla(20), Gina(20), Darla24, Darla(20)*

*The EchoGals family is no longer supported. Drivers can be found on the Archived Windows Drivers page and the Archived Mac OS X Software page.

12. Are 64-bit Windows drivers available for all Echo products? [top]

64-bit Windows drivers are now available for the 3G, Indigo, Echo24 and AudioFire families. We will not be releasing 64-bit drivers for the EchoGals family. In addition, the Indigo DJx and Indigo IOx are not supported in Snow :Leopard's 64-bit mode.

13. Do you support Intel Macs? [top]

Yes! We are proud to fully support the Intel Mac platform.* The AudioFire line of products use Apple's built in FireWire driver, so support was built in since the very first Intel Mac was shipped! We also provide a software console which works in compatibility mode on Intel Mac. A Universal Binary version of the software console can be downloaded from our Mac OS X Software page. In addition, our Indigo DJx and Indigo IOx have Intel Mac support as well. However they are not supported for Snow Leopard's 64-bit mode.

*The hardware in the Intel Macs is incompatible with our PCI and Cardbus hardware.

14. What about Vista, Vista64, Windows 7 and Windows 7 64-bit support? [top]

Vista 32-bit and 64-bit drivers and Windows 7 32-bit and 64-bit drivers are now available for the AudioFire, 3G, Indigo and Echo24 families. We will not be releasing Vista 32-bit or 64-bit drivers or Windows 7 32-bit and 64-bit drivers for the EchoGals family.

15. What settings should I use in Sonar? [top]

SONAR supports ASIO and WDM/KS for low-latency access to audio hardware. The ASIO mode performs well and is straightforward to set up, requiring no special configuration. If you want to adjust the buffer size when Sonar is running, you do this in Options/Audio/General/ASIO Panel.

If you prefer, you can also use SONAR in WDM/KS mode. However, our AudioFire product line does not support WDM/KS mode. Here are the required settings for using SONAR with our other products in WDM/KS mode:

Within SONAR, go to Options/Audio.
• On the “General” tab, set “Audio Driver Bit Depth” to 24.
• On the “Advanced” tab, we suggest selecting “Trigger & Freewheel”
• On the “Driver Profiles” tab, uncheck “Access Driver In Mono”. Be sure to set “Stream > 16 bit data as” to “32-bit PCM, left justified”.

You may get a message that your audio devices are not compatible with the specified format; you may need to restart SONAR several times. Make sure each time that the settings are correct; once SONAR starts successfully without the “not compatible” message, be sure to run the Wave Profiler under Options/Audio/General.

Note: When installing a new hardware device, you may need to delete the aud.ini file. Deleting this file resets the settings back to their defaults and facilitates installing new or different hardware.

16. What settings should I use in Cubase? [top]

The settings in Cubase 3 and Cubase 4/5 are slightly different.

In Cubase 3, go to Devices -> Device Setup -> VST Audiobay. From the drop down menu choose "ASIO AudioFire" or "ASIO Echo PCI" depending on the product you are using. If it asks you if you want to switch, say yes. Then go to "ASIO AudioFIre" or "ASIO Echo PCI" under VST Audiobay. From here there is a "Control Panel" button from which you can control the buffer size. Next go to "VST Inputs" and hit the "Reset" button. Do the same under "VST Outputs." The final step is to go to Devices -> VST Connections. From here you set up your input and output busses. I would suggest starting from scratch and deleting the busses that are shown. Then add the busses you are going to use. Note that having all possible busses available may slow down performance. Now that you have set up the busses, you can access these busses from your tracks.

Cubase 4/5 is similar to Cubase 3, except that the "VST Inputs" and "VST Outputs" pages have been conflated with the "ASIO AudioFire" or "ASIO Echo PCI" page. You should reset the inputs and outputs from this page. You will still need to setup up your busses in "VST Connections." If you are not using all of the busses, it is recommended that you only set up the busses you are using, as this can affect performance in Cubase.

17. How do I set up the Echo console for the Indigo DJ and Indigo DJx correctly? [top]

The phones output is Analog 1-2 and the line output is Analog 3-4. In the Echo console, you can choose between the Analog 1-2 bus and the Analog 3-4 bus. In the Analog 1-2 bus make sure you have virtual output 3-4 muted. In the Analog 3-4 bus make sure you have the virtual output 1-2 muted. From within your audio application you can now assign your headphones output and your house (line) output.

18. What if my Indigo doesn't work with my laptop's ENE CardBus Controller? [top]

Some laptops with a PCMCIA controller made by ENE have been found to be incompatible with our Cardbus products (Indigo, Indigo io, Indigo dj, Layla24 Laptop, Mona Laptop). If you have such a laptop and are having audio playback problems with one of our products then this utility may help you. Go here to find out more information and download the utility. However, this utility may not work in Vista or Windows 7.

19. What if I have a product suggestion? [top]

If you have a new product suggestion or an idea for an improvement to an existing product, please email technical support. Please put in the subject line: "New Product Suggestion."