Analogue-sequencer

On Tue, 17 Aug 2004 16:24:37 -0500 (CDT), blip <bleep@waste.org>
wrote:

>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?

It randomises the event type. So it could be altering pattern length
on one pass, muting a track on another. It can mute itself of course
and at that point it means it's ready to finish. This critter has a
mind of its own... 8)

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

Great innit? 

>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. :)

Come here. Bring drugs.

>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...

Despite its size and apparent inscrutibility, the interface can be
very fast indeed. 

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

We are not worthy... OK, I'm not... 8)

Paul
---
Paul Nagle / Soft Room Music
Email: paul@softroom.co.uk www.softroom.co.uk
                           www.BogusFocus.com