MUX: Problems with Parameter Event Generator

[chrom]

I am interested in MUX but there seem to be some problems especially at my favored controlling section.

1.) when loading a song with MUX incl. (Event Input -> Multi Point Env -> Parameter Event Generator -> VST parameter) it immediately starts automating the target VST parameter although no events are sent to Event Input

2.) Parameter Event Generator can be routed to several VSTs at the same time but it is not possible to select a VST-specific target-parameter for all VSTs; it's not clear which parameters are controlled. Is this wanted?

3.) (only with 1 VST) after changing the target of Parameter Event Generator the parameter automated before cannot be changed; its value seems to be locked by the routing before

[MuTools]

1.) when loading a song with MUX incl. (Event Input -> Multi Point Env -> Parameter Event Generator -> VST parameter) it immediately starts automating the target VST parameter although no events are sent to Event Input

That's how the MPE works. The reason is that when it's used in an effect, it should not need a note to get started. Now in case you don't want that you can use an ADSR + Modulation Mapper to get more control over the MPE's output. See this example: http://www.mutools.com/mux/library/exam ... 120808.Mux
It's with an LFO but the principle is the same.

2.) Parameter Event Generator can be routed to several VSTs at the same time but it is not possible to select a VST-specific target-parameter for all VSTs; it's not clear which parameters are controlled. Is this wanted?

When you want to control multiple parms with 1 mod source, use multiple Parm Event Generators.

3.) (only with 1 VST) after changing the target of Parameter Event Generator the parameter automated before cannot be changed; its value seems to be locked by the routing before

Please elaborate.

[chrom]

regarding 3.)
with a routing (Event Input -> Multi Point Env -> Parameter Event Generator -> VST parameter)

first set target of Parameter Event Generator to parameter A of the VST and work with this constellation

then set target of Parameter Event Generator to parameter B of the VST;
now parameter A shouldn't be bounded to Parameter Event Generator. but you cannot change it in the VST itself; you can adjust its GUI-element but it always jumps back to the last value given by Parameter Event Generator setting

[MuTools]

I can't repeat this. But you wrote that this is only happens with 1 specific VST, right? Then it sounds like it's an issue with that VST, right?