Freezing tracks and CPU usage

[Chad P]

Macbook 2Ghz Intel, 2GB RAM
Live 7.0.15
NI Pro-53
Fabfilter One

Never had problems with CPU usage before, but my latest track is cutting out. The Fabfilter synth is new, so I'm guessing it's the cause. I've frozen every track but the drums and CPU usage is still at 55 - 80% without even playing anything. I've also played around with the buffer size, but it still cuts out during more complicated passages. Short of buying a new computer which I plan on doing within the next year is there anything else I can do? I thought freezing the tracks should drastically cut down on CPU usage?


Thanks,
Chad P

[NPC]

hi, i'm also into this low-cpu trip (read my specs below..).i would say the pro53 is one of the lowest cpu-hungry vst so i guess it is not the problem..i was wondering have you tried opening a new live set and putting in just the fabfilter plug?because you should see right away if it generates spikes & stuff..for example if i put a predator in a blank live set my poor ibook starts jumping (with no notes playing) between 45-80% of cpu. if this is the case, i suggest to change vst:) still, if this is the case freezing wont help as the problem is not that the instrument is playing but just that it is turned on..maybe you can freeze-copy clips-paste on an audio track-delete the freezed midi track but obviously you will lose the ability to play the vst...

[Chad P]

Great idea, thanks for the tip. I just tried opening a new set and ran 3 tracks with the Fabfilter synth. Usage stayed at 3%... any other ideas?

[NPC]

..and the drums, where are they coming from?since you didn't quote them in the specs i guess you're using drum racks..and there are a lot of premade racks that are quite cpu-intensive & very spiky (ie they clikc & pop) so maybe that is the problem..anyway i would recommend trying to rebuild the set as it is, step-by-step, so it will be easier to isolate the problem..i always do this way when i experience strange stuff like this.