[PD] Profiling PD patches and externals.

[Gerhard Kern]

hi,
look on my website www.musikmechaniker.blogspot.de <http://www.musikmechaniker.blogspot.de/>
all instruments works with pd

please, if you will answer. make it in german, my english knowledes are not good.

gerhard kern
musikmechaniker // künstlerische projekte
am ziegelgrund 26 50170 kerpen-buir tel. 02275 6778 mail gkern at ihp.de

> Am 14.03.2016 um 21:13 schrieb Rafael Vega <contacto at rafaelvega.co>:
> 
> Hi.
> 
> I've been working on a synthesizer built with PD and running it on a BeagleBone Black [1]. For this, I've written a number of abstractions and two externals. Right now the synth is monophonic and uses 100% CPU when started, causing many audible clicks and artifacts. After about 5 seconds, it "stabilizes" down to 75% CPU and the latency and sound is pretty good.
> 
> Now, I need to make the synth polyphonic so CPU time has to be freed for the additional voices. For this, I'm thinking about building PD with debug symbols and running my patch through a profiler such as Callgrind/KCacheGrind to try to figure out where most CPU consumption is happening and optimizing around that.
> 
> Can anyone share any techniques or tips used to optimize PD patches and externals? Are there any tools specific for PD for this kind of task? Any reason why my approach would or would not work?
> 
> Thanks!
> 
> Rafael Vega.
> 
> [1] http://beagleboard.org/black
> 
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20160314/c14c4191/attachment.html>