accessing VST-parameters of VSTs loaded outside of Max (For Live)

I think for direct parameter control you need to load the VST into a [vst~] object of an M4L device, thus acting like a VST-wrapper. When loading the VST into a track in Live, parameter control is also possible (via the Live API) but requires mapping of each parameter and introduces some latency.

Thank you, BROC.
That's what I feared...
The problem with mapping always is the limited number of assignable parameters. I hope in the case of M4L, there are more than with MIDI. How many parameters does this Live API provide? (I don't really know what this Live API is, actually.)

AFAIK, the number of parameter mappings via the Live API is not limited. But first you need to make the VST parameters visible in Live (using "Configure Mode") and I'm not sure if there is a limitation.

i remember some situation where live had a limit of 400 parameters total. and within live itself the automation i is still 128 i think.
via live api there should not be any limit of the numbers, but for sure you dont want to deal with latency issues and other things broc mentioned.

i would do it in max/msp (first), there are no limits at all.

or, instead of making an amxd you could make a max4live patch. and then host the instrument in question within that patcher...

Hello,
I have a problem linked to this post..
I want to migrate my big old maxmsp patch to Maxforlive and I have some issue with the VST.

I think for direct parameter control you need to load the VST into a [vst~] object of an M4L device, thus acting like a VST-wrapper. When loading the VST into a track in Live, parameter control is also possible (via the Live API) but requires mapping of each parameter and introduces some latency.

I know Max a lot more than Maxforlive and I'm a bit disappointed.
I loaded a VST in a [vst~] inside my maxforlive device and every thing is working properly for sending and receiveing parameters values, but impossible to make automation possible..
I can record them with no problem but when I play them there is like a loop between the automation lane and the parameter and the automation stops (lane is greyed). I have to push "re-enable automation" but of course it's only working few milliseconds.

I saw someone who made a device which allways toggle "re-enable automation" in Live but the problem is then it's not possible anymore to move the parameter during playback and, btw, it's not a very elegant solution...

So, how it is possible to automate a vst parameter inside a [vst~] in Live ?

Here it's a little part of my patch.

Thanks a lot for your help !

Julien

Controlling a [vst~] parameter in M4L works like any other device parameter. It can be done manually or from automation lane. At playback you can switch between the modes but not use both at the same time. I think that's common behaviour of any DAW.

Hello BROC,

thank for your response but I don't manage to make automation in Live reacting in the same way with a regular VST in a track and a VST in a [vst~].

For the first case, it's working pefectly : you record the automation and then during playback if you change the parameter the automation stops (common behaviour), but with an automation of VST inside a [vst~] impossible for me to just play a simple automation, the lane is reseting by itself from the beginning ...

Strange, just did a quick test and it works well for me. There seems something special with your VST. Maybe it sends parameter values at playback which disables the automation lane?