[gmpi] Re: Reqs 3.8 Events - ramped events
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Mon, 12 Jan 2004 17:57:36 -0800
On Mon, Jan 12, 2004 at 05:42:08PM -0800, Chris Grigg wrote:
> So, what if each parameter (OK, the control that drives each
> parameter) publishes two pieces of info: the max update rate of
> whatever internal DSP parameter(s) it drives, and whether the control
> implements ramping (within the plug)? This way, a) you get the
> possibility of allowing an ambitious host to implement ramping for
> any control of any plug (i.e. even if the plug itself doesn't
> implement it), and b) there's no risk of inefficiency from generating
> too many update events because you only generate them as often as
> needed.
I'm OK with something like this. Plugins that don't want to handle ramping
can get pseudo-ramped by the host. Plugins that can handle it themselves
will. Is the max update rate needed? It makes things obvious, I guess.
Not sure. What do others think?
Tim
----------------------------------------------------------------------
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:
