Archive of the former Yahoo!Groups mailing list: MOTM

previous by date index next by date
  topic list next in topic

Subject: Re: [motm] Using a Lag an an Envelope Follower -- Not Quite

From: jwbarlow@...
Date: 2000-07-21

In a message dated 7/20/2000 7:01:01 AM, ken.tkacs@... writes:

>
>Yes, that's right-

Thanks Ken for this more accurate (and detailed) explanation!

>Since the input signal can be anywhere from 0-20kHz in frequency, usually
>there is a "Range" control, such a as three position switch, to control
>the
>general "speed" of the integrator, tailoring it to a good range for the
>input signal. That gives you a voltage out corresponding pretty nicely
>with
>the envelope of the input signal, which is the _general_ amplitude at any
>particular time (not following every peak-and-trough of the waveform).

I like these basic controls here Ken, but one reason why I keep harping on
certain controls (which I think seem extremely useful and not too costly --
similar to the mixing inputs on the VCFs), is because they might be a bit
more unusual than one might think. I have two EF about three feet from me
right now, the one on the ARP 2600 has one control (an attenuator which seems
to merely attenuate the input and control the amount of EF in that way),
while the Serge EF (a Preamp/Envelope Follower module) has NO control on the
EF portion at all (when the preamp is used as an input, the PA level control
works the way the EF on the ARP does).

When I use my ARP EF, I usually run it through the Lag Processor first, then
to a VCF or some similar thing. When I use my Serge EF, I usually run it into
one of the DSG slope generators for different rise and fall rates and limited
VC lag ability (much more useful than the ARP LP, but the MOTM looks to be a
killer in this respect).

So, if some limited lag processing could be implemented on board the EF
itself, it could save an 820 to be used elsewhere (or for more exotic EF
patches).

>Finally, some of this is tapped off and fed to something like a Schmidtt
>(sp?) Trigger to produce a gate. (It's cool, by the way, when you can set
>the rise/fall thresholds here, because you can create a flexible gate
>delay/hold that way.)


Again, neither of mine have a gate out, and this seems like such an obvious
addition to an EF. I REALLY like the idea of having separate rise and fall
thresholds. Also, this portion of the module seems like a useful place for a
Bradley LED.

I'm saying all this since so few people read my posts anymore, and we never
get to submit features for future modules anymore, I'm hoping to start some
kind of a wave of enthusiasm!
JB