Discussion Items

###Layers and grouping

*Groups constitute of layers (Is this a question?)

*Each layer has a unique order number Yes

*A source can show up on multiple layers and hence be affiliated with multiple order numbers Yes

*Are we gonna do any inheritance? (I don't think it is necessary) however maybe we should think about "copying effects" from one layer to another?

I wouldn't call it inheritance, but settings should be in a struct or object that is "copyable". The main issue to resolve here is what should be copyable? I think you can duplicate a layer (which will duplicate everything except for the layer order number). And you can copy individual effect parameters, and layer transform parameters. But these copying behaviors need to be isolated, as not every layer will have all of the same effects, etc.

###External controllers

*It would be cool if we could make the parsing somehow dynamic/extensible so that when we switch GUI applications (such as mrmr vs touchOSC or even ipod vs androids, maybe even bluetooth etc), the system is still usable (maybe add these into settings?)

I don't quite understand this questions.

*Are we gonna support midi controllers?

Not directly, and not in this first version. Easiest solution is create a Max controller that will convert MIDI to livedraw OSC.

*Also, since we know what effects/transformations can have external control, maybe we can allow linking some of those to openCV utils?

I don't quite understand this question, but again, I think for the first version, this should happen via a Max bridge.