[gmpi] Re: 3.11 Parameters
- From: Steve Harris <S.W.Harris@xxxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 31 Mar 2004 18:10:20 +0100
On Wed, Mar 31, 2004 at 08:48:42 -0800, Tim Hockin wrote:
> On Wed, Mar 31, 2004 at 02:56:04PM +0100, Steve Harris wrote:
> > On Tue, Mar 30, 2004 at 08:13:10 -0700, Mike Berry wrote:
> > > - Can we have a way for a parameter to reveal its linkages to other
> > > parameters? I.e., if the host changes parameter 2, parameters 4 and 5
> > > may change?
> >
> > Do you have a use case for this? How will the changes be communicated back
> > to the host, and how does it play with automation?
>
> I've seen it used to great success in a filter, where the resonance was tied
> to the cutoff. When you turn the cutoff down, the resonance would go down.
> It was non-linear and non-obvious what the functional relationship was, but
> it was clearly functional. That's the only time I've seen it. And that
> didn't srictly NEED to be exposed, but it was nice to see the knobs move :)
How would the host handle that if the cutoff and resonanance were
automated simultaneously? Most filters I know link the resonance to the
cutoff internally, but they dont expose that to the user in that way. You
have a consisent resonance value that sound appropriate over the usable
range of cutoffs.
- Steve
----------------------------------------------------------------------
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:
