[PD] Managing really big PD projects?? Style guide or best practice etc?

HI all,

I have been building a project in pd and lately it has got difficult to manage because of the complex web of spagetti all over the place.

I'd like to hear others' advice on sensible architectures for PD projects to prevent them becoming unweildy and confusing.

Especially, how you deal with:

• lots of abstractions with multiple instances
• send and receive objects and remembering where they all go to - come from
• identifying where slow-downs occur in big patch networks
• keeping notes of your project in a way that makes sense after not looking

at it for a month or two. :)

I would be keen to collect all these pearls of wisdom into one doc for the wiki or somewhere, if one does not already exist.

Cheers, Rod

Rodney Berry ATR Media Information Science Laboratories Kyoto Japan