PDA

View Full Version : Elastic Audio - Crackling, Popping, and Distortion


lclebsch
10-07-2009, 04:13 PM
I have recently migrated my PT8 from Windows to Mac, and I"m loving it. I got a MacBook Pro with 4GB RAM and I'm writing files to a Seagate 400GB FireWire drive.

I have a whole bunch of vocals that I need to get aligned using elastic audio, but every time I try I'm getting really bad distortion and/or crackling and popping. Does anybody know what could be the cause of this?

I'm wondering if it has something to do with the drive...maybe it doesn't have the TI chip or something....Has anyone had these types of problems before?

lclebsch
10-07-2009, 04:13 PM
I should have mentioned that I am running SL, and I have installed the pre-release.

zodo
10-08-2009, 11:57 AM
Do you have "Ignore Errors" turned on in your playback engine setup dialog? If that's the case, you may be overloading your cpu with the session and it's not throwing any errors.

tamtamstudio
10-10-2009, 10:25 AM
me too, sounds terrible in monophonic and varispeed mode.
polyphonic and rhythmic and x-form seems doesn't affected.

raulbarroso2
10-10-2009, 04:53 PM
I had the same problem trying to use elastic audio monophonic mode. if anyone knows how to solve this problem, please let me know too. Thanks a lot!!!

lclebsch
10-17-2009, 06:46 AM
I bought a firewire drive...a WD My Book Terrabyte Fire Wire drive. Switching from the USB to the Fire Wire drive seemed to eliminate most of my EA problems.

It still seems like i get more artifacts than when I was in XP. I'm wondering if maybe one SL incompatibility issue is in how effective elastic audio is.

Don't get me wrong, I'm manipulating like 10 tracks of vocals (rythmically, not melodically) a TON, and have been able to acheive everything I want. It's just taking a lot more time than usual...

Hope this helps...

weparecords
12-08-2009, 08:56 AM
Same exact problem here as well. I'm going to save a session on the computer with Snow Leopard and open it on my 10.5 Leopard system to see if the problem is saved onto the file or it is just an elastic playback issue.

Using xform does not produce this same static.