On 01.01.2012, at 20:33, Kassen wrote:
> Alex;
>
>> The version of Pure Events that Ade Ward has been live coding with for
>> several years is a tracker, where the events are javascript functions.
>> Hopefully he will pop up and explain but I think it makes a nice
>> point that trackers are spreadsheets plus time.
>
>
> That'd be nice.
> I think trackers are a bit more (in a relevant way); aside from
> playback instructions they also have instructions on the way time runs
> through them (skip the rest of the pattern, time offsets for shuffle,
> etc) and a set of specialised input macros.
>
> The way I'm imagining a "livecoding tracker" is like a tracker but
> instead of slots for samples there would be slots for synthesis code
> where reserved variables would correspond to the fields for
> parameters. There would also be a field for the time playback which
> could default to something like;
>
> every beat
> play the "step" in each channel
> increment the step counter
>
> Maybe there'd also be a repl to write quick commands in to fill the
> "spreadsheet".
>
> In my mind's eye this would be quite a nice thing to have.
>
> Kas.
There is one tracker that works like this for SC and jitlib, it's called "eternal return", and you can rewrite not only code, but also your own past, while all that is not changed keeps running.
Received on Sun Jan 01 2012 - 22:46:41 GMT