Strange. Isn't it.Timur wrote:Power schemes in Windows allow control over CPU steppings, seems like there is no such thing on Mac OS (beside Coolbook). <shrug>
I just switched from PC to Mac.
-M
You had coolbook set to have 8 steps and still got that low of a cpu hit (47%) ?guille wrote:I'm using Coolbook now. Before Coolbook I got 67%-78% CPU with crackles and 8 or 6 tracks using Live 6 & 7 Performance Test.
Now I get 47% CPU with 8 tracks.
This is my tested configuration:
- 800 Mhz 0.8500V
- 1200 Mhz 0.8500V
- 1400 Mhz 0.8500V
- 1600 Mhz 0.8500V
- 1800 Mhz 0.8625V
- 2000 Mhz 0.9125V
- 2200 Mhz 0.9625V
- 2400 Mhz 1.0250V
Temp limit: 75ºC
Throttling level: Medium
I would like some more clarity on this issue,,,dango wrote:ok, i am done spazzing out about Live's shite performance and am ready to give into the 3rd party coolbook. i want to keep using Live.
but does this coolbook always keep running on your computer and can this cause any damage to the computer?
I have not bought it yet, but just running the demo download, when i turn up the 'cpu load' dial to about 3 it drops the cpu strain in live down by 50% (from 60% to 30%). what is this doing exactly when i do this? is it ok for the system? answers please.
Happy New Years!
d~
Coolbook uses a kernel extension, you basically can't do any of this stuff from user space in os x. And the architecture of os x is different enough from windows (cf. mach, bsd) that it's not really possible at all to use knowledge of windows to predict how either user space or kernel space applications will behave.Timur wrote:Since I have no experience with Mac OS I can only guess. But most likely this application runs in User space at realtime priority which is worse than running in Kernel space at driver priority.
I think you're right on this. Having originally set Coolbook to my processor's maximum, I experimented with a full set of steps. High drain AU presets which ran smooth as silk when clocked to the max immediately started producing dropouts.Timur wrote:Well, I can predict as much as this: To monitor the CPU load and switch the clock several dozend times a second (aka fast enough) in software you produce CPU load yourself and most likely need to call several dozend interrupts per second as well. This will interrupt your precious DAW calculation times and thus it is a good idea to check wether Coolbook compromises your DAW's performance when running in automatic mode or if maybe it would be better to just clock the CPU to max and leave it there while you're working in your DAW.
I don't have to care, I'm just offering free hints out of my vast computer background!Besides, Mac OS X is running on a BSD Unix kernel as far as I know and the differentiation and logic between kernel and user space is not a Windows only thing.
This was my experience, which was why i was starting to think that i wasn't using CB properly,,Mammalux wrote:I think you're right on this. Having originally set Coolbook to my processor's maximum, I experimented with a full set of steps. High drain AU presets which ran smooth as silk when clocked to the max immediately started producing dropouts.Timur wrote:Well, I can predict as much as this: To monitor the CPU load and switch the clock several dozend times a second (aka fast enough) in software you produce CPU load yourself and most likely need to call several dozend interrupts per second as well. This will interrupt your precious DAW calculation times and thus it is a good idea to check wether Coolbook compromises your DAW's performance when running in automatic mode or if maybe it would be better to just clock the CPU to max and leave it there while you're working in your DAW.
I don't have to care, I'm just offering free hints out of my vast computer background!Besides, Mac OS X is running on a BSD Unix kernel as far as I know and the differentiation and logic between kernel and user space is not a Windows only thing.
When you save the coolbook settings and have the throttling on and the 'use coolbook' box checked, you don't have to re-open it, it will always work how you have it set (different settings for battery/adaptor).Homebelly wrote:I would like some more clarity on this issue,,,dango wrote:ok, i am done spazzing out about Live's shite performance and am ready to give into the 3rd party coolbook. i want to keep using Live.
but does this coolbook always keep running on your computer and can this cause any damage to the computer?
I have not bought it yet, but just running the demo download, when i turn up the 'cpu load' dial to about 3 it drops the cpu strain in live down by 50% (from 60% to 30%). what is this doing exactly when i do this? is it ok for the system? answers please.
Happy New Years!
d~
Also,,,
How exactly are you supposed to use this,,,??
I'm really not all that clear on it, I've tried all the settings in this thread, but i'm not sure i have my head around using this application at even the most basic level.
For example,,
Does it run all by it's self all of the time, or do i need to start it up then set it every time??
Should i put it into my start up folder??
Should i just run it with live??
I'm sooo confused![]()