On Sat, Apr 10, 2004 at 09:29:43AM -0400, Paul Davis wrote: > >On Sat, Apr 10, 2004 at 08:46:21AM -0400, Paul Davis wrote: > >> a randomize button in the UI should lead the UI to generate random > >> values, not the plugin(s). > > > >So I'm asking you again: > > > >Does this mean that a plugin without a custom GUI can not do things like > >morphs? > > > >Does this mean that I can't use a MIDI note as a trigger to start a morph? > > > >Does this mean I can not clip a param based on another param? > > i don't think steve's example is related to morphing, for one simple I assumed "continuous randomization" as opposed to one-off randomization. I agree that this should be host-centric or UI centric. This does touch a bit on patch loading, though. Are plugins not allowed to do patch manatgement themselves? I know a lot of VSTs that have their own way of doing bank/patch files that would not be happy if we told them they can't do that anymore. > reason. a plugin cannot do anything that would lead to > proxied/stacked/duplicated/whatever-you-call-it plugins ending up with > different parameter values. I have no idea what you're saying here.. > thus, no, you cannot use a MIDI note to trigger randomization of > parameter values. randomization != morphing, and it can only be > initiated by a layer that understands the > proxied/stack/duplicated/whatever-you-call-it plugin arrangement. If I can't use odd MIDI rigs to change stuff, GMPI seems less fun than VST. I'm not saying that it seems useful for a plugin to map it's MIDI keyboard input to individual params, but plugins today are using certain MIDI keys as triggers to do morphs and such. ---------------------------------------------------------------------- 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