Home » Support » Knowledge Base » Knowledge Base

Knowledge Base

Pops, clicks, crackles, dropouts, or distortion – FireWire Troubleshooting Guide
Text size [-] [+]

When using a FireWire audio interface with your computer, there are a variety of things that can result in pops, clicks, crackles, dropouts, or distortion during playback and recording. This article offers troubleshooting steps and suggestions that should resolve the majority of these problems. 

General

System Requirements

Digital audio recording places significant demands on your computer system’s resources.  For the best user experience it is recommended to use a computer system that not only meets, but exceeds the minimum system requirements.  Be sure to check the system requirements for your software as they are likely to be higher than your M-Audio device.


Latest Drivers

Do you have the latest M-Audio device drivers installed for your Operating System?  M-Audio regularly updates its drivers and it is likely that there is a newer driver available than the one included with your device.  The latest driver releases for M-Audio products are available on our drivers/updates page.  If you are unsure of your exact OS version, please see this article.


Bus Power vs. Power Supply

With the exception of the ProFire 2626, ProjectMix I/O and NRV10, M-Audio FireWire interfaces can get their power from the FireWire (1394) bus*.  When bus power is present, using the included AC power adapter can cause these issues (pops, clicks, distortion, etc).  The power adapter provided with the FireWire device is only to be used if you are using a computer which does NOT send power via the FireWire cable; such as when using the 4-pin FireWire connection found on most PC laptops.  For more information please see this article.

* Note: the ProFire 2626, ProjectMix I/O and NRV10 are exceptions; these devices are not powered by your computer's FireWire bus, and require the included power adapter at all times.

Other FireWire Devices

Do you have another FireWire device (e.g. FireWire hard drive) connected to the computer?  If so, disconnect the device(s) and test recording and/or playback.  Connecting other FireWire hard drives to the same FireWire bus (including FW800) as your M-Audio interface can result in pops and clicks.  Start by testing with all other FireWire devices disconnected to see if the problem disappears.

Other devices should be connected to the second FireWire port on your M-Audio interface (if available*); alternatively you can connect your M-Audio interface to a FireWire expansion card with a Texas Instruments (TI) chipset and run it on a separate FireWire bus to eliminate this conflict.  It may be necessary to test the FireWire expansion card in different expansion slots (if available).  If you have an external hard drive that also offers USB 2.0 connectivity, this can be used as an alternative.

 * Excludes Ozonic, ProjectMix I/O, and ProFire Lightbridge

 
Hum/Ground Loop/Electrical Noise

If you experience a constant humming or low frequency buzzing you probably have a ground loop.  Try connecting all devices to the same power outlet on the wall.  If you have a laptop, disconnect its power supply to see if the hum/buzz disappears.  Please see this guide for assistance with troubleshooting ground loops.


Digital Synchronization (Clocking)

When recording with the S/PDIF input or output on your M-Audio FireWire interface, synchronization or clocking problems can result in pops, clicks, or distorted audio.  Test recording and playback with the analog inputs/outputs first.  If you experience the same problems, your issue is not with the S/PDIF connection.  If the problem goes away when using the analog I/O, try the following steps to ensure your digital devices are properly synchronized

  • Although standard RCA cables may appear to work for S/PDIF connections, they are not reliable.  Only use 75ohm coaxial cables specifically designed for digital audio
  • When recording to the S/PDIF input of your M-Audio FireWire interface, you must set the device for external S/PDIF sync on the hardware tab of the control panel.  This will synchronize the M-Audio device with your external digital device
    • Make sure the sample rate on your external device matches the sample rate in the M-Audio control panel and your recording software
  • When playing audio through the M-Audio device's S/PDIF output, your external digital device must be configured to lock or synchronize externally to the clock signal being sent by the M-Audio interface
    • Make sure the sample rate on your external device matches the sample rate in the M-Audio control panel and your recording software


Faulty Cables

Test with a different FireWire cable.  Faulty cables are often times the source of many problems.  Loose connections can result in crackles and interruptions in the audio.  Check the connections of your audio cables to ensure they are secured.    If you hear noise when moving the cables, they may be faulty.  Test with different audio cables.


Below are additional troubleshooting steps specific to Mac and Windows.



Windows (XP, Vista, & Windows 7)


Buffer Size

Buffers are used to help keep audio hardware and software running smoothly by processing audio in groups of samples rather than one sample at a time. Due to variations between computer hardware and software, it is impossible to recommend a single optimum setting for all systems.  It may be necessary to experiment with various settings until you find the best buffer size for your system.  The goal of setting a buffer size is to reduce it as much as possible without hearing any clicks, pops, or other glitches. If the buffer size is too small, the computer will not be able to make all the required audio calculations in time, and you will hear pops, clicks, and stuttering in your audio streams. On the other hand, if the buffer size is set too high, your computer will process audio without incident, but your software will feel sluggish and unresponsive.

To find your system’s optimum buffer size setting, begin with a high setting and gradually reduce the size until you begin to hear clicks, pops, or other audible glitches in your audio. Then, raise the buffer size setting until these glitches disappear. You may need to stop playing audio any time you change this setting, and certain applications will require you to close the program before making changes, or relaunch the program before the new buffer size settings become active.

 

CPU Throttling/Power Management Utilities

Many new computer motherboards and processors have varying forms of CPU Throttling and Power Management Utilities that can have a negative effect on any audio playback and recording which will be audible as noise bursts, pops & clicks, or distortion.  Please see the following guide for more information on disabling these utilities to improve performance:

Improve Audio performance by disabling CPU Throttling & Power Mgmt Utilities (PC)


FireWire Controllers & Chipsets

M-Audio Fire Wire devices perform best on a dedicated FireWire controller with a Texas Instruments (TI) chipset.  Theses problems (pops, clicks, distortion, buzzing, etc) are often encountered when using onboard FireWire ports, including those with Texas Instruments chipsets.  You can identify your chipset in the “IEEE 1394 Bus Host Controllers” category in the Windows Device Manager (Start>Run>devmgmt.msc). Undesirable chipsets include VIA, Ricoh, and NEC.  For a more detailed explanation, please see the Why is the FireWire Chipset Important FAQ.

Unibrain firewire cards also come with a driver which you can install in place of the Windows firewire driver.  Don't install this, just install the card and allow Windows to use its firewire driver.

In Windows 7, Microsoft changed the architecture of the IEEE-1394 (Firewire) controller driver.  This new architecture does not work well with all FireWire chipsets.  If your firewire device is not being recognized or the connection to your firewire device is repeatedly being dropped, try changing to the Legacy IEEE1394 (Firewire) driver.


IRQ Conflicts

IRQ sharing can also cause these problems.  Follow these steps to check for conflicts:

  1. Go to the device manger (Start>Run>devmgmt.msc)
  2. Select Resources by Connection from the “View” menu
  3. Select Interrupt Request (IRQ) and a list will be displayed
  4. Find your “OHCI Compliant IEEE 1394 Host Controller” in the list
  5. Look for the PCI number listed before your FireWire controller

Do other devices have the same PCI number?  If a device such as the graphics/video card, Network Controller (Ethernet, modem, or wireless), or the built-in audio card have the same number, this may be the source of your problem.  With the exception of your video/graphics cards, these other devices can be disabled to eliminate the conflict.  Right-click and choose disable to disable the device.  To enable the device, right-click and select enable.  If you have installed a FireWire expansion card, shut down the computer and test the card in a different PCI or cardbus slot.  We have a separate article for more in-depth IRQ Troubleshooting.


System Optimization

Audio applications can be affected by system settings and other software and hardware drives installed on your computer. For best possible performance, it is recommended that you optimize your computer system to improve performance with audio applications.  There are a variety of other settings that can be adjusted to improve performance.  See the Optimization sections of these guides, though written for Pro Tools, the optimizations are also applicable to all other audio applications:

 

Additional Troubleshooting

Thesycon’s DPC Latency Checker is a free Windows tool that analyses the capabilities of a computer system to handle real-time data streams properly. It may help to find the cause for interruptions in real-time audio and video streams, also known as drop-outs.  As often times these drouputs are caused by other devices on the system, this tool can be helpful when troubleshooting IRQ’s.  Please visit http://www.thesycon.de/eng/latency_check.shtml for download links and more information on using this tool to check for latency spikes.


Windows XP users only; do you experience pops and clicks associated with graphics activity such as opening, closing, or minimizing windows?  Do you get a zipper noise when moving the mouse? Try lowering the Hardware Acceleration for your Video/Graphics Card and see if performance improves.  Click here for a guide to walk you through this process

 

 

Mac


Buffer Size

Buffers are used to help keep audio hardware and software running smoothly by processing audio in groups of samples rather than one sample at a time. Due to variations between computer hardware and software, it is impossible to recommend a single optimum setting for all systems.  It may be necessary to experiment with various settings until you find the best buffer size for your system.  The goal of setting a buffer size is to reduce it as much as possible without hearing any clicks, pops, or other glitches. If the buffer size is too small, the computer will not be able to make all the required audio calculations in time, and you will hear pops, clicks, and stuttering in your audio streams. On the other hand, if the buffer size is set too high, your computer will process audio without incident, but your software will feel sluggish and unresponsive.

To find your system’s optimum buffer size setting, begin with a high setting and gradually reduce the size until you begin to hear clicks, pops, or other audible glitches in your audio. Then, raise the buffer size setting until these glitches disappear. You may need to stop playing audio any time you change this setting, and certain applications will require you to relaunch the program before the new buffer size settings become active.

In OS X, this setting is adjusted from within your recording application.  This setting is generally located in the Preferences Menu in an audio configuration menu.  Please refer to your application’s user guide to find out how to change the buffer size. 


System Optimization

Audio applications can be affected by system settings and other software and hardware drives installed on your computer. For best possible performance, it is recommended that you optimize your computer system to improve performance with audio applications.  There are a variety of other settings that can be adjusted to improve performance.  See the Optimization sections of these guides, though written for Pro Tools, the optimizations are also applicable to all other audio applications:


Repair Disk Permissions

This only takes a few minutes and it is a general maintenance routine for the OS, and important to ensure the proper functioning of MIDI and audio.

  1. Open the Utilities folder located in Macintosh HD>Applications >Utilities
  2. Double click to open Disk Utility
  3. Select your Macintosh HD
  4. On the First Aid tab click Repair Disk Permissions

When the permissions repair is complete you can quit the Disk Utility.


Disable Bluetooth and Airport

Bluetooth and Airport Wireless have been known to cause problems with pops, clicks, and distortion during recording and playback.  Disable both of these from System Preferences and then test the audio quality again.  These devices can easily be activated when needed.


Operating System Updates

Is your Operating System up to date?  Since we have seen problems after using the Automatic Software Update to update the OS, we always recommend downloading and installing the “Combo Update”.  Installing the combo update is recommended as a troubleshooting step and ensures that all system files are up to date.  This combo update can be installed on top of your existing OS without having to reformat and lose any files.  For example, if you are using OS X version 10.5.5, go to http://www.apple.com/downloads and search for “10.5.5 combo update”.  Save the appropriate file for your exact OS version to your desktop.  Disconnect your M-Audio FireWire device before installing the combo update.  Once the combo update is installed repair disk permissions (see above), then uninstall and re-install the latest M-Audio driver, shut down, and then reconnect your M-Audio FireWire device.  After the system loads repair disk permissions again.