There’s this thing I like to do on Teletype that is clocking scripts with
M set on a tempo (like a multiple of 120 BPM, for example), then multiplying that speed via probability and stuff.
// M --------------------
M BPM T // T is set to a specific BPM, let's imagine it's 120.
PROB 50: T * 120 RRND 1 4 // multiply tempo by a random integer up to 4, sometimes
$ 1; TR.P 4 // idk, clock stuff
This, while it creates some cool ratcheting and funky grooves, you can’t output anything steady off it due to master tempo manipulation. This problem would arise when using up a trigger output for clocking other things like delays and stuff (which is the driving force behind this haiku).
So, while we’re on the topic of clocking delays, some time ago I was doing something similar to this and tried to clock a Chronoblob 2. Needless to say, it was all over the place, so it called for an unsteady groove from a steady one.
Cue this single line:
EV X: $ 1; X RRND 1 4 // yup, groovier than PROB 50:
In the grand scheme of things, this is dastardly simple: every
X times, change
X and do stuff, not much else to it. But, my mind exploded. I could keep the groovy clocking within Teletype and have a typical clock keeping other things in steady check within a patch. I managed to have my cake and eat it too in terms of generative scripting and delay clocking. It was a revelation to me.
I bring this silly simple little stupid verse here to appreciate how simple things in programming can be so effective, and at times, even mind-expanding.