<br><br><div class="gmail_quote">On Tue, Feb 28, 2012 at 9:06 PM, Jamie Bullock <span dir="ltr"><<a href="mailto:jamie@postlude.co.uk">jamie@postlude.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div class="h5"><br>
</div></div>Yup, I think this is related to the Portaudio driver. I reported it here:<br>
<br>
<a href="http://sourceforge.net/tracker/?func=detail&aid=3100679&group_id=55736&atid=478070" target="_blank">http://sourceforge.net/tracker/?func=detail&aid=3100679&group_id=55736&atid=478070</a><br>
<br>
I don't think it's Portaudio itself that's at fault, but rather the way it interfaces with Pd.<br><br></blockquote><div><br></div><div>DspFuncLib is in:</div><div><br></div><div> /System/Library/Extensions/AppleHDA.kext/Content/Plugins/DspFuncLib.kext/Contents/MacOS. </div>
<div><br></div><div><span class="Apple-style-span">If you run command nm on the lib, you'll see a plethora of dsp functions like MultiBandCompressor, NoiseCanceller, Loudness, Softclip, Limiter and whatnot. Functions in this lib are called when the internal soundcard is used. When using an external soundcard with Pd, </span>DspFuncLib<span class="Apple-style-span"> is not called and that makes the big difference in CPU load.</span></div>
<div><br></div><div>AppleHDA and mach_kernel are Apple libs as well and together with DspFuncLib they are responsible for the crazy CPU load in the 'idle-but-dsp-on' case. </div><div><br></div><div>PortAudio functions are apparently statically built into Pd and they consume very little CPU time.</div>
<div><br></div><div><br></div><div>Katja</div><div><br></div></div>