About the iTunes EQ, that is really funny. I just profiled PD while
running the example patch, and you're right (see example 1 below).
Using "Instruments" showed similar results, + a _lot_ of time spent
microsleeping.
Do you find that the CPU load scales well in large patches,
disregarding the 10% overhead?
--Example 1--: # Report 0 - Session 2 - Time Profile of pd.mshark - Time Profile of pd SharkProfileViewer # Generated from the visible portion of the outline view
long) (com.apple.driver.DspFuncLib)
unsigned long) (com.apple.driver.DspFuncLib)
long) (com.apple.driver.DspFuncLib)
(com.apple.driver.DspFuncLib)
(com.apple.driver.DspFuncLib)
On Feb 4, 2008, at 12:56 PM, chris clepper wrote:
On Feb 4, 2008 11:16 AM, bsoisoi bsoisoi@mac.com wrote: I've attached an example patch "sample-test-01.pd" and it's dependencies. On my dual core 2.4ghz Macbook Pro (4gb ram, 10.5.1, pd extended 40.3-2007-12-07), I hit 21-27% cpu load
On the Macbook 'Pro' 1.83 I have here the CPU time is never above
10% and all of that time is spent in the driver - I bet you didn't
know the Apple drivers always apply the iTunes graphic EQ effect to
the output did you?Your problem might be simply having the latest Macbook with its
unbelievably shitty drivers. The Apple written drivers have gotten
really bad lately - try to stick with ATI GPUs just to avoid Apple's
in house Nvidia drivers for example. The wireless drops connections
with perfect reception and the audio sucks a lot of CPU pointlessly.Maybe use Bootcamp for Pd?