[gmpi] Re: Reqs 3.8 Events - ramped events
- From: Steve Harris <S.W.Harris@xxxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Mon, 12 Jan 2004 13:50:55 +0000
On Mon, Jan 12, 2004 at 04:23:41 -0800, Tim Hockin wrote:
> On Mon, Jan 12, 2004 at 12:26:30PM +0100, David Olofson wrote:
> > > The issue is that a sender of events needs to know whether the
> > > receiver can properly handle ramps.
>
> > I think that depends on the implementation. Both <start, delta> and
> > <target, duration> events, in conjunction with the "drive inputs as
> > long as you're connected" rule, will set the target value at the end
> > of the ramp, if the receiver just ignores the ramping ang grabs the
> > start or target value.
>
> You're missing the point - ramps are a shortcut. If a receiver is going to
> disregard the ramp (and use it as a point value instead) then the sender may
> choose to not send a ramp at all, and instead use the more expensive but
> more accurate series of point values. Without that info, the sender might
> send a ramp to an unramped control, which would be worse than having no
> ramps at all.
I would expect the choice of ramp/noramp on the part of the plugin to
depend more on the function of the control.
If you choose no to use ramp because the recalculation cost is too high
then increasing the rate of control points is a bad idea too.
- 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:
