Re: SUSStutter vs SUSMultiply

[Jeffrey Larson <jeff@zonemobius.com>]

The Mobius interpretation of Stutter comes from this section
of the EDP manual:

   SingleCycleMultiply works as follows. When you have done a Multiply
   and have several Cycles in a loop, pressing Insert will insert
   repetitions of the next Cycle. As the inserts are made you can  
overdub
   a longer phrase over the repetitions of the Cycle. The results  
will be
   inserted into the loop when you press Insert again.
   ...
   This can make very interesting results when working with
   very short Cycles, and that is why it is called StutterMode.

I wasn't exactly sure what that meant, what is implemented is this:

   When you press Stutter (or SUSStutter), you enter "stutter mode".
   In stutter mode, when you reach the end of the current cycle, a copy
   of the current cycle is inserted at that point.  This insertion of
   the cycle copy continues every time you reach the end of the cycle
   until you finaly end Stutter mode.

This "single cycle multiply" is rounded, meaning that you always insert
exactly one cycle, and it is quantized to the end of the cycle.  The  
cycle
you are inserting is always the cycle you are currently in.  If you  
do this
in the last cycle, the effect is very much like ordinary Multiply.  The
main differences between Stutter and Multiply are:

   - Stutter can insert cycles in the middle, Multiply only at the end.
   - Multiply over a previously multiplied loop will "re multiply" and
     remove cycles that were not playing during the multiply, stutter  
never
     removes cycles it only inserts.
   - Stutter only inserts the current cycle, (re)Multiply will append
     all of the cycles if you let it run long enough, then it starts
     over from beginning.

I haven't tried this on my EDP, but re-reading the description it looks
like the EDP may do the insert at the moment the Insert button is
pressed rather than quantizing to the end of the cycle.  It is unclear
to me whether this insert is rounded or unrounded.  The insertion is
apparently the "next cycle" not the current cycle, though personally
I find it more useful to stutter something I've just heard, not remember
what will be in the next cycle.

[Per]
 > Oh, so the live input will not be layered on top of the stuttered  
loop
 > then? Excellent! I didn't know this. That's useful.

The docs say "As the inserts are made you can overdub a longer phrase
over the repetitions of the next cycle".

Jeff