[gmpi] Re: 3.15 MIDI (What does it mean to be a plugin)
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Tue, 22 Jun 2004 01:06:50 -0700
On Tue, Jun 22, 2004 at 01:02:11AM -0700, Chris Grigg wrote:
> Yeah, fine, but I'm having trouble parsing you w/r/t what you're
> saying about Mike's objection, you started out with 'primary
> tenet...awkward to get multiple... responses...," but then you
That was paraphrasing Mike, who found it very awkward to handle.
> switched to timing -- is that secondary, then? Or is it that it's
Timing is another issue, which also appears when we divorce UI from DSP.
> not the necessity of plugs making and hosts handling the
> setParameterAutomated() calls Mike objects to -- since there would be
> similar calls in different places with Actors -- it's just that the
> particular design of VST's setParameterAutomated() system sucks?
setParameterAutomated() is non-causal, was what I THINK he was bitching
about. Setting param P1 in an event would result in 1, 2, 3, 5, 100 calls
to setParameterAutomated().
Mike, am I catching your intent?
----------------------------------------------------------------------
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:
