Ableton Forum

Can it really be so? After years of using my M-Audio USB Duo for
recording vocals into live, in version 6 [which I just upgraded to],
while trying to play back only a few tracks with a few FX, it throws my CPU into the 70's and turns it all into glitchy mish-mash.

When I disable the DUO and go with the "Built-In" for In's and Out's it
all plays fine...

I made sure my driver was updated for the Duo. It seems very disordered
in its behavior too. I had a reference tone going at one point when I was
doing the tutorial lesson for "setting up I/O" and at first I had a clean tone
but then it got all glitched out and I couldn't get it back to sounding normal
no matter what I tried. Even when I am not playing anything, I get more CPU
then I used to and even some crackles here and there and some really abrasive
electronic glitch sounds.

Granted I need a better laptop and prolly a better soundcard but this setup has
worked with previous versions of Live. Any thoughts?

THANK YOU in advance for any info...

This is so painful.

I'm spending 4 times as long as I used to when writing a song. I am continually
freezing tracks and then allowing myself to record. Even with tons of tracks
frozen the CPU is in the 70s and beyond and I'm getting intermittent crackles.
What a destroyer of my creative flow this is...

Is there some logical reason why this version of Live uses more CPU power than
the previous versions?

Isomer wrote:This is so painful.

I'm spending 4 times as long as I used to when writing a song. I am continually
freezing tracks and then allowing myself to record. Even with tons of tracks
frozen the CPU is in the 70s and beyond and I'm getting intermittent crackles.
What a destroyer of my creative flow this is...

Is there some logical reason why this version of Live uses more CPU power than
the previous versions?

Have you tryed to set the buffer size?Set it more than 512ms and see if it works for you.Or try to delete the driver from you audio card and install it again.

Tried setting the buffer size but it doesn't seem to help in the long run.

If by "setting it to more than 512m ms" you mean to set it to more than 512 samples,
thereby altering the input/output latency (ms), that DOES help but then it renders me
incapable of recording in sync because the latency is way out of wack. Even when
I slam the buffer suze into the Thousands and max it out, things seem to play
OK but my CPU still is hovering in the 50s or more!

This is why I think there is a deeper problem here. I will delete the driver and install
it again. Thanks for your thoughts...