Really fine possibilities in manipulation of VST-plug-ins!
I have some further questions.


Can the modules LFO and Wobble Generator be triggered via note? They seem to run always.
Perhaps if you only want to modulate the target when stroking a key.

When in LFO Tempo Sync is activated how can I choose measures corresponding to the beat (half, quarter, ...)? I miss concrete half, quarter, ... dotted, ... Only "x.yy Cpb" is possible.

It seems to be that value of Parameter Event Generator always sets the initial value of the target VST parameter and so changes the original VST setting . Is it possible to let the VST-parameter at its original value and the automation starts from this starting point? Perhaps something like read the origin before change?

Is there a computation rule available for the MUX users for the combination of the severals ADSR Env levels inclusive Sustain and the Parameter Event Generator value?

You could use an ADSR + Modulation Mapper.
I made an example, here it is: http://www.mutools.com/mux/library/examples/Test20120808.Mux

Download + drop this file onto the top section of a mux editor, or use the "Open Preset" function.



Cpb = cycles per beat.
So if you set it to 1.0 it will be 1 cycle per beat.
Hold [Cntrl] to make fine parameter changes. That applies to all parameter knobs.



Not yet possible.



The effective parameter value = parameter value + sum of modulations.
The effective parameter value is limited between 0% and 100% so you can't 'over modulate' a parameter. (that would be dangerous in Vst land, Vst doesn't allow that)

I might add regarding LFOs and looped multi point env:

1) No Event Input is connected to the LFO (blue cable): the LFO is free running
2) Event Input is connected to LFO -> LFO is restarted with each note

3) LFO(s) inside the Polysynth -> each note gets it's own LFO (1 and 2 applies)
4) LFO in the top MUX and routed inside a Polysynth via Modulation Input in the Polysynth -> each note gets the same LFO (1 and 2 applies)