I'm planning to use the coll object to process 'scores' which control a
large number of performance related parameters in a complex patch.
The idea is to have an entry on each list stored in coll which could
determine which part of sequence to play, another to start the relevant
sequencer, others to determine which devices are synch'ed with what, another
index would cause coll to output the instructions to the rest of the patch.
The list could also feed probabilities to a prob object to be used in a
Somethinng like this seems at first sight to be a good answer to the problem
of how to control a lot of parameters in performance. For example, the same
score could be used for different improvised note sequences - so some
flexibility could be preserved.
One potential drawback is that my lists would probably need to have about 50
elements. So I'll probably need to design a score editor to cope!
However, I was wondering if other's have gone down this path or have decided
on a different philosophy of performance.
I await your responses with interest!