Urs Heckmann wrote: > > Why bother with normalized parameters then? Because it's the most convenient way to represent a parameter as a knob position (or as Y-axis for a curve). For user, it's the mapping giving the maximum and most regular resolution, where a parameter change actually makes audible change. Actually it's important to provide host with a conversion function, because mapping based on the generic unit (ie log scale for a parameter expressed in Hz) is not generally the most convenient way to do it. That's why IMHO it's important to have both, or at least something to convert from one representation to another. Steve Harris wrote: > > I dont think custom is needed. I do. Every Ohm Force parameter curves are finetuned depending on the application of the control; it makes huge usability improvment in some cases. -- Laurent ==================================+======================== Laurent de Soras | Ohm Force DSP developer & Software designer | Digital Audio Software mailto:laurent@xxxxxxxxxxxx | http://www.ohmforce.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