[gmpi] Re: Decision time: 8.2

--- Steve Harris wrote:
> 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.

They still would be.  It's just that there would also be these other
events that can be used to mark the beginnings and ending of parameter
change gestures, too.  And those are *optional* for the DSP component to
use itself, *if it needs to*.  And you agree that those events need to
exist anyway, it's just that you're saying that they shouldn't even be
available to the DSP component, even if it might need them.  That I don't
understand.  That will only make life harder for some developers, and
simpler for no one.

Why can't anyone seem to really explain why they are opposed to this? 
This is getting tiresome...

> 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

Where does this model come from?  It certainly is nothing like any I've
seen with any plugin APIs or MIDI i/o implementations.  I've never seen
MIDI be mitigated by any sort of UI, it is usually a high priority data
stream directly for the DSP component just like audio.  But if it does
work this way, then okay, my scenario would still work with the DSP
component being crippled out of the ability to post parameter change
gesture begin/end events.  But this is definitely not how I've ever seen
things work, so admittedly it seems not very real-world or dependable to
me...

> But obviously that is only my view. I guess your thinking of a DSP
> plugin that accepts MIDI data as well.

Yes, like almost every plugin that I've made.

Marc

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

----------------------------------------------------------------------
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: http://www.freelists.org/archives/gmpi
Email gmpi-request@xxxxxxxxxxxxx w/ subject "unsubscribe" to unsubscribe

Other related posts: