On Sunday, April 11, 2004 11:46 AM [GMT+1=CET], Steve Harris <xxxS.W.Harris@xxxxxxxxxxxxxxxxxx> wrote: >>> OK, but its still no relevant here; it doesn't require DSP plugins to >>> change thier inputs. >> >> It requires the DSP (or whatever accepts the parameter change event) to >> respond that the parameter was NOT accepted as-is and was changed. It is >> essentially an internal change, only it is synchronous to a single other >> external change. > > Yes, but that response is graphical No, it is not (only): that response is hearable in the audio. (assume [0-1] range for params) min = 0.5, max = 0.8, locked (in the sense dmin = dmax) --> request to set min to 0.8 --> DSP checks what the new parameter states would be after setting min to 0.8 --> DSP sees that this would lead to an illegal value for max --> DSP decides to set min to 0.7 and max to 1.0 Let's not forget that these parameters affect the sound. The response to a "set min to 0.5" is the same as for "set min to 0.7" in this case. It's NOT only graphical. > - the actual input value to the plugin > is not being changed, It's just used as a workaround to get the UI to > update. It seems that you would prefer the outside world of the plugin to work with/reflect the requested values (the input values), which are NOT the ones you hear, instead of the correct ones that the DSP has allowed, set and is using to produce the audio you hear. These correct values should be returned to the "requester" imo. 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