Analogue-sequencer

On Tue, 17 Aug 2004, Paul Nagle wrote:

> here's one to stretch the old grey matter (well, it did mine).

i think mine is broken... heh...

> Create a pattern with a sequence in it on one track. Leave the rest
> inactive. As a precaution to what's coming, make sure all parts have
> that pattern active.

i don't get the part connection here... aren't you just running this
single part with a single track/pattern active? what i do see is this
single step will change randomly upon each repetition... didn't colin's
mail say that the re-assignment only takes place on the step that the
event is active on? so in your case, only step 1 would be randomized? what
am i not seeing?

> what it will throw up. Certainly it sounds nothing like the original
> sequence. And I only put in an event on step one in each case - I
> could have chosen to vary the event for every step!

i have no idea how this happens... :)

> We're heading into wild new territories here gang. Which is nice...

yeah, and i'm totally lost... which is good. maybe when i'm able to get
auxes working on my P3 i will be less lost. :)

i'm *damn* glad i have a month off to learn this thing!

on an interface sidenote... the most efficient interfaces are always those
that are run from human memory, e.g., the combination of a unix command
prompt and a knowledgeable unix geek will always be the fastest way to get
around a computer... what i'm discovering with the P3 is that it is much
the same here. things may seem complicated (like unix), but it is all
easily memorizable (less like unix, heh) which makes you blaze through the
interfacey part without even thinking about things, which slows you
down...

so yes, good job on that part too, colin!

bleep.
out.

---
http://leichenfeld.iuma.com
http://thirdwavecollective.com