OK, so we know some basics of what DoMOAS will contain (see Paul quoted
below).
What I'd like to talk about is the possibility of optimizing the controls to
make DoMOAS a kick ass performance sequencer as well. I'll throw out a
couple of ideas, but I am an old fart and don't know what's currently
currently available in other systems like X0X, 777, Cyclodon, etc. etc.
Someone please clue me in as to cool things that are already possible with
these and other systems.
For starters, it seems like you'd want to be able to modify Chains in real
time, or even create one on the fly while the sequencer is playing. You
would want to have access to all the HOLD, LOOP, FORK etc. commands, perhaps
from dedicated buttons.
Also, it seems like you would want multiple outputs, like maybe 4. Then you
could assign patterns and chains to more than 1 output, and even have
control over starting and stopping, looping, etc. independently on each
output. How about playing one chain at double or half speed?
If this thing was interactive enough, I'd probably mount it in a tabletop
box instead of my main synth cab.
Dave
> From: "Paul Schreiber" <synth1@...>
>
> There are 99 memorys (#1-99). The length is set to say 16. You twiddle the
> 16 pots
> to the correct voltages, press <STORE>. (You 'alpha' in the location with
> the data entry knob).
>
> A <CHAIN> is another memory, that stores sequences of memory locations. A
> <CHAIN> might be:
>
> 1-2-45-3-74-1-70.
>
> In other words, it plays the notes in #1, followed by #2, followed by #45,
> etc.
>
> Of course, we could place a <HOLD> in the <CHAIN> until, say, a
> <GATE IN> is
> sensed.
> or a <HOLD/LOOP> that repeats the <CHAIN> over and over until <GATE IN> is
> active, then it proceeds.
>
> OR, a more bizarre <FORK>, which means if <GATE IN> is active ∗at that
> time∗, go on, else
> branch to another <CHAIN>. Or a <HOLD CC>, which releases the <HOLD> if a
> MIDI CC message is active........
>
> The joys of the lowly microprocessor. Take ∗that∗, lowy Moog 960.