Ok, I'd like to propose a "patch-off." What's the cleanest, clearest way to present adsr.pd from the audio tutorials?
I choose this patch because there are lots of crossed wires, plus one has to leave space for the explanatory comments of the patch. Here are two versions I could think of. -Jonathan --- On Fri, 3/20/09, Mathieu Bouchard <ma...@artengine.ca> wrote: > From: Mathieu Bouchard <ma...@artengine.ca> > Subject: Re: [PD] style guide idea: [send foo] versus [; foo( > To: "Frank Barknecht" <f...@footils.org> > Cc: pd-list@iem.at > Date: Friday, March 20, 2009, 9:05 PM > On Fri, 20 Mar 2009, Frank Barknecht wrote: > > > For example I'd rather start with making people > properly left-align their patches and avoid crossing patch > cords > > well, I do my best to reduce the number of crossings, but > if I have to avoid crossings completely, I'll just avoid > Pd... > > Pd doesn't make it easy to avoid crossings. > > Not all crossings are even bad. Crossings that are > ambiguous-looking are very bad. Too many crossings in the > same area is bad, except if the crossings are very > regular-looking (a line crossing a bunch of parallel lines > is more orderly than a line crossing a bunch of > random-angled lines). > > _ _ __ ___ _____ ________ _____________ > _____________________ ... > | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, > Québec_______________________________________________ > Pd-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list
adsr.pd
Description: application/puredata
adsr2.pd
Description: application/puredata
_______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
