MUX meta-params not latched on real parameters upon preset load

[Liero]

I just bought MUX - it's an awesome plugin - but I'm having a big problem with the way it behaves with presets.

The way I work is that I have a VST preset of a MUX instance that is housing some VST's that I control with meta-parameters.

The problem is that although the VST preset saves the knob position of meta-parameters, none of the parameters are _actually_ what the meta's say until I touch the knobs once.

This is really frustrating because I have to touch every single meta knob every single time I load an instance to get the knobs to "reset".

Any ideas?

[Liero]

doublepost

[MuTools]

Which host? Which platform?

[Liero]

Windows 10 pro / 64-bit
Reaper 5.27
MUX VST2 / 64-bit 7.2.23

This behavior is most easily evident with plugins like Plogue Chipcrusher, which has a "monotonicity" parameter which makes a lot of noise unless it's value is at 100%.

Drop it into MUX, set meta-parameter to control value "monotonicity", set the meta to 100%, save the plugin as an FX Chain preset.

Load that FX chain preset. The plugin should load with meta showing 100% but noise output would seem to indicate a loaded value of 50%. The value immediately resets if you touch the meta param knob.

[MuTools]

Which exact steps do i have to take to repeat the problem?

[Liero]

Upon further testing it seems like this behavior is actually also evident just by switching MUX presets inside the plugin itself - so it could totally host independent.

Upon loading a preset all meta-parameter controlled values are set to 50% even though the meta-parameter knob position is saved in another state.

[Liero]

Which exact steps do i have to take to repeat the problem?

I'll make a list, just a moment.

[Liero]

Ah, this needs some more testing - it has something to do with PEG's of inactive modulators that I've connected to the parameters.

The 50% value is coming from PEG's that are mapped to the same value as the meta-parameter. The only thing is that the PEG's themselves are connected to modulators that in the setups default state are disabled/bypassed.

So it seems that upon loading a preset the meta-parameter value is parsed first, after which the PEG is checked and the latter value stays as the loaded one.

I'll try to find a workaround for this but conclude that this isn't a bug at all, just something to tackle.

Thanks for the help!