On Tue, Apr 13, 2004 at 06:33:37PM +0100, Steve Harris wrote: > > No, just send back a change notification to the clipped value. > > That is a horribly inelegant colution - think of the implications on using > a graphical UI, plus theres no hint to the user that that range has > changed. I don't see a clean way to do parameter clipping without making another level of dynamism on top of parameters. The ideal would be that the GUI knob would just stop rotating at a certain point, until the clip was resolved. Making it go past the clip then come back after some latency DOES suck. A custom GUI can probably provide the ideal behavior, but a motorized fader or an LED-encircled endless rotary encode has the latency problem. I think we're travelling down a rat-hole and we need to punt on some of the details. How can we characterize this all as reqs? ---------------------------------------------------------------------- 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