Xpantastic!

The lag can be applied to every modulation destination, however the guys who made the 
Xpander chose to give you a "hardwire" option for the pitch of both oscillators 
(portamento) and the filter. Also, the LFO has its own lag to smoothen out corners (e.g. 
RND). You can use the lag feeding in every other modulation source (e.g. ENV) but most of 
the obvious choices have a hardwire LAG in the 2nd page already. 

Now, the tracking generator is a fun thing to apply. Just to give you one or two ideas, you 
can use it to double the frequency of the LFO by setting the Tracking Generator to low, 
high, low, high setting. Or to give a brass sound the roughness you could do a high, low, 
high, low, xxx setting using an Envelope as the source and the filter as the destination. 
This way the filter opens, closes,... during the attack phase. The last value would put the 
filter sustain on that level when you chose to max. sustain in the envelope. 

Read the manual, it is all in there with examples. 


--- In xpantastic@yahoogroups.com, "mattvrazo" <vrazomatt@...> wrote:
>
> Hi all,
> I've been wrangling with my Xpander for some months now, and still
> only feel vaguely comfortable when trying to implement the lag and
> tracking generators (i.e. I actually know what they are doing!)
> 
> Starting with the Lag G, my biggest source of confusion is that lag
> can be added on page 2 (to the oscs or filter for example), it can be
> added as a mod source, and then it has its own input on the Lag G
> page...  
> 
> I can't figure out how the input affects the lag when it is then used
> as a mod source elsewhere.  E.g. if you make LFO1 the INPUT, what
> should I expect the result to be on the lag when assigned elsewhere?
> 
> And does the lag INPUT affect the oscs/filter page 2 lag parameter?
> 
> As for the tracking generator, I guess the same question applies-how
> does what is placed as INPUT affect the TG when it is used as a mod
> elsewhere?  
> 
> The function of these has been the hardest aspect of this synth to
> grasp and it is when you start using TG 1 as an INPUT to TG 1 (for
> example), that I really have no idea what's going on!
> 
> Can anyone give me some basic pointers?
>