Roth

I've observed the [vst~] not correctly setting parameters on the hosted plug-in (

) if there are a large number of automation parameters (e.g. 285). 

Is there a limit to the number of supported parameters? I'm guessing there might be a 64 parameter limit, as I seem to have no problem setting parameters on a plugin with 63 parameters.

In the case of the 285 parameter plug-in, it seems all parameter setting was broken (e.g. I saw no UI updates and could not trigger debugger break points setting parameter 25 for the 285 parameter plug-in).

I've observed the [vst~] not correctly setting parameters on the hosted plug-in (I tried AU, VST2, and VST3) if there are a large number of automation parameters (e.g. 285). 

Is there a limit to the number of supported parameters? I'm guessing there might be a 64 parameter limit, as I seem to have no problem setting parameters on a plugin with 63 parameters.

In the case of the 285 parameter plug-in, it seems all parameter setting was broken (e.g. I saw no UI updates and could not trigger debugger break points setting parameter 25 for the 285 parameter plug-in).

I've observed the [vst~] not correctly setting parameters on the hosted plug-in (I tried AU, VST2, and VST3) if there are a large number of 

-possible-bug-does-vst~-support-a-maximum-number-of-parameters

After additional attempts to reproduce the issue, it now seems that I only encounter this problem loading an AudioUnit.

As another data point, I recompiled the plug-in with 285 parameters, reducing the number of exposed parameters to 48 and the issue went away.

After additional attempts to reproduce the issue, it now seems that I only encounter this problem loading an AudioUnit.

As another data point, I recompiled the plug-in with 285 parameters, reducing the number of exposed parameters to 48 and the issue went away.

64 would exclude half the existing plug-ins if you think about it.

[Possible bug] Does vst~ have a maximum number of supported parameters?