<br><br><div class="gmail_quote">On Tue, Feb 28, 2012 at 7:12 PM, Rich E <span dir="ltr"><<a href="mailto:reakinator@gmail.com">reakinator@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><div><br></div><div>Anywho, the latest nightly build is still running at around 17% cpu for me before ever opening a patch. It's just enough to make my fans hum. :)</div>
<div><br></div><div>I've attached a process sample from Activity Monitor, hope it helps track it down.</div><div><br></div></blockquote><div><br></div><div>An interesting question. On my MacBook with OSX 10.5 Pd is sometimes running as much as 27% in 'idle' state. When Pd is started, dsp if off but the adc/dac are not. Only after turning dsp on, and off again, the adc/dac are off.</div>
<div><br></div><div>As you're on OSX, you can use the magnificent performance profiler Shark.app to get a better view of CPU load of functions. Most CPU time for adc/dac is consumed by DspFuncLib, AppleHDA and mach_kernel. Apparently, the system does a lot of processing on the audio stream without us asking for it. There's denoise, equalizer and fft functions amongst others. I don't think Pd can influence these routines, except by not using the adc/dac. </div>
<div><br></div><div>CPU load for adc/dac depends on hardware. Using an external audio interface reduces the load.</div><div><br></div><div><br></div><div>Katja</div></div>