Random audio pops.. CoreAudio?

Question

Level 1

1 points

Random audio pops.. CoreAudio?

After reading through dozens of threads with similar audio issues, none quite fit my particular case nor did any of the suggestions solve it. I've been struggling with this for months now..

I have an early 2011 Macbook Pro with OS X 10.7.4, and Echo AudioFire 4 as the interface. The problem is that any input signal from the audio interface is contaminated with little random pops, not loud but definitely noticeable. I know that the audio interface is not the issue because it has a "direct monitoring" function, where the input is directly put through to the output, and the signal there is clean, no pops.

I've checked/replaced the mic as well as the mic and firewire cables. I've tried bigger audio buffer settings (up to unacceptable 50ms) and no change, still pops. I've calibrated the "driver error compensation", which was 0ms.

It happens with several software, e.g., Ableton Live and MainStage independently, so I believe the cause of the problem must be between the software and the audio interface: either the laptop itself, or the CoreAudio driver. I've tried removing the coreaudio plist, but no difference.

If anyone has a suggestion, I'd really appreciate it.

I suppose I can try using the laptop's own microphone to bypass the audio interface and narrow down the exact cause.

MacBook Pro, Mac OS X (10.7.4)

Posted on Jun 1, 2012 4:27 PM

Reply

Answer 1

Lio Eters Author

Level 1

1 points

Jun 1, 2012 4:57 PM in response to Lio Eters

Interesting -- when using the built-in microphone, there are no pops. So, it's not Coreaudio.

That leaves: the firewire socket on the laptop; the firewire cable; and possibly the daisy-chained HDD. Currently I have the laptop, audio interface, then the HDD, which seems to be the logical order.

Reply

Answer 2

Lio Eters Author

Level 1

1 points

Jun 3, 2012 4:01 AM in response to Lio Eters

I reinstalled OS X through Lion recovery (Option+R at startup) -- which for some reason put me back to 10.7.3 -- so I updated to 10.7.4.

The first try on audio input is without pops. So far, so good. I'm crossing my fingers that this solved the issue.

Reply

Answer 3

Lio Eters Author

Level 1

1 points

Jun 3, 2012 4:19 AM in response to Lio Eters

Nope, still there. Hmm..

Reply

Answer 4

bigb6611

Level 1

0 points

Nov 20, 2012 9:32 AM in response to Lio Eters

Lio, were you able to resolve this issue? I am in the same situation : late 2011 macbook pro, audiofire 4, random pops and clicks occurring, in a non constant fashion.

In my DAW (Reaper), any samples buffer setting below 512 will cause the pops. I'll even get the pops at 512, and even sometimes at 1024!!!

Regards

Reply

Answer 5

Lio Eters Author

Level 1

1 points

Nov 20, 2012 10:45 AM in response to bigb6611

Hello, bigb6611. Ah, this problem frustrated me for months! I've got it solved now but I tried so many things, I don't remember exactly what fixed it. Here are some things I've looked at.

In the Echo Firewire Console settings, update the console (via About button) if you haven't already. Set clock source to internal, and the sample rate should be the same as the DAW's. I also noticed that on the out channel (1-2, 3-4) settings, if the master volumes on the right are set to maximum (0dB), it can cause clipping, a dirty distortion when the signal hits max. So I always keep them a little under.

Another thing I can think of is to make sure "trim" knobs on the input channels of the AudioFire are not set to max.

Also, on the Mac OS, under System Preferences -> Sound settings, I switched both Output and Input to something other than AudioFire. I seem to recall that this might have been what fixed the problem finally. I don't know if it's CoreAudio or the AudioFire, but I find that the handling of several applications using the same interface can get awkward.

I hope that helps!

Reply

Answer 6

bigb6611

Level 1

0 points

Nov 21, 2012 4:27 AM in response to Lio Eters

Lio, thanks for your reply.

So all these steps did solve it for you? That's great news! :-)

I have already tried pretty much all of these, but with no success... still getting the pops and clicks. 😢

I tried an entry level M-Audio interface (Fast Track USB), which also uses CoreAudio: glitch free at buffer settings as low as 96 samples, with a bunch of plugins processings in the background. So to me, CoreAudio is not guilty here. All eyes point to the Audiofire 4.

Thanks again for you input

Reply

Answer 7

Lio Eters Author

Level 1

1 points

Nov 21, 2012 4:38 AM in response to bigb6611

Yes, to be honest, after I struggled with the Audiofire 4 for months, I couldn't trust it for a reliable recording. I gave up and bought an Apogee One. That totally solved my problem! 😀

Reply

Answer 8

bigb6611

Level 1

0 points

Nov 21, 2012 4:43 AM in response to Lio Eters

Haha! I must say I'm almost there too! Just trying to figure out what would be my best option! 😉

Reply