When my arrange view looks like this...

Tarekith · Post by **Tarekith** » Fri Dec 15, 2006 2:25 am

Live starts to act really, really sluggish. What is it about having so many clips that makes Live bog down? This is an average drum section for me too, I haven't even added any instruments yet....

Tone Deft · Post by **Tone Deft** » Fri Dec 15, 2006 2:38 am

shared video RAM? isn't there a screen update rate in the preferences?

Tarekith · Post by **Tarekith** » Fri Dec 15, 2006 2:46 am

Brand new Mac Book Pro, 2.16 c2d, 1GB RAM.

I mean, it's much faster than my last laptop, but still.

longjohns · Post by **longjohns** » Fri Dec 15, 2006 3:27 am

I'd be really interested to know how that same set performs with all the tracks folded up. I have always suspected too much effort going into the waveform rendering. You know how they seem to shimmer or shudder during playback?

Tarekith · Post by **Tarekith** » Fri Dec 15, 2006 3:43 am

That's a good idea. I tried it just now, and unfortunately, no difference.

jamester · Post by **jamester** » Fri Dec 15, 2006 5:16 am

Looks like you've only got about ten tracks going there. Holy Crap, that's not good!

In Sonar I often work on tunes with 30+ tracks, and it never gets sluggish. I know this problem is nothing new for Live, but if Live is trying to establish itself in the "real daw" arena (and it is), then this absolutely needs to be fixed.

b0unce · Post by **b0unce** » Fri Dec 15, 2006 5:24 am

I bet it has something to do with vectors.

longjohns · Post by **longjohns** » Fri Dec 15, 2006 5:30 am

Or ball bearings.

It's all ball bearings these days.

mechcon · Post by **mechcon** » Fri Dec 15, 2006 5:41 am

make sure that the notebook's energy setting is set to maximum when on charger.

that can't be right, as my powerbook in that view runs fine.

got the latest build of 10.4?

Anubis · Post by **Anubis** » Fri Dec 15, 2006 5:56 am

jamester wrote:In Sonar I often work on tunes with 30+ tracks, and it never gets sluggish. I know this problem is nothing new for Live, but if Live is trying to establish itself in the "real daw" arena (and it is), then this absolutely needs to be fixed.

I've got the opposite situation. Live runs lean and mean on my notebook yet Sonar runs finnicky by comparison. I've concluded that Sonar doesn't play well with the asio drivers. Thank Michael for Asio4All!

jamester · Post by **jamester** » Fri Dec 15, 2006 6:38 am

Anubis - That's odd, I use ASIO as I get lower latency than with WDM. I have yet to do anything substantial in Live yet beyond a few tracks, so I've not experienced any of the dreaded sluggishness myself.

Oh, and if you like Sonar you should check out REAPER:

http://reaper.fm/download.php

Sonar's days are numbered for me...

rbmonosylabik · Post by **rbmonosylabik** » Fri Dec 15, 2006 6:45 am

processor stepping maybe?

disk access speed?

Johnisfaster · Post by **Johnisfaster** » Fri Dec 15, 2006 6:47 am

sorry I can't tell if those are midi tracks or audio tracks but I would suggest consolidating some of those as I've always suspect live doesn't like alot of little slices running around in arrange view. consolidate a whole track and then chop out the long silent parts seems to me like it runs smoother but I haven't tested enough to be able to promise it'll work for you.

also if you have any audio tracks in there you could try loading them into ram mode.

b0unce · Post by **b0unce** » Fri Dec 15, 2006 6:52 am

its got something to do with live's audio engine, which is designed for live performance and uses 'vectors' to deal with its audio.... its a shame the arrangement view uses the same engine, because the audio vectors get priority and the visual feedback lags like a bitch....

maybe they should change the engine somehow for arrangment, and assume the user isnt performing live so its easier to edit loads of tracks.

conjecture ?

Machinesworking · Post by **Machinesworking** » Fri Dec 15, 2006 6:53 am

With the BD and Snare you have many tiny cut up clips. live stops addressing the hard drive every time the clip ends, then jumps into action when the next one starts, it's possible it's hard drive related. try rendering those two tracks as one big audio file, and see if that helps.