[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [sc-dev] idle scsynth CPU usage
I have a new powerbook and have the same problems. I think its a
problem with this series. I have a september build and scsynth uses 6
% cpu idle
what shall we do ?
On 08.01.2006, at 17:28, vince wrote:
i just did a fresh cvs checkout and build before. on my machine a
12" powerbook 1.33 ghz, 1.28 gb ram, using internal sound. the
scsynth using between 1.0 and 2.0% cpu, shown by the top, the
processor performance set on automatic, if i change the setting to
highest the scsynth is using about 0.5 % less cpu.
i've read you other thread about the problems with your new
powerbook. i think this problem could be related to your new
machine, and its new architecture or maybe something is broken
inside of your powerbook, a manufacturing defect? i don't hope so,
but you should consider this. i had an experience a few years ago,
after a lot kernel-panics and total freezes, i returned my new dual
g4 to apple and they changed the whole processor board after
running 48 hours hardware-test programs without finding some
broken. but then everything was running fine.
if you know any other owners of the latest powerbook. you could
test running sc on their machine.
you could connected them thru a firewire cable, boot your machine
in firewire target mode and then reboot the other machine on your
On Jan, 08 2006, at 06:29 , Joshua Parmenter wrote:
I've been noticing something strange with scsynth (this is after
all the other CPU strangeness that has been happening appears to
have worked itself out). Basically, I noticed in Activity Monitor
and top that simply starting scsynth has it running at 8% of the
CPU with nothing happening. The server window reports 0.2%. This
is on one of the 1.67 GHz PowerBooks. Either way... a recent build
on my old machine (1.5 GHz PB) shows about 1% in Activity Monitor.
I just did a fresh build... I'm wondering if anyone else sees
anything like this in a new build? And if so... is this perhaps a
recent change that has done this? Or is it my machine that is
causing the problem... which based on my experiences over the past
couple days wouldn't surprise me!
Post-Doctoral Research Associate - Center for Digital Arts and
Raitt Hall - University of Washington
Seattle, Washington 98195
sc-dev mailing list
sc-dev mailing list