Hello all in list-land,
Part of my undergrad thesis is a little paper on Max-type language
(Max, Pd, jMax) patch design methodology. Things like how to go about designing effective patches, design rules that make debugging easier, patch organisational models, etc. The aim of the paper is to come up with a set of rules for designing "effective" patches, as a guide for beginners and also as a set of tips for seasoned users.
I've been recently codifying my own methods for the paper. And any
thoughts, tips, or insight that any of you can offer about your own methods and practises would be greatly appreciated.
David
. . David McCallum . Music wants to be free . http://mentalfloss.ca/sintheta/ .
Hi David,
2c worth of thought; generally I find that those things which apply to good software design also apply to good patch design. Modularity, re-use, clear commenting/labelling etc. If I was you i'd get out some books on software design and see how much of it applies to patching. Of course with Pd you also have the pleasant aesthetic aspect of the design. Which is why all my knobs and sliders are orange.
Chris.
On Tue, Jan 14, 2003 at 01:46:47AM -0500, David McCallum wrote:
Hello all in list-land,
Part of my undergrad thesis is a little paper on Max-type language
(Max, Pd, jMax) patch design methodology. Things like how to go about designing effective patches, design rules that make debugging easier, patch organisational models, etc. The aim of the paper is to come up with a set of rules for designing "effective" patches, as a guide for beginners and also as a set of tips for seasoned users.
I've been recently codifying my own methods for the paper. And any
thoughts, tips, or insight that any of you can offer about your own methods and practises would be greatly appreciated.
David
. . David McCallum . Music wants to be free . http://mentalfloss.ca/sintheta/ .
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list