How to Trigger Envelopes
Although the sequencer was conceived primarily as a complex modulation source, it would have
been a shame not to have allowed it to trigger envelopes somehow. Here’s how…
ModSeq1 and ModSeq2
The list of envelope trigger options (see the envelope panels in TWEAKS & FX) includes two
‘ModSeq’ entries: ModSeq1 means the
leftmost used tap
, while ‘ModSeq2’ means the
next
used tap along
, or Tap4 by default. If no taps at all are connected, ModSeq1 defaults to Tap4
and ModSeq2 remains undefined.
The slider values are interpreted as gates with velocities (see below).
Here’s an example of how the modulation sequencer might appear while playing pitches and
triggering an envelope. The first 8 values control oscillator pitch via the red cable (note that
ModSeq1 can
also
be used to trigger an envelope). The blue dummy connection ensures that
ModSeq2 only uses 4 steps:
to oscillator pitch
to anywhere (e.g. lag generator)
pitch modulation
gates / velocities
unused
Gates and velocities
When envelopes use
ModSeq
, positive values are interpreted as GATE ON including velocity,
while zero and negative values are interpreted as GATE OFF without velocity.
Note that envelope velocity now comes from the sequencer
instead
of from incoming MIDI
notes. Of course regular MIDI note-on velocity is still available in the MIDI & MORE panel.
As gates also need to be closed, the ‘ModSeq’ part of the pattern will usually have to be set at
least twice as fast as the rest. Have another look at the above image: The speed factor of the
tap used for oscillator pitch is set to 2 while the speed factor for the envelope trigger (Tap3) it is
set to only 1 – twice as fast. Although the Tap1 speed factor is also set to 2, this value is
irrelevant as Tap1 is not being used in this patch.
Finally: To compensate for halving the overall speed, simply double the value of
!
39