[gmpi] Re: Decision time: 8.2

  • From: Steve Harris <S.W.Harris@xxxxxxxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Mon, 25 Aug 2003 10:20:08 +0100

On Sun, Aug 24, 2003 at 03:49:23 -0700, Marc Poirier wrote:
> And then Steve Harris disagreed with that, and then I disagreed with Steve
> and agreed with Mike.  So I guess then that the point of disagreement here
> is whether or not the DSP component should have a way to mark beginning
> and ending of parameter gestures.  And you and Steve are saying "no."  I
> am still saying "yes."

Yes, I think parameter changes should be simple, single "events", a target
and time or a ramp spec. or somesuch.
 
> scenario e:
> 
>     The DSP component of the plugin wants to mark a parameter 
>     gesture, for whatever reason it may have, it wants to and 
>     should be able to.
> 
> Why is there opposition to this?  Why not just let anyone generate these
> begin/end notifications?  Why exclude the plugin itself?
> 
> Here's a real world example, and I know of plugin makers who do this, so
> already we can forcast problems with this arbitrary (so far as I can tell)
> rule:
> 
> The plugin allows for MIDI CCs to control parameters.  And it allows for
> the plugin to "broadcast" these parameter changes resulting from MIDI CCs
> as automated parameter changes, so that they can be recorded as automation
> data in a host app and thus reap the benefits of whatever automation
> editing/handling capabilities that the host provides, which might be
> preferable to dealing with MIDI data.  In order to be able to simulate

I think this is the source of confusion, In this case I think of the
MIDI data as being processed by some UI code, and sent to the plugin as
GMPI data.

To me this is the core distinction between UIs and DSPs:

   Mouse movements       --------
   + whatever   -------> | UI   | ----.
                         --------      \
                         --------       \ --------------
   MIDI data ----------> | UI   | ------- | DSP Plugin |
                         --------  GMPI   --------------
                                   data
                                   only

But obviously that is only my view. I guess your thinking of a DSP plugin
that accepts MIDI data as well. In my model anything that is registered to
receive events arriving at the DSP plugin will have enough information to
be able to replay automation precicely (by definition).

- 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: