Ableton Forum

i've just downloaded Demo of Live 6 . Installed on MacPro 2.66 . started Live and with blank Project i get 10% Cpu hit in Live CPU Meter .if i switch Multiprocessor suport CPU Meter dops to 5-6% .it looks like obvious bug.
Meter should stay on 1-2% Max with blank project.

2. MulticoreRewire Button is greyed out . what is this button for ?


Regards
B

Bakuna wrote:Meter should stay on 1-2% Max with blank project.

Erm... who said that?

1-2% That's what was Live 5 Blank project was showining .
besides , ignore above and think OF why activating Multiprocessor suport adds 5% on ?

B

Bakuna wrote:1-2% That's what was Live 5 Blank project was showining .
besides , ignore above and think OF why activating Multiprocessor suport adds 5% on ?

B

I'd guess it's down to a different way in which the CPU time must be measured for dual core. The meter in Live is far from accurate any way, don't loose sleep over it.

Funkstar De Luxe wrote:

Bakuna wrote:Meter should stay on 1-2% Max with blank project.

Erm... who said that?

my P4 2.6 is staying on 2% while recording an audio track, so 2% in an empty set sitting idle sounds perfectly reasonable!

Funkstar De Luxe wrote:

Bakuna wrote:1-2% That's what was Live 5 Blank project was showining .
besides , ignore above and think OF why activating Multiprocessor suport adds 5% on ?

B

I'd guess it's down to a different way in which the CPU time must be measured for dual core. The meter in Live is far from accurate any way, don't loose sleep over it.

5% for MacPro is not a big deal but it looks odd .if it needs to be fixed it will be.

Regards B

Bakuna wrote:i've just downloaded Demo of Live 6 . Installed on MacPro 2.66 . started Live and with blank Project i get 10% Cpu hit in Live CPU Meter .if i switch Multiprocessor suport CPU Meter dops to 5-6% .it looks like obvious bug.
Meter should stay on 1-2% Max with blank project.

2. MulticoreRewire Button is greyed out . what is this button for ?


Regards
B

What latency are you running your audio mLan audio interface at ?

Increase the latency slightly (e.g. 512 samples at 44.1kHz) to see any difference reflected ?

Bakuna wrote:i've just downloaded Demo of Live 6 . Installed on MacPro 2.66 . started Live and with blank Project i get 10% Cpu hit in Live CPU Meter .if i switch Multiprocessor suport CPU Meter dops to 5-6% .it looks like obvious bug.
Meter should stay on 1-2% Max with blank project.

2. MulticoreRewire Button is greyed out . what is this button for ?


Regards
B

What latency are you running your audio mLan audio interface at?

Increase the latency slightly (e.g. 512 samples at 44.1kHz) to see any difference reflected?

I assume you have the latest mLAN tools installed also ...?

I have latest MLan UB Tools installed. i run it at 96khz .latency hmm i dont remember after trying few different settings i guess i settled with 125 .
my point is not to find a workaround . i'm compareing Live 5 to Live 6 . with exactly same settings and hardware Live 5 was showing 1-2% with blank project Live 6 is on10% .big difference . it looks like a clear bug to me .

Regards
B

before you start declaring bug's galore, i'd suggest you read the live 6 beta forum which has many a thread discussing the multi-core support issue. from what i have read it would only kick in when multiple plugins are used, so doubt it will make any difference on a blank set... but i presume its far more complicated than that.

also mac osx 4.8 has just been released, which i believe also has some tweaks to optimise multi-core threading.

+ the MulticoreRewire Button is to enable multi-core when using rewire!

I have noticed the same behaviour in live 6 regarding the initial cpu usage, which is higher with 2, then with 1 processor. However, when using more and more resources, the cpu doesn't quite speed up as rapid as befor, so u can get much more effects/tracks going. So, don't worry about performance, you'll get the power when you need it in my experience.

Nixon wrote:I have noticed the same behaviour in live 6 regarding the initial cpu usage, which is higher with 2, then with 1 processor. However, when using more and more resources, the cpu doesn't quite speed up as rapid as befor, so u can get much more effects/tracks going. So, don't worry about performance, you'll get the power when you need it in my experience.

may be so . it would be good to know Ableton's comment on this thread ?


B

hi bakuna

i cant confirm that.
with a blank project i get 0% usage in CPU Meter on mac pro.
and it makes no difference if i turn on/off multiprocessor support.
maybe a Mlan driver problem only.
have you also tried with build in audio interface ?

regards,
tomac

tomac wrote:hi bakuna

i cant confirm that.
with a blank project i get 0% usage in CPU Meter on mac pro.
and it makes no difference if i turn on/off multiprocessor support.
maybe a Mlan driver problem only.
have you also tried with build in audio interface ?

regards,
tomac

thats quite a revelation . i will try internal sound card tonight see if it makes

B

Nixon wrote:I have noticed the same behaviour in live 6 regarding the initial cpu usage, which is higher with 2, then with 1 processor. However, when using more and more resources, the cpu doesn't quite speed up as rapid as befor, so u can get much more effects/tracks going. So, don't worry about performance, you'll get the power when you need it in my experience.

hi Tomac ,

thx for your suggestion . higher cpu hit with Multicore suport switched on isn't MLAN's fault .i tried internal MacPro sound card . exactly same behaviour but what Nicson and Justin suggested in earlier replies turned out to be true .Multicore supports shows its effect when you use big number of effects , reverbs etc,. i say this after testing driving Cubese 4 which arrived today . with Cubase' 30 new VST Instruments each instruments having own Cubase reverb opened MacPro's cpu monitor was still on14% , Cubase' performance meter with MultiCore suport on -26% ,when switched off 34% .pretty impresive.(if you use that number of reverbs you have to have audio buffer on 326 in cubase though .its crazy amount of reverbs to have opened in one progect but it was for test drive reason to see how much MacPro can take., answer is awful lot .screaming fast machines they are) i still have to test Live's behaviour with similliar scenario . you will hear from me tomorrow with results

regards
B