Tempo-Based Parameters: T_Rate, T_Delay, T_Tap, Etc - Eventide Eclipse User Manual

In cases exemplified by
alter parameters for both filters simultaneously. Its parameters are "un-
adorned," for example
screen to the right. Parameters that only pertain to filter 1 have "
pended to their rears. For example, in the third screen to the right we see
(GAIN1) , (FREQ1) , and
In cases exemplified by
will scale the "absolute" parameter values found under
, etc. To the right, we see four menu pages, with the bottom
DELAY#2
three found under the soft keys of the top screen (
and ). The absolute value of
DELAY#2
absolute value of
(DELAY2)
to . Consequently, the actual delay times are 100ms and 200ms. By altering
50%
the relative difference between the two delays (in this case, delay2 is always twice as long as delay1).
You will see other cases of
What's more,
HOT KEYS

Tempo-based Parameters: T_RATE, T_DELAY, T_TAP, etc.

The Eclipse's little heart is always thumping to the beat of its "tempo." The tempo can be keyed in, tapped in
on the key, derived from a sequencer connected to the Eclipse's MIDI in, and so on
TAP
the Eclipse's delays and LFOs automatically synchronize to the tempo. It works like this
example, but other " " parameters behave similarly)
T_
A delay parameter will have two soft keys associated with it; one will say
(DELAY1) or something like that, while the other will have a "
to its name: (T_DELAY1)
is selected in rhythmic terms:
(T_DELAY1)
note , whole note , etc. Assuming the tempo is synched to the music that
is being effected, the delay shown to the right will repeat after a 1/8th note.
The (DELAY1) parameter does two things. First, if you press its soft key
but don't turn the knob, it "reports" the actual delay time in milliseconds as
a function of the tempo and the value of
If, however, you turn the knob to change the delay time in milliseconds,
will override the value derived from the tempo and
(DELAY1)
But get this: if you now update the tempo (by tapping the
ample) or alter
(T_DELAY1)
the value of
(T_DELAY1)
Think of them as warring nations. On one side you have
side you have the tempo and
by which side "moved" last. If you alter
determines the actual delay time. If you alter the tempo or
(DELAY1)
alone, then the tempo and
However, if you set
(T_DELAY1)
determined solely by
(DELAY1)
Release 2.500
Eclipse User Manual
dual filters , a MASTER
, , and
(GAIN) (FREQ)
(Q1) .
, a
m_pandelays MASTER
(DELAY1)
is . However, both of those values are scaled by
400 ms
menu pages that behave similarly to the ones we have described.
MASTER
often link to these "master" controls.
:
. The " T_ " stands for "tempo."
1/8 note
(T_DELAY1)
, the delay time will once again be derived from
in combination with the tempo.
teamed up (in rhythmic terms). The actual delay is determined
(T_DELAY1)
(DELAY1)
(T_DELAY1) determine the actual delay time.
to , then the actual delay time will be
off
in terms of milliseconds. If you want all of
Page 35 of 64
menu page exists that will
shown on the second
(Q)
" ap-
1
menu page exists that
DELAY#1
,
MASTERS DELAY#1
is , and the
200 ms
T_ " appended
, ,
1/8 trip 1/16
.
(T_DELAY1)
key for ex-
TAP
(in terms of milliseconds). On the other
(DELAY1)
and leave the tempo and
,
,
(M_DELAY)
, you preserve
(M_DELAY)
(see page 15)
(we'll use a delay as an
.
(T_DELAY1)
and leave
(T_DELAY1)
Eclipse User Manual
, which is set
. Most of
alone, then
(DELAY1)