automation or triggering functions

[Rainer Straschill <moinsound@googlemail.com>]

Thanks, Raul, for that interesting thread.

Now before I go into my view, I'd like to quote Per:
"I find it difficult to answer because I don't know where the border is"

Now Per, there are a few scripts I got from you which definitely fall
into the "automation" category - how about "chromatic waves"?
On the other hand, Raul defined "automatic" as "by a hw/sw sequencer".
Does Mobius' scripting function qualify as a sequencer? I believe so.
So my location for the line to be drawn (which is actually very
implementation-dependant and technical, not function-related) is
"automation is everything where you use some kind of
sequencer/scripting etc. to either execute a function call within the
time frame of a pre-programmed, longer sequence which forms the piece,
or to execute several function calls triggered by one user command".
And with that definition, even "copy to next track and set that to
half speed immediately" assigned to a footswitch would qualify as
automation.

While I personally work with the "open canvas" approach of Luis Angulo
(which, according to him, might bring surprises everytime), I've
recently tried working with what I call "interactive sequences" (which
are patterns programmed in a sequencer, e.g. Ableton Live, but where I
retain a certain level of control e.g. by being able to repeat, skip
or extend one specific section). Actually, this does not only include
the looping, but also other functions of my computer (e.g. effects
processing).
And this approach can also bring big surprises, simply because while
you define the way the processing is executed, you can still leave the
input material completely open. Defined that perfect sequencer
automation for a specific melody you've composed? Then let the
sequencer run and try to make odd noises instead of playing the melody
and see what happens. Or play the melody, but have the sequencer run
in the wrong tempo.

Just a few thoughts,

           Rainer