--- Koen Tanghe wrote: > ----- Original Message ----- > From: "Tim Hockin" > > > 1) range change > > - make a new control** with the new range and a new name > > I personally don't like the idea that changing a parameter's range (or > another property) of a parameter would require you to make a new > parameter with a new name! That just doesn't feel right at all to me. It > IS still the same parameter, only some properties have changed, but it > still has the same conceptual meaning (unless you want a parameter to > have another conceptual meaning, and in that case you'd better give it a > different name indeed, but that has nothing to do with merely changing > it's value range). This idea makes me shiver, but actually I don't mind > really, with this heat wave over in Europe, it's a nice refreshment ;-) Heh heh, yeah, I can feel your chills, even through the hot winds blowing over from Europe. ;-) I had the same reaction, I liked everything else about Tim's idea, but not that. However, here's one thing to think of: if we agree to use literal parameter ranges/values (i.e. not normalized ranges, but specific min and max for each parameter, which I really really really really hope that we do, then changing the range of a parameter won't cause any compatibility issues, and therefore won't require a new parameter in Tim's scheme, or any sort of translation at all. Marc __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com ---------------------------------------------------------------------- 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