<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1276" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2><!--StartFragment --><FONT face="Times New Roman"
size=3><FONT face=Arial size=2>Bradon,</FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial size=2>I've found that a lot of pd performance
problems come from the GUI. While running your patch, open up the Windows
Task Manager and keep an eye on the "pd.exe" and "wish83.exe" processes.
I've found that the "wish83.exe" process corresponds to the GUI and the "pd.exe"
process corresponds to the actual audio/midi/control processing. Keep
an eye on the CPU% usage for these processes while using your patch and you
should be able to see what the bottleneck is. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2>I've found that changing states (e.g. via pool or
state) will cause a big spike in the GUI process because many
numberboxes/sliders/etc are being updated at once. Also, I've found that
GOPs use up more GUI power.</FONT></DIV></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>If the GUI is the problem, try putting as much of
the patch as possible in a sub-patch and keep that sub-patch window closed... so
you only have a minimal amount of GUI elements on the screen. This is
where an external MIDI controller of some sort comes in handy, because you can
tweak parameters without relying on the GUI.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I hope this helps.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>-Bill</FONT></DIV>
<DIV><FONT face=Arial size=2><A
href="http://www.williamfields.com/">http://www.williamfields.com/</A></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV></BODY></HTML>