[gmpi] Re: 3.11 Parameters
- From: "Ben" <ben@xxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Fri, 02 Apr 2004 08:25:03 -0600 CST
I don't have time to closely follow the list, so sorry if this is redundant.
I'd like to support Tim's post and add a bit.
It seems to me there must be some data repository where the "actual" parameter
value lives. The DSP takes this value and truncates it to the values it can
support. A graphics knob will only display values within the limits of it's
range. But if two controls are "linked" with an offset, and then one of the
values is driven beyond the limits of it's range, the true values must be
preserved so that when the values move back into the valid range, the offset is
preserved.
-Ben Loftis
> Date: Thu, 1 Apr 2004 18:11:03 -0800
> From: Tim Hockin <thockin@xxxxxxxxxx>
> Subject: [gmpi] Re: 3.11 Parameters
>
>
...
> Some of the function callbacks can be eliminated by assuming that any value
> that is in-bounds will be accepted AS-IS by the plugin. That is, if I set
> paramX (which is 0-200 range) to 123, the value will ALWAYS be set to 123.
> Under no conditions will the plugin say "you sent 123, but I changed it to
> 100". The plugin might do things internally based on other parameters,
> butthe exposed parameter would never be rejected while in-bounds.
>
....
----------------------------------------------------------------------
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
Other related posts:
