[gmpi] Re: My plugin system
- From: Tim Hockin <thockin@xxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Mon, 13 Oct 2003 18:48:47 -0700
On Tue, Oct 14, 2003 at 03:49:28AM +0200, Marco Ballini wrote:
> > As I see it, GMPI is not rigth until most everythign else can be a plugin:
> > sequencers, automation engines, tempo control, MIDI in/out. I'd even like
> > to see drivers be plugins, but I'm willing to bend on that :)
> I agree with this vision, though I wouldn't use the word "host". In the
> case where a graph of plugins is wrapped and executed by another plugin,
> a "network plugin", to run this you would need an "host" app.
> Processing the graph could be done by the network plugin, while managing
> buffers of memory could be done by the host.
Ah, but thxp eplugins inside the sub-graph plugin ask their parent for
buffers, so it IS a host, it just passes the requests on to it's own parent,
which may be another plugin. Somewhere up the chain, the real management
happens. That doesn't make it any less of a host.
--
Notice that as computers are becoming easier and easier to use,
suddenly there's a big market for "Dummies" books. Cause and effect,
or merely an ironic juxtaposition of unrelated facts?
----------------------------------------------------------------------
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:
