Does anybody know the reason?
...and other thing... i like the concept of drum rack but it's not possible to make sends for individual tracks!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I don't understand it!!
Can I ask....does the unregistered version of Coolbook measure the change in clock speed as you put load on the processor? I have tested it with the Live Performance test and the clock speed stays at 800mhz. on my MBP 2.4sparklepuff wrote:Yup, Coolbook dropped the CPU usage in Live down to 56% for me. That's a 13% improvement. I'm sure I could tweak more to get better performance, I just installed it.
I am curious what it would do for your already low 56%, Tarekith. Maybe even knock it down to the low 40's, perhaps?
open the chain editor, click on the R in the down left corner, put your send effects here, click on the S to adjust the send levels for each drumpad, voilaguanche wrote: ...and other thing... i like the concept of drum rack but it's not possible to make sends for individual tracks!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I don't understand it!!
Ok!!!! merci man!! I'm gonna try.m:o wrote:open the chain editor, click on the R in the down left corner, put your send effects here, click on the S to adjust the send levels for each drumpad, voilaguanche wrote: ...and other thing... i like the concept of drum rack but it's not possible to make sends for individual tracks!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I don't understand it!!
Doesn't that just mean that Coolbook throttles the CPU to its maximum setting, and you're seeing better percentages because of thatpribeh_tom wrote:I just installed it (and applied default settings with a "high throttle") on my Macbook Pro and I scored 49% instead of 67-9. That's a 20% difference
Which it is. Because Ableton stutters at pretty low cpu quite often (lke 65%), it is totally worth it to get that extra throttling from the processor. The computer doesn't think it needs to be at full speed when live is around 60-70%, but at the same time that's really Live's maximum useable percentage, unfortunately. So you end up maxing out live before the computer even decides to go to full speed. I personally think it stinks both on the part of apple for it's crappy speed-steeping implementation, and ableton for either it's poor stability at moderate cpu use or improper cpu reporting or something.Nokatus wrote:Doesn't that just mean that Coolbook throttles the CPU to its maximum setting, and you're seeing better percentages because of thatpribeh_tom wrote:I just installed it (and applied default settings with a "high throttle") on my Macbook Pro and I scored 49% instead of 67-9. That's a 20% difference?
In other words, it seemingly makes the score dramatically better, as a load of 67% isn't necessarily high enough for the CPU to throttle to a higher speed according to the default settings. However, if you were to hit a higher load, the speedup would occur eventually in any case.
"Prematurely" throttling to a higher setting allows you to measure the potential of the system, as far as the load percentage goes, but it doesn't actually conjure 20% more performance out of the system. There is an actual benefit only if the default throttling is "lazy" enough to induce dropouts before speeding up.
It should show you which speeds its jumping around from. In my case it shows that it jumps from 2171 to 2338. Buy it though, and try it out. It's only ten bucks. You can't go wrong. And test it then.Mammalux wrote:Can I ask....does the unregistered version of Coolbook measure the change in clock speed as you put load on the processor? I have tested it with the Live Performance test and the clock speed stays at 800mhz. on my MBP 2.4
Again (no offense), but I really don't care enough to try it.sparklepuff wrote:I am curious what it would do for your already low 56%, Tarekith. Maybe even knock it down to the low 40's, perhaps?
By definitition, i'd say definitely yes. Certainly setting my PC laptop to 'always on' produces more heat when runinng ableton. I recommend the Zalman NC1000 cooler - miles quiter than your laptop fans on full tilt. That way you get all the power without the racket.Tarekith wrote:Again (no offense), but I really don't care enough to try it.sparklepuff wrote:I am curious what it would do for your already low 56%, Tarekith. Maybe even knock it down to the low 40's, perhaps?If I can get 56% running a project that uses way more plug ins than I'll ever use in real life, why mess with it? That's still way more than enough juice for me finish a song, so it's just not something I want to even mess with.
One question though, wouldn't doing this kind of work cause the fans to kick on more frequenctly? I'd imagine using more CPU power requires more mains power, which means more heat, no?
With my Mbox 2, I too, got 68% cpu usage on my Macbook Pro. After reading the posts in this thread, I did the test with my Ultralite and wuddya know... 55%. Amazing.R.J.Dubya wrote:Wow, that's really good to know. A 15% drop because of a firewire interface? I'll have to check this with my firepod. So just having your outputs set to use your saffire brought on the improved cpu useage? I wonder how USB2 interfaces fare...garyboozy wrote:ok after my higher than expected cpu hit with the same mac as tarekith, i've updated to leopard. tried the test again with the built-in audio and got the same hit of 67%, which is what i had with tiger using both built-in and using the saffire LE. was a bit gutted. so, plugged in the saffire and i now get 54% cpu! seems like leopard has been seriously tweaked for firewire audio use. very nice!