[gmpi] Re: Reqs 3.8 Events - ramped events
- From: David Olofson <david@xxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Wed, 7 Jan 2004 15:12:59 +0100
On Wednesday 07 January 2004 14.47, David Olofson wrote:
[...]
> <target, duration> ramps don't have this issue. You don't need to
> have a clue about the current value to generate a proper, click
> free ramp, so it works reliably even if the control input has an
> extremely inaccurate ramping implementation.
BTW, this also means you can safely interrupt long ramps on inputs
that approximate linear ramping. Non-linear approximations make it
impossible to jump in with SET events or <start, delta> events
without the risk of jumps. There's no way the sender can know what
actually happens during a ramp, unless the ramping is *perfectly*
linear.
Note that "clicking" isn't some clearly defined phenomenon that can be
eliminated by a hardwired control filter. A fast envelope *should*
generate sharp transients! The whole point with ramp events is to be
able to express more accurately what you want, so plugins don't have
to be cripled by hardwired 20 Hz LPFs on all control inputs.
//David Olofson - Programmer, Composer, Open Source Advocate
.- Audiality -----------------------------------------------.
| Free/Open Source audio engine for games and multimedia. |
| MIDI, modular synthesis, real time effects, scripting,... |
`-----------------------------------> http://audiality.org -'
--- http://olofson.net --- http://www.reologica.se ---
----------------------------------------------------------------------
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:
