MuLab & MUX Modular 6.5.33

[mutools]

I would edit the synth via its own editor and when the sound is right, copy-paste the sound to the other intance(s), and only map those parameters that you want to automate.

[bibz1st]

I thought there may be a separate vst that had a bank of mappable parameters for just such a thing, searched on Google but I cant seem to find anything, maybe Im using the wrong words.

[pljones]

It will be great if MUX have an option to link all the contols

The idea of the meta parameters is that they are there to simplify things, not replicate things - i.e. one meta parameter over many parameters.

I think what you're after is a fairly specialist "stitcher of synths" VST wrapper module - tell it the VST synth and the number of instances and it gives you one front panel for the VST and sends events to all copies. There are synths with over 500 controls. I don't know whether you'd really want to be trawling through that many meta parameters trying to find the one you were after normally... It would also have to be able to handle wrapping synths with many audio outputs, too (e.g. 64 outs times multiple instances makes for many outputs from the wrapper).

This needn't be a MuX module - it could easily be a VST, something like jBridge.

[magicmusic]

I know 6.5.35 is release, but the directory for beta in the thread title contain no history file to see easy whats new. maybe it is possible that you put the history file too in this folder to see easy whats new ?

[mutools]

The 'official' change log for release versions is here:
http://www.mutools.com/mulab-mux-change-log.html

Only when doing test phases there also is an intermediate change log in the webfolder that contains the test versions, but no such test phase is active atm. M6.5.35 is the one now.