----- Original Message ----- From: "Tim Hockin" <thockin@xxxxxxxxxx> > > 8d.) Is there a heirarchy of parameters? > > Not clear what you mean? I definitely see a need for sub-units within a > plugin, in which parameters exist. Something à la OSC (Open Sound Control): addressing of parameters is done using strings looking like paths: "\synth1\filters\1\cutoff" (don't recall if it's actually like that with OSC, but it gives the idea). Don't know about the cost of parsing this though! > I also see a use for something I've dubbed an 'argument'. An Argument is > something passed to the plugin at creation time - for example, a wrapper > plugin would have an argument of the plugin to wrap. Those would be > unchangeable. > > If you can take the view that EVERYTHING (except arguments) is a parameter > (or 'control' in XAP), then sequencing becomes a case of automation playback. > > MIDI note-on becomes a change in the NOTE parameter. Aftertouch becomes a > stream of changes to the AFTERTOUCH parameter. Filter sweeps become a stream > of changes to the CUTOFF parameter. Tempo changes become a change to the > TEMPO control. If a plugin doesn't have a tempo param, it must not care > about the host tempo. If a plugin has a NOTE param, it can be played by the > sequencer. > > It's pretty different than anything that I've seen out there, but it seems > to be pretty elegant. Yes, it does seem so. Koen ---------------------------------------------------------------------- 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