Ableton Forum

Well, after trying out a lot of different tracking-ways, i discovered that when i run midi-tracks and audiotracks simultaneously, the Live-cpu tips over after 4-8 tracks! This have to be caused by the extra info midi-tracking feeds the Live-engine - cause when i run only audio (doesn't matter if it's from ReWire or just plain instruments), i have no probs running 60-100 tracks in 24/48 on mLAN (i use mLAN anyway-anyhow - it's a nice protocol!) - And it's NOT my DAW - it's a very powerful one, btw..

Any else seeing this? This should be priority nr. ONE for the Live-team with the next upgrade (4.0.5), it's pretty frustrating having dropouts/clicks just because Live added a Midi-engine/feature that doesn't cope as it should!!

Regs,
Jo

yes i have the same problem , i get a cpu spike and the sound pops etc...i have 3 audio tracks and 2 midi..

I also noticed midi tracks seemed to eat up much more ressources than they should. Also would like to see this corrected.

Well, then this is a must for the team to solve ASAP! Last night i resampled the midi-tracks, so i got em all into audiotracks, and the cpu/Live-engine were a lot destressed; infact with this workaround, it runs nice&stable without glitches/crackles/cpu-tipping at all. But the the midi-edit's blown away, tho.. But it's a cheap workaround that works for now, i guess..

Regs,
Jo

I noticed it also... 20% more cpu adding 3 tracks.
Hmm...

It all depends on what instrument you are using...
I use a lot of reaktor, absynth, beast, impulse, eqs, camelphat and I can use up to 15 tracks with half midi and half audio...
but I tend to render the midi too... well, you might say that you loose midi editing, but you don't really. just don't use too many instruments (which in either case is hard to handle) and then use more than just ONE sound per synth. that way you can enter the BANK and PROGRAM parameters (this opened my mind on midi!!!), deactivate the synth and put it out of sight.. that way you can always edit your tracks later...
bla bla bla... I should shut my mouth!
well... beeing a little confused today...

Well, i guess that MAY help a bit, but believe me - i tried that, and i have about 40-60 vsti's to choose from, most of those you mention, and a lot of others (real good ones - Stylus RMX and so on.. only pro-plugs, almost all of them..) But it doesn't matter, the cpu (i have a 3.2 Prescott L2-1Mb & 2 UAD-1 cards - thats a lot of cpu.. + 2 gb of FAST ram AND an "active audio" disk at 10 000rpm) - but it doesn't help much! Well, it may help a tiny bit, but you can't cope with it (midi) and audio-tracks at the same time, without pops/"cpu-tipping" - if you run more than MAX a dozen mixed tracks (midi+audio) - and who can live with THAT limitation..? I've tried to turn the vsti's on&off when they don't have to run (that's a normal procedure to me..), and i have used Live since the very first release of Live 1.5 (?) and all new releases from then to now.. So i know what i'm talking about, and i've loaded sounds from sound-fonts to rex, aiff, wav and a lot of other different audio-types, but it doesn't help much - 8 tracks max, on a heavy DAW is NOT good enough from the Live-team these days - it should cope as all other hosts do, else they should get rid of the midi-feature until they got a system that WORKS!!!

But thanx for your advice!!

Regs,
Jo

myztmuzic wrote: I have a 3.2 Prescott L2-1Mb & 2 UAD-1 cards - thats a lot of cpu.. + 2 gb of FAST ram AND an "active audio" disk at 10 000rpm

wow! that's impressive. so yeah, I agree with you, you should be able to have at least 100 midi tracks and audio tracks running @ the same time.
I guess this could be a windows related problem. Or a setting problem. or a harddisk problem (try opening on the internal drive), or a vst problem (check user rights etc..), try using the internal soundcard to see if the problem persists. I had a performance drop too when it came to v4. then, hasardly, I've tried the internal soundcard and my system was a lot faster! then I've updated my soundcard drivers and ev. went fine again.

check your hardware first, then blame abletons. cause for me everything is working fine!

or switch to mac ;-)

and don't forget: you loved this program at version 3, so you don't really need the vsti ;-) but I agree, they come in very handy...

Well, i agree, the Abletons doing Pretty ok, but i'm very used to all kinds of different, heavy DAWs, as i build them at my work (heavy computer-handling-from building to tweaking the os) - and i mean heavy tweaking, like adding dwords in the reg, cutting useless backgr.processes, changing all adapter-cards latency and stuff like that..
I run mLAN, tho - working smooth&stable, flashed to mLAN2 (Presonus Firestation that WORKS - can you believe that..? ) - Well, it took me 14 days & nights with coffee as breakfast, dinner and supper.. But it was worth the effort, since it works better than ever on all progs, except Lives midi-feature.. So thats why i think this is very strange..

And like you say, warabunga, it's nice to have the vsti-feature at hand

Thanx for your response!!

Regs,
Jo