Well, that being the case, something along the lines of B is probably
best... so that the DSP part of the plug-in doesn't have to care why the
value is like it is, it just acts on it.
However, the GUI part of the plug-in would still need to know - any GUI
that doesn't know the difference between parameter-state and
realtime-modulation will be completely unusable.
Cheers,
Angus.
but the plug-in still ha
jeffmcc@xxxxxxxxxx wrote:
Hi Angus,
That's an interesting question.
one clarification..
In GMPI, it's the host that holds the parameter state. Not the plugin. Your plugin is able to automate it's own parameters (via the Parameter Pre-Processor/ Actor) but it does so indirectly by hooking into the Host API. What i'm trying to say is, yes we probly need to diferentiate between stateful/non-stateful parameter updates...but it's the Host that gains the complication, not the plugin.
Best Regards, Jeff McClintock SynthEdit
---------------------------------------------------------------------- Generalized Music Plugin Interface (GMPI) public discussion list Participation in this list is contingent upon your abiding by the following rules: Please stay on topic. You are responsible for your own words. Please respect your fellow subscribers. Please do not redistribute anyone else's words without their permission.
Archive: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
---------------------------------------------------------------------- Generalized Music Plugin Interface (GMPI) public discussion list Participation in this list is contingent upon your abiding by the following rules: Please stay on topic. You are responsible for your own words. Please respect your fellow subscribers. Please do not redistribute anyone else's words without their permission.
Archive: //www.freelists.org/archives/gmpi Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe
