Ableton Forum

8.1.3 = NO CPU Overload solution. This is a very annoying issue, because I can't even make a set with this thingy. Loved version 7 where everything was going smoothly... During production process, Live 8 uses 60% of CPU to process two VST tracks with Massive and one VST Sylenth1. Something is wrong "Abes", and at least you could tell us is that there is something wrong and that you are, or not, efforting to solve it.

Anyway, if you have any problems regarding this issue, with any version of Live 8, put them here so Ableton can understand what's going and solve this ASAP.

Please leave your hardware specs (including controllers),

Diogo

P.S.: EVEN IF YOU DON'T HAVE THIS SORT OF PROBLEMS, VOTE ANYWAY!

Hi diogo_semedo,

Achieving 60% of CPU load with 2 tracks of Massive + one track of Sylenths1 is of course possible, depending on your settings and the presets in use. Please contact [email protected] with your full system specs and the mentioned Liveset. Additionally, please also include a screenshot of your preferences/audio in Live.

Best,
Jörg

I was just creating some smokes. In Live 7 with similar presets this would not happen.

Diogo

stop blowing smoke and send the damn logs in.

why you gotta bring up old shit?

H20nly wrote:stop blowing smoke and send the damn logs in.

why you gotta bring up old shit?

I believe you didn't understand what I said. I was creating swoshes (you know those things that raise energy on a track??) on a track of mine, not trying to create any conflicts in here.

And for you, THIS IS NOT OLD SHIT, I SPENT 400 EURO ON A SOFTWARE THAT DOESN'T WORK, NEITHER FOR ME OR OTHER PEOPLE WITH THE SAME PROBLEM. If you don't have this problem, thanks for reading and go troll somewhere else.

jok wrote:Achieving 60% of CPU load with 2 tracks of Massive + one track of Sylenths1 is of course possible, depending on your settings and the presets in use.

It could definitely be possible, depending on your system and the polyphony/quality chosen in Massive.

@ Jorg- is Live only reporting the most active core on the CPU meter? What I've seen in my old version (6.0.11) and the reports I've seen over at the NI forums would suggest this is the case...

ew

"it works on fine on Live 7" - old shit.



"Calling all forum members"


I have issues with Live 8. I don't talk about Live 7.

You don't rub a dog's nose in a shit he took 2 years ago.

Hi Ewistrand,

@ Jorg- is Live only reporting the most active core on the CPU meter? What I've seen in my old version (6.0.11) and the reports I've seen over at the NI forums would suggest this is the case...

yes, spot on.

Best,
Jörg

jok wrote:Hi Ewistrand,

@ Jorg- is Live only reporting the most active core on the CPU meter? What I've seen in my old version (6.0.11) and the reports I've seen over at the NI forums would suggest this is the case...

yes, spot on.

Best,
Jörg

But in other conversations about the CPU meter, we were told the CPU meter is an indicator of how much Audio processing power is left. And that it explained why most people can't get past 80% because that other 20% included non audio processes like graphical processing.

If I got that correct, then how do we know the available power of the least active core?
If Live uses multiple cores, wouldn't it also be able to display multiple meters?
1 core = 1 meter
4 cores = 4 meters

And while on the topic, if the empty space in a CPU meter does include other processes beside audio. Wouldn't it be helpful to see something like: Audio 60% GUI 17% RAM 88%

Hey diogo_semedo, I had a look at your system specs, a 2.4Ghz macbookpro, and what you are using - Massive and Sylenth.

I have to tell ya that Massive is a CPU hog - and Sylenth only a little better.

I have a 1.83Ghz macbookpro running Logic, and one note from Massive will overload the CPU.
I can run many instances of other plug-ins, but one note from Massive kills everything.

Now, I'm not in any way trying to say that Ableton does not have problems.
But Massive is a bad example to be using on a 2.4G machine - which will have problems in Logic or any other DAW you put on that macbookpro.

If I started running Logic with any sample rate higher than 44.1 - Sylenth would crash that party.
I'm just trying to put some perspective on this.

A better test of Ableton issues would be to use only Ableton plug-ins and see what used to run smoothly in Live 7 that clearly does not run smoothly in Live 8.

S.

Scott Righteous wrote:
I have to tell ya that Massive is a CPU hog - and Sylenth only a little better.

In Massive's case, you have to remember that voices are computed in groups of four; parallel processing like that actually decreases the CPU load with higher voice counts. However, with single voices, you're going to see close to the load that you would with four; it's within 3-4%.

I'm not sure whether or not Lennard uses the SSE/Altivec parallel processing routine or not; I'm guessing he does.

I have a 1.83Ghz macbookpro running Logic, and one note from Massive will overload the CPU.
I can run many instances of other plug-ins, but one note from Massive kills everything.

What variant OSX? What's your quality setting in Massive? Unison voices?
If you're using 10.5.x or below, you might want to look into using coolbook/QuietMBP or some other kernel extension to shut off speedstepping; IntelMacs with 10.5.x and below have aggressive speedstepping as defaults.

Now, I'm not in any way trying to say that Ableton does not have problems.
But Massive is a bad example to be using on a 2.4G machine - which will have problems in Logic or any other DAW you put on that macbookpro.

Definitely not true if you tame the speedstepping in OSX, or, if that doesn't do it, turn down the quality in Massive. On my old 4600x2 Windows box (actually 2.4 GHz), 16 voices of Massive in ultra quality mode would average around 55-60% of one core; using four voices (a note and threee unisons) would run around 15%. Turn the quality down to high, and I'd see maybe a third less.

Your Massive forum moderator,
ew

Scott Righteous wrote:Hey diogo_semedo, I had a look at your system specs, a 2.4Ghz macbookpro, and what you are using - Massive and Sylenth.

I have to tell ya that Massive is a CPU hog - and Sylenth only a little better.

I have a 1.83Ghz macbookpro running Logic, and one note from Massive will overload the CPU.
I can run many instances of other plug-ins, but one note from Massive kills everything.

Now, I'm not in any way trying to say that Ableton does not have problems.
But Massive is a bad example to be using on a 2.4G machine - which will have problems in Logic or any other DAW you put on that macbookpro.

If I started running Logic with any sample rate higher than 44.1 - Sylenth would crash that party.
I'm just trying to put some perspective on this.

A better test of Ableton issues would be to use only Ableton plug-ins and see what used to run smoothly in Live 7 that clearly does not run smoothly in Live 8.

S.

That's what I've been doing for some time and Massive, several instances, worked pretty well on 7 and even in Logic in the same machine

Gotta say I had cpu overload problems playing around with the software and figured out how to avoid them, so I don't have them any more and only running dual core. but it seems Macintosh is definitely having problems. also I haven't gotten to using the rewire with other programs yet.

predict a lot of these issues are hardware related, especially in notebook users

8.1.3 has solved all my issues. I've run it for the last few days and no nastiness of any kind.

I haven't had any CPU issues even with 8.1.1 running on a dual-core ASUS lappy with XP SP3.

Friends of mine running Vista are still having some probs, not sure about Win7, but my experience seems to suggest avoid Vista at all costs (we know it's shit anyway, but just to state the obvious).

I think I'll be staying on XP for my production machine for a while.

SAME HERE .MASSIVE CPU OVERLOAD. NOT HAPPENED ON 8.1.1