in june i cleaned up and released my red-framework for managing max/jitter patches. it is hosted here and you can get it via anonymous svn checkout. the framework is for stacking, chaining and mixing max/jitter patches and shows my way of organising patches. i've been working on/with it since 2006 and it now contains >100 modules. it can handle jitter, control data, midi and also softvns video under max4.5. welcome to join the project if you are interested. it is easy to write your own modules. installation... (for osx 10.4 and earlier you'll first need to install svn separately) in the terminal type: svn checkout http://red-framework.googlecode.com/svn/trunk/ red-framework-read-only then press (p) to accept permanently. last add the red-framework folder to max's file preferences. it is licensed under gnu gpl v2 and requires max5+jitter for osx. it has not been tested on windows xp yet but should run. concept... modules: generators, modulators, outputs faders: cross, gain, etc. slots = module+fader chain = slots in series stack = slots in parallel mixer = go from parallel to serial //--module: a max/jitter patch following a simple standard it must have 2 inlets: in, ctrl and 2 outlets: out, info the module can be generator, modulator or output //--slot: a slot is a fader + a module slots also have 2 inlets: in, ctrl and 2 outlets: out, info //--stack: builds a stack of slots - serial in and parallel out //--chain: builds a chain of slots - serial in and serial out //--mixer: a mixer of slots - parallel in and serial out pros and cons... why use red-framework? same for jitter, midi, controldata, softvns reusable patches generalised and efficient i have made various bigger performance patches using red-framework special gui/bpatchers for stacks, chains, mixers drawbacks? only discrete events - no msp no opengl or shaders too complicated to perform with went back to my old os9 patch eg. learning the effect chain - not re-ordering!