[gmpi] Re: Parameters / controls / GMPI event system - refreshment
- From: David Olofson <david@xxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Sat, 26 Nov 2005 01:53:15 +0100
On Thursday 24 November 2005 22.08, thockin@xxxxxxxxxx wrote:
[...]
> > So, "events" are a delivery mechanism. What do they deliver?
> > "Parameter Updates" and "Control Signal Updates". As far as
> > coding goes, the two types of events should look the same, it's
> > just the purpose that differs.
>
> So I think we should simplify this and just say that they are the
> same. We've already established the idea of hidden/visible flags and
> stateful/non-stateful flags on parameters.
Real-time safe/not real-time safe? No warranty in either direction,
but can serve as a helpful hint, and since controls are basically all
the same, users can still try running "unsafe" controls in real time
if they have the guts and spare CPU cycles.
I was thinking one might want another flag for any controls that may
reallocate memory, as in, "I may allocate memory, but I don't use
many CPU cycles myself to deal with this control". However, either
you don't care and don't need to know, or you eliminate the problem
by providing a real time memory manager and still don't care - so
there should be no need for plugins to provide that information.
//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:
