<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Thanks for your advices Franck, these are the kind of programming tips I was looking for.
<P>
<P>David
<P>
<P>
<DIV>
<P style="MARGIN: 0cm 0cm 0pt" class=MsoNormal><FONT size=3><FONT face="Times New Roman"><A href="http://www.flickr.com/photos/schafferdavid/">http://www.flickr.com/photos/schafferdavid/</A></FONT></FONT><BR>
<P style="MARGIN: 0cm 0cm 0pt" class=MsoNormal><FONT size=3><FONT face="Times New Roman"><?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p><A href="http://audioblog.arteradio.com/David_Schaffer/">http://audioblog.arteradio.com/David_Schaffer/</A></o:p></FONT></FONT></P></DIV><BR><BR><BR>
<BR>> Date: Mon, 2 Aug 2010 13:02:00 +0200<BR>> From: fbar@footils.org<BR>> To: pd-list@iem.at<BR>> Subject: Re: [PD] CPU saving strategies<BR>> <BR>> Hi,<BR>> <BR>> On Sun, Aug 01, 2010 at 12:35:41PM +0200, David Schaffer wrote:<BR>> > I recently built a midi CC sequencer abs. It helps me add some<BR>> > timeline-based control to my patches. But I came across a problem I never<BR>> > had to deal with before: CPU consumption. I realized I could'nt use more<BR>> > than four instances of my sequencer before the patch would become<BR>> > unmanageable (interface freezes, audio drops, and, finally... a crash) I<BR>> > think this is related to the use of large size arrays. I would be grateful<BR>> > if someone out there could point me to a better data storing/ CPU saving<BR>> > strategy for my sequencer, maybe data structures? Thanks in advance.<BR>> <BR>> You're using way too many debugging GUIs, like [bng] or number boxes. Remove<BR>> all of them that you don't see and optionally speedlimit the updates of those,<BR>> that you want to see. [m_speedlimit] from rj (http://github.com/rjdj/rjlib) can<BR>> be used for speedlimiting.<BR>> <BR>> In general, never patch debuigging stuff like this: <BR>> <BR>> [...]<BR>> |<BR>> [0\ <- a numberbox<BR>> |<BR>> [...]<BR>> <BR>> or this: <BR>> <BR>> [...]<BR>> |<BR>> [bng] <- a GUI bang<BR>> |<BR>> [...]<BR>> <BR>> <BR>> Instead always put the debugging GUIs into their own path like here: <BR>> <BR>> [...]<BR>> |\<BR>> | [0\ <- a numberbox<BR>> |<BR>> [...]<BR>> <BR>> This way it's easier to remove them later, when you're finished debugging your<BR>> patch. Make that a habit.<BR>> <BR>> Ciao<BR>> -- <BR>> Frank Barknecht Do You RjDj.me? _ ______footils.org__<BR>> <BR>> _______________________________________________<BR>> Pd-list@iem.at mailing list<BR>> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list<BR> </body>
</html>