Creating M4L patch to control VST Instrument plugin

arbooz65's icon

Hello, I've been trying to use Max MIDI effect to send control data to vst plugin and haven't been able to successfully even make one knob to respond. If I can learn the basics, I can populate the patch with multiple parameters. For time being, even one parameter is enough (like M4L knob to move a knob in the VST plugin (in this case let's say Oscillator 1 shape selector CC 31 on Aura Blofeld Editor VST plugin). The reason I like to set it up this way is to have M4L as intermediate stage to have flexibility for naming the parameters. Right now on my Novation SL mkiii MIDI controller, the parameter names are so long (fed from the VST plugin) that I can't discern any useful info on the knob displays (limited to 10 digits) and it is confusing. By default, Live doesn't allow renaming the configured plugin parameter names, and I was seeking a solution and this seem to be a suggested potential. I need to configure more than 64 parameters so the Novation Components software or using Live plugin Macro is not sufficient. I also tried it as a Max Audio Effect (tried to see if DAW style automation of parameters can be streamlined this way) and still wasn't successful. Thanks for your help.

Roman Thilenius's icon

since pluggo had been killed, this kind of remote thing works different in every host and eventually also in every live and max4live version.

one "solution" (while not answering you question as it was asked) is to host the plug-in in question inside your max4live device.

no idea about the disadvantages which this might have for your use case, but the huge advantage is that you do not have to care about finding the midi map and guess about a parameters resolution; instead you can just control all VST paramaters directly, in floating point resolution, and including those VST parameters which would not allow control via MIDI otherwise.