One instance inside Ableton - Massive CPU

This one is a killer for me...

First proper use of Mashine for a live set - configured 7 groups for a live set. And this bad crackling started to happen.

Removed machine from the lives set and CPU went from 80% down to 9%..

Byt the way this is on a quad core desktop machine with tonnes of memory - what hope do I have when i transfer this to my laptop for live use !

Any help/tips appreciated - but right now this is unusable for me - have go to an bounce all the work I did down to audio grr

-G-

 

Some more info would help. OS? What quad core?

ew

 

Ok we figured it out...

I was loading up a single Maschine patch with all the drum patterns for a collection of songs in Ableton...

I thought I would save come CPU by having only one Maschine VST...

I had it setup so there was a different set of patterns on each Group and each group represented the drum track for a song in Ableton...

so it was a pretty large patch...

However I forgot that Ableton dedicates at most 1 CPU to each track...

So i went back and split up the single Maschine patch into a multiple patches and loaded multiple Mashine VSTs in Ableton and things are much better - I can even save some more cpu by enable/disable the unused Maschine VSTs

-G-

 

Cool... =)

If you can go with using multiple instances, that's always the best way to go with multicore systems.

ew