Xpantastic! group photo

Yahoo Groups archive

Xpantastic!

Index last updated: 2026-04-28 23:44 UTC

Thread

Lag/Tracking Generator tips?

Lag/Tracking Generator tips?

2009-01-23 by mattvrazo

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?

Re: Lag/Tracking Generator tips?

2009-01-23 by MeMyself&I

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:
Show quoted textHide quoted text
>
> 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?
>

Re: Lag/Tracking Generator tips?

2009-01-24 by mattvrazo

Thanks-both those examples are helpful.  I have read the manual, but
alas, they only give one or two examples and despite reading again, I
didn't really get the big picture regarding inputs vs. sources.

For the first example-LFO speed doubling via the TG:  Am i using the
LFO1 as INPUT, and the speed of LFO1 as the source?  

--- In xpantastic@yahoogroups.com, "MeMyself&I" <xpander@...> wrote:
>
> 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. 
Show quoted textHide quoted text
> 
> 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?
> >
>

Re: [xpantastic] Re: Lag/Tracking Generator tips?

2009-01-25 by PeWe

Hi !

Try to look at the "track generator" device as a tool to manipulate values of outputs of other devices you select as an input for the tracking generator.
The input device can be nearly anything available in the Xpander and the results can be very obvious or subtle in dependence of what the input device is.
You see 5 values in the TG, 0 / 15 / 31 / 47 / 63 which represent a linear curve which means there´s no manipulation of the input value at all.
In fact a TG "re-scales" any modulation scale appearing at the input of the TG.

Example:
Input is keyboard ( the keyboard of a Matrix 12 is 5 octaves keyspan )
Each value ( see above) of the TG represents one of the octaves of a 61-key keyboard ( lowest note pitch is 0 and highest note is 63 ),- so, if you would reverse the values in the TG ( 63 / 47 / 31 / 15 / 0 ) as a result the keyboard is reversed.

There are more examples,- use a LFO for pulse width modulation of an oscillators square waveform by selecting the desired LFO as input for the TG and the TGs output as a modulation source of the modulation destination OSC1 (and or 2) pulse width. This can be done by selecting the TGs output as a (+) positive modulator of PW in Osc1 and (if you like) as a (-) negative modulator of PW in OSC2.
Normally in this case, you adjust the pulse widh of OSC 1 and 2 to slightly different positive and negative values in the OSC section, let´s say -13 in OSC1 (modulate this w/ the (+) pos. output of the TG) and +16 in OSC2 ( modulate this w/ the (-) neg. output of the TG).
By fine adjusting the LFOs frequency rate and the amount of the 2 modulation sources ( TG pos. and TG neg.) you´ll find your desired pulse with modulaton effect for a specific range of the keyboard but might not be satisfied w/ this sound in other keyranges.
NOW, changing the 5 values of the TG will change the amount of PWM across the keyboard depending on the values you adjust in the TG.
In addition, you can do this w/ the speed of the LFO too by using a 2nd TG, resulting in different LFO speeds modulating PW of the OSCs across the keyboard.
More complex is to use different LFOs to modulate PW of the OSCs separately and to use 1 TG for the amount of modulation across the keyboard and 2 TGs to control the mod speed of the 2 LFOs separately and change the speed across the keyboard.
This is a great tool for pads b.t.w..

You can also scale the behaviour of wheels/levers and or footpedals /continuous controllers, filter cutoff and/or resonance, envelope times and so on. It´s endless possibilities ...

The Xpander is a half modular complex machine and it´s very important you have a imagination of sound before you start programming.
With modulation sources and destinations, their values and manipulation of these values, the sound of the Xpander/ Matrix12 starts to live. It´s a modulation monster.
You have to know what the components in this machine do and the manual is sometimes too much theory.
The only way to learn is experimentation w/ these components over a longer period of time as also using your ears.
The other way around is looking for factory patches which use TGs, analysing the modulations routing, switching things off and on again and trying to find out what happens and why by listening.

Do you have other synths incl. stored patches ?
Try to reprogram these by using the Xpander.

I learned programming the Xpander by reprogramming of some beloved patches of my former OB-8 because I didn´t want to miss these and I also re-programmed patches from the Matrix 1000 w/ the Xpander.

But I´ve also seen people selling their Xpander shortly after purchase because they weren´t satisfied w/ the factory patches and because they were to lazy or had no time to experiment w/ this machine.

Long post and eventually hard to understand, but to explain it in more detail would fill pages.
I own my Xpander since ~ 20 years and I always find new possibilities up today.



mattvrazo schrieb:
Show quoted textHide quoted text

Thanks-both those examples are helpful. I have read the manual, but
alas, they only give one or two examples and despite reading again, I
didn't really get the big picture regarding inputs vs. sources.

For the first example-LFO speed doubling via the TG: Am i using the
LFO1 as INPUT, and the speed of LFO1 as the source?

Re: [xpantastic] Re: Lag/Tracking Generator tips?

2009-01-25 by Tony Cappellini

Thanks PeWe

Actually all of this is quite useful and I' want to try these myself.

It would be great If we could consolidate snippets like into a wiki or
simple database on the web.
Does anyone have enough experience / time to look into this?
Show quoted textHide quoted text
On 1/24/09, PeWe <ha-pewe@...> wrote:
>
>    Hi !
>
> Try to look at the "track generator" device as a tool to manipulate values
> of outputs of other devices you select as an input for the tracking
> generator.
> The input device can be nearly anything available in the Xpander and the
> results can be very obvious or subtle in dependence of what the input device
> is.
> You see 5 values in the TG, 0 / 15 / 31 / 47 / 63 which represent a linear
> curve which means there´s no manipulation of the input value at all.
> In fact a TG "re-scales" any modulation scale appearing at the input of the
> TG.
>
> Example:
> Input is keyboard ( the keyboard of a Matrix 12 is 5 octaves keyspan )
> Each value ( see above) of the TG represents one of the octaves of a 61-key
> keyboard ( lowest note pitch is 0 and highest note is 63 ),- so, if you
> would reverse the values in the TG ( 63 / 47 / 31 / 15 / 0 ) as a result the
> keyboard is reversed.
>
> There are more examples,- use a LFO for pulse width modulation of an
> oscillators square waveform by selecting the desired LFO as input for the TG
> and the TGs output as a modulation source of the modulation destination OSC1
> (and or 2) pulse width. This can be done by selecting the TGs output as a
> (+) positive modulator of PW in Osc1 and (if you like) as a (-) negative
> modulator of PW in OSC2.
> Normally in this case, you adjust the pulse widh of OSC 1 and 2 to slightly
> different positive and negative values in the OSC section, let´s say -13 in
> OSC1 (modulate this w/ the (+) pos. output of the TG) and +16 in OSC2 (
> modulate this w/ the (-) neg. output of the TG).
> By fine adjusting the LFOs frequency rate and the amount of the 2
> modulation sources ( TG pos. and TG neg.) you´ll find your desired pulse
> with modulaton effect for a specific range of the keyboard but might not be
> satisfied w/ this sound in other keyranges.
> NOW, changing the 5 values of the TG will change the amount of PWM across
> the keyboard depending on the values you adjust in the TG.
> In addition, you can do this w/ the speed of the LFO too by using a 2nd TG,
> resulting in different LFO speeds modulating PW of the OSCs across the
> keyboard.
> More complex is to use different LFOs to modulate PW of the OSCs separately
> and to use 1 TG for the amount of modulation across the keyboard and 2 TGs
> to control the mod speed of the 2 LFOs separately and change the speed
> across the keyboard.
> This is a great tool for pads b.t.w..
>
> You can also scale the behaviour of wheels/levers and or footpedals
> /continuous controllers, filter cutoff and/or resonance, envelope times and
> so on. It´s endless possibilities ...
>
> The Xpander is a half modular complex machine and it´s very important you
> have a imagination of sound before you start programming.
> With modulation sources and destinations, their values and manipulation of
> these values, the sound of the Xpander/ Matrix12 starts to live. It´s a
> modulation monster.
> You have to know what the components in this machine do and the manual is
> sometimes too much theory.
> The only way to learn is experimentation w/ these components over a longer
> period of time as also using your ears.
> The other way around is looking for factory patches which use TGs,
> analysing the modulations routing, switching things off and on again and
> trying to find out what happens and why by listening.
>
> Do you have other synths incl. stored patches ?
> Try to reprogram these by using the Xpander.
>
> I learned programming the Xpander by reprogramming of some beloved patches
> of my former OB-8 because I didn´t want to miss these and I also
> re-programmed patches from the Matrix 1000 w/ the Xpander.
>
> But I´ve also seen people selling their Xpander shortly after purchase
> because they weren´t satisfied w/ the factory patches and because they were
> to lazy or had no time to experiment w/ this machine.
>
> Long post and eventually hard to understand, but to explain it in more
> detail would fill pages.
> I own my Xpander since ~ 20 years and I always find new possibilities up
> today.
>
>
>
> mattvrazo schrieb:
>
>  Thanks-both those examples are helpful. I have read the manual, but
> alas, they only give one or two examples and despite reading again, I
> didn't really get the big picture regarding inputs vs. sources.
>
> For the first example-LFO speed doubling via the TG: Am i using the
> LFO1 as INPUT, and the speed of LFO1 as the source?
>
>
>
>  
>

Re: Lag/Tracking Generator tips?

2009-01-25 by Stephen Teller

I would love to hear some examples of this. Do you have anything you can post to 
demonstrate this or any other neat Xpander only type patches? Your knowledge of the 
machine seems very deep.

Stephen


--- In xpantastic@yahoogroups.com, PeWe <ha-pewe@...> wrote:
Show quoted textHide quoted text
>
> Hi !
> 
> Try to look at the "track generator" device as a tool to manipulate 
> values of outputs of other devices you select as an input for the 
> tracking generator.
> The input device can be nearly anything available in the Xpander and the 
> results can be very obvious or subtle in dependence of what the input 
> device is.
> You see 5 values in the TG, 0 / 15 / 31 / 47 / 63 which represent a 
> linear curve which means there´s no manipulation of the input value at all.
> In fact a TG "re-scales" any modulation scale appearing at the input of 
> the TG.
> 
> Example:
> Input is keyboard ( the keyboard of a Matrix 12 is 5 octaves keyspan )
> Each value ( see above) of the TG represents one of the octaves of a 
> 61-key keyboard ( lowest note pitch is 0 and highest note is 63 ),- so, 
> if you would reverse the values in the TG ( 63 / 47 / 31 / 15 / 0 ) as a 
> result the keyboard is reversed.
> 
> There are more examples,- use a LFO for pulse width modulation of an 
> oscillators square waveform by selecting the desired LFO as input for 
> the TG and the TGs output as a modulation source of the modulation 
> destination OSC1 (and or 2) pulse width. This can be done by selecting 
> the TGs output as a (+) positive modulator of PW in Osc1 and (if you 
> like) as a (-) negative modulator of PW in OSC2.
> Normally in this case, you adjust the pulse widh of OSC 1 and 2 to 
> slightly different positive and negative values in the OSC section, 
> let´s say -13 in OSC1 (modulate this w/ the (+) pos. output of the TG) 
> and +16 in OSC2 ( modulate this w/ the (-) neg. output of the TG).
> By fine adjusting the LFOs frequency rate and the amount of the 2 
> modulation sources ( TG pos. and TG neg.) you´ll find your desired pulse 
> with modulaton effect for a specific range of the keyboard but might not 
> be satisfied w/ this sound in other keyranges.
> NOW, changing the 5 values of the TG will change the amount of PWM 
> across the keyboard depending on the values you adjust in the TG.
> In addition, you can do this w/ the speed of the LFO too by using a 2nd 
> TG, resulting in different LFO speeds modulating PW of the OSCs across 
> the keyboard.
> More complex is to use different LFOs to modulate PW of the OSCs 
> separately and to use 1 TG for the amount of modulation across the 
> keyboard and 2 TGs to control the mod speed of the 2 LFOs separately and 
> change the speed across the keyboard.
> This is a great tool for pads b.t.w..
> 
> You can also scale the behaviour of wheels/levers and or footpedals 
> /continuous controllers, filter cutoff and/or resonance, envelope times 
> and so on. It´s endless possibilities ...
> 
> The Xpander is a half modular complex machine and it´s very important 
> you have a imagination of sound before you start programming.
> With modulation sources and destinations, their values and manipulation 
> of these values, the sound of the Xpander/ Matrix12 starts to live. It´s 
> a modulation monster.
> You have to know what the components in this machine do and the manual 
> is sometimes too much theory.
> The only way to learn is experimentation w/ these components over a 
> longer period of time as also using your ears.
> The other way around is looking for factory patches which use TGs, 
> analysing the modulations routing, switching things off and on again and 
> trying to find out what happens and why by listening.
> 
> Do you have other synths incl. stored patches ?
> Try to reprogram these by using the Xpander.
> 
> I learned programming the Xpander by reprogramming of some beloved 
> patches of my former OB-8 because I didn´t want to miss these and I also 
> re-programmed patches from the Matrix 1000 w/ the Xpander.
> 
> But I´ve also seen people selling their Xpander shortly after purchase 
> because they weren´t satisfied w/ the factory patches and because they 
> were to lazy or had no time to experiment w/ this machine.
> 
> Long post and eventually hard to understand, but to explain it in more 
> detail would fill pages.
> I own my Xpander since ~ 20 years and I always find new possibilities up 
> today.
> 
> 
> 
> mattvrazo schrieb:
> >
> > Thanks-both those examples are helpful. I have read the manual, but
> > alas, they only give one or two examples and despite reading again, I
> > didn't really get the big picture regarding inputs vs. sources.
> >
> > For the first example-LFO speed doubling via the TG: Am i using the
> > LFO1 as INPUT, and the speed of LFO1 as the source?
> >
> >
>

Re: Lag/Tracking Generator tips?

2009-01-27 by mattvrazo

Thanks for your time (and energy!) to write this all down.  Very
helpful...  And for me, really the kind of thing that could only be
explained directly-experimenting only gets you so far sometimes!

--- In xpantastic@yahoogroups.com, PeWe <ha-pewe@...> wrote:

>

Re: [xpantastic] Re: Lag/Tracking Generator tips?

2009-01-27 by John Pallister

This is the sort of thing I had in mind for my Xpander Geek site
(http://xpander.geek.nz). Unfortunately I haven't had much time to
play with my Xpander, let alone work on the site.

But if the amount of traffic on this list is anything to go by,
there's still plenty of interest in the Xpander and therefore a
potential user base for a wiki. So I will try and get something set
up and report back to the list. But don't hold your breath...

Cheers,

John :^P

Tony Cappellini wrote:
> Thanks PeWe
> 
> Actually all of this is quite useful and I' want to try these myself.
> 
> It would be great If we could consolidate snippets like into a wiki or
> simple database on the web.
> Does anyone have enough experience / time to look into this?
-- 
John Pallister
john@...

Re: [xpantastic] Re: Lag/Tracking Generator tips?

2009-01-27 by PeWe

Hi Tony, Steven, Matt �n John !

Thx for your friendly responses.

Tony,- in general, it is a good idea creating a wiki or database on the web.

Steven,- because of some over years growing health issues, I�m actually not able to demonstrate any programming tricks by creating records of examples, looking for the desired patches and doing uploads.

All my programming skills and general knowledge of gear is coming from working w/ synths since the late 70th and that means,- I started w/ much easier to program synths than the Xpander.
In fact, I knew all the basics of subtractive synthesis already when I buyed the Xpander at the time it was released in the past.
In other words, I just only had to learn the user interface and the additional functions to come up w/ satisfying results relatively fast,- but I needed 6 weeks of programming the Xpander side by side w/ all my other machines of that time as w/ the manuals on my knees as well.

As a pro, I worked in the times w/ no samplers, romplers, drummachines and sequencers existing in countless recording sessions and several times a week as also performed live w/ many synths on stage, this under time pressure all the time because of the demands of producers, artists and managers and w/ tight budgets of these,- so I had to be fast all the time and to realize their imaginations of sound from scratch.

All this was a good training and leaded to knowledge about many electronic instruments, not only the Xpander and it was also a good training in reading music and playing/creating lines and arranging parts w/ the resulting patches.
But I never collected all these patches and records,- if the work was done and I got my money, the job was finished for me.

You have to imagine, I never had to repeat something in the past, the adjusted patches resided in the edit buffer, the tape started rollin� and I played my parts by hand,- finished,- next one ... and so on.
In addition, every track recorded was a mix of several pathes from several synths/instruments. In the pre-midi times, we recorded several single tracks and did a submix which went to the final track, when midi appeared, we midied up the gear, adjusted the desired levels for each component of the sound needed and printed directly to tape and there was never time to store and archivate all these single-parts and patches as also there was no interest in doing this because no one wanted to listen to the same sound in another tune.
In addition, you would be eventually disappointed if you�d listen to any single patch of a layered patches combo because it was not created to listen to it solo but had to work in the layer.
All these tracks were unique at this time and that was the reason to be in the biz as a, in these times somewhat rare, specialist and making my life w/ it for more than 25 years.
So, all was/is just learning by doing and I work this way up to now.
I don�t need too much presets, it�s much faster to grab one of �em and to edit or starting from scratch.
With thousands of collected patches in a library, you lose overview or you end up being a procurist, spending your time organising you librarys of all the machines instead of making music.

Today, in my home studio, I have 2 different "work-spaces",- the modern DAW-stuff incl. all the virtual instruments and FX plugs as well as my "nostalgic" hardware studio, including a old tape MTR, pure midi sequencers ( hardeware and software), bankmanager/bankloader/editor-software running on old computers and a bunch of old keys and synths from the past,- and it�s hard and time consuming to keep all this alive and in working condition because I simply love it.

Because of the request of total recall, the hardware instruments, even they are good or better sounding than the virtual stuff, are rearly in action. I prefer to play my real instruments but in recording work w/ a DAW, I use the Sonicprojects OPX-Pro for many Oberheim parts, - I also try to preserve my Xpander now.

Now, unfortunally, I suffer from sitting at keyboards, synths and machines w/ a bended back and neck as also standing in large keyboard rigs in countless tour-rehearsals for sometimes more than 10hrs a day as well as performing live w/ large rigs, standing on one leg and operating pedals w/ the other in hundreds of shows over the decades.

I have so much issues w/ the disks, spin column, hip joints and a shoulder now, I have to start a nitemare of therapy this year beginning from yesterday and I hope, I�ll see a stage again maybe in 2010 if possible.
Maybe I have to think about to design my workspace more ergonmic to do long-time work ( if available) just only at home and probably I have to cut down my gear a bit to reduce the schlepp factor which also appears at home if you want to clean the studio room, not only for gigging ( there were roadies anyway all the time).
In any way, I cannot do work anymore if I have to transport and setup my gear myself which means reduction in work and income.

I�d like to see this group alive as long as possible as some kind of knowledge base and meeting point of synth geeks.
I found many useful tech tips here to keep my gear alive and working and I hadn�t found Karl without this group existing.

I�ll read all the mails I recieve here on my machine and chime in if I can, but there�s no chance to put more energy in as neccessary or possible,- this for a unknown period of time.

Best is, some others start w/a wiki or knowledge base and I come up w/ comments if I�ve read it here or wherever and if I have the time.

go ahead ...

PeWe


John Pallister schrieb:
Show quoted textHide quoted text

This is the sort of thing I had in mind for my Xpander Geek site
(http://xpander.geek.nz). Unfortunately I haven't had much time to
play with my Xpander, let alone work on the site.

But if the amount of traffic on this list is anything to go by,
there's still plenty of interest in the Xpander and therefore a
potential user base for a wiki. So I will try and get something set
up and report back to the list. But don't hold your breath...

Cheers,

John :^P

Tony Cappellini wrote:
> Thanks PeWe
>
> Actually all of this is quite useful and I' want to try these myself.
>
> It would be great If we could consolidate snippets like into a wiki or
> simple database on the web.
> Does anyone have enough experience / time to look into this?
--
John Pallister
john@synchromesh.com

Re: [xpantastic] Re: Lag/Tracking Generator tips?

2009-01-27 by John Pallister

Hi PeWe,

Thanks for that interesting post! I hope that your rehab/therapy
goes well, and that you are able to keep making music and making a
living.

Cheers,

John :^P

PeWe wrote:
> 
> 
> Hi Tony, Steven, Matt �n John !
> 
> Thx for your friendly responses.
> 
> Tony,- in general, it is a good idea creating a wiki or database on the web.
-- 
John Pallister
john@...

Re: [xpantastic] Re: Lag/Tracking Generator tips?

2009-01-27 by PeWe

Many thx John,- I hope so and for the 1st time since years I have the 
feel I found good doctors.
Let�s continue exchanging knowledge and tips here,- I stay active.


John Pallister schrieb:
Show quoted textHide quoted text
>
> Hi PeWe,
>
> Thanks for that interesting post! I hope that your rehab/therapy
> goes well, and that you are able to keep making music and making a
> living.
>
> Cheers,
>
> John :^P
>
>

Re: Lag/Tracking Generator tips?

2009-01-30 by mattvrazo

Just as a follow up-I think the main reason I couldn't figure out the
LG or the TG was that I was not treating them as
"interpreters/manipulators" of the INPUT.. I was liberally using them
as a mod source, but not understanding that it was the INPUT that
would ultimately be the thing affecting the destination.

these posts helped substantially in getting me up to speed!


--- In xpantastic@yahoogroups.com, PeWe <ha-pewe@...> wrote:
Show quoted textHide quoted text
>
> Hi !
> 
> Try to look at the "track generator" device as a tool to manipulate 
> values of outputs of other devices you select as an input for the 
> tracking generator.

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.