Ableton lagging - Is this one core for one track issue?

[UniversalFlyer]

Hi,

I can't normally work with my Macbook pro i7 2.0ghz x 4 cores and live 9 64bit. It looks like I need more resources.

First case (quite clear):
Yesterday tested this with activity monitor and found that only 130/400% of cpu was used.
When I freezed drum rack the issue was solved.

Is this related with one core for one track limitation? Not enough one core for drum rack track?

How to resolve this issue? No ways for one midi clip and one drum rack modulation/automation?

Any suggestions how to make your project simpler and powerful?

Second case is that sometimes I reach 400% usage when use plugins from this list: razor, 2c eather reverb, many instances of izotope ozone and so on.

How much cores enough for high quality sounding? Could you tell me about your system and experience?

[Valiumdupeuple]

How much RAM do you have ?
I had similar problem with the exact same machine, and obviously I couldn't believe that it was not powerful enough.
It had 4go ram. I've added some more and now this problem is gone.
But, I mostly use Live's native devices and m4L.

[UniversalFlyer]

8G. I have splitted my drum rack into 3 tracks - much better.

But I can confirm when you use high quality plugins you can reach 400% and you just need to refuse some of stuff.

[Valiumdupeuple]

when you use high quality plugins

No offense, but take some time to master Operator, Sampler, Tension, racks... you'll might change your mind about "high quality plugins".

[UniversalFlyer]

I agree about for e.g. operator, but feel lack of effect plugins. I like to modeling sound with Trash, Ozone, Kontakt fx, some impulse reverbs.
About racks, do you mean layered sounding?

[Valiumdupeuple]

About racks, do you mean layered sounding?

Yes, layering different instruments. Or effects, or making weird crazy signal routing (tip : have a look at compressor, or gate, sidechain. Turn on the little headphone button and choose a signal source... yes, this way you can pick any signal from anywhere in your set and blend anywhere you want.),
or modulations rack...

[UniversalFlyer]

How to detect cpu usage for each track? I see in activity monitor usage ~240%, but project a bit lagging. It seems that one track wants more than one core.

[UniversalFlyer]

About racks, do you mean layered sounding?

Yes, layering different instruments. Or effects, or making weird crazy signal routing (tip : have a look at compressor, or gate, sidechain. Turn on the little headphone button and choose a signal source... yes, this way you can pick any signal from anywhere in your set and blend anywhere you want.),
or modulations rack...

Layering is important thing. I always use it. Except side chain, didn't try mentioned routings.

[Valiumdupeuple]

Generally speaking, with Live it gets problematic when you're reaching 450-500% in osx activity monitor. But it can vary a lot depending on what plugins are used. That's what I observed by doing tests,though, but I've never reached such high performances in real scenarios even on very large sessions.
You should be ok with your 8Go.
There's a lot of chances that it might be related to the 3rd party synth and FX you use, as you said. I've heard that Razor for example is supposed to be a real cpu hog even on very recent machines, and I suppose thats it's highly possible that it uses the full ressources of an entire core, because of how Live manage cpu ressources.
I guess - I don't know if you're using any but - cracked plugins might also create some problems.

Layering is important thing. I always use it. Except side chain, didn't try mentioned routings.

It's not that it's important, it's just highly convenient to be able to build an instrument with let's say, Analog for subtractive synthesis, melt with FM in Operator, with a touch of granular synthesis done by Granulator + some crazy bowish metallic sound generated by Tension... and so on dancing together. It's just a huge modular thing. If only all those instruments had more than only ADSR envelopes, Absynth would have no chance to survive.

[UniversalFlyer]

Generally speaking, with Live it gets problematic when you're reaching 450-500% in osx activity monitor. But it can vary a lot depending on what plugins are used. That's what I observed by doing tests,though, but I've never reached such high performances in real scenarios even on very large sessions.
You should be ok with your 8Go.
There's a lot of chances that it might be related to the 3rd party synth and FX you use, as you said. I've heard that Razor for example is supposed to be a real cpu hog even on very recent machines, and I suppose thats it's highly possible that it uses the full ressources of an entire core, because of how Live manage cpu ressources.
I guess - I don't know if you're using any but - cracked plugins might also create some problems.

Is there any tool to monitor cpu usage on individual track? To resolve root cause I can delete device and see what happens, but it will be better to monitor this.

It's not that it's important, it's just highly convenient to be able to build an instrument with let's say, Analog for subtractive synthesis, melt with FM in Operator, with a touch of granular synthesis done by Granulator + some crazy bowish metallic sound generated by Tension... and so on dancing together. It's just a huge modular thing. If only all those instruments had more than only ADSR envelopes, Absynth would have no chance to survive.

Thank you for the tip. I will check about this and Granulator.