[gmpi] Re: Requirements
- From: "Michael Gogins" <gogins@xxxxxxxxxxxx>
- To: <gmpi@xxxxxxxxxxxxx>
- Date: Sun, 16 Nov 2003 00:41:13 -0500
In many cases a developer will create a class library of unit generators
that will be used as building blocks for signal processing or synthesis.
Suppose the developer produces 5 plugins, and each plugin uses a wavetable
oscillator unit, an envelope generator unit, a delay line unit, and a quad
filter unit. If there are 5 separate DLLs for 5 libraries, there is an
oscillator, an envelope generator, etc., in each DLL (or else there is a
separate DLL). If all plugins are in 1 DLL there is no duplication of unit
generator library code.
============================================
Michael Gogins
gogins at pipeline period com
Irreducible Productions
CsoundVST, an extended version of Csound for programming music and sound
Available at http://sourceforge.net/projects/csound/
============================================
----- Original Message -----
From: "Marco Ballini" <marcoballini@xxxxxxxxx>
To: <gmpi@xxxxxxxxxxxxx>
Sent: Saturday, November 15, 2003 11:00 AM
Subject: [gmpi] Re: Requirements
> On Sat, 2003-11-15 at 05:25, Tim Hockin wrote:
> > > About multiple plugions in a single file.
> > > Is that really needed? Sorry, I missed why (too many e-mails to read).
> > > Could anybody briefly explain or pointing me in the right direction?
> >
> > Is there a good reason to disallow it?
>
> Simplicity. Both from the point of view of the host and of the user (1
> file corrispond to 1 plugin => easier to remember where a plugin is).
> I really don't see the advantage of having multiple plugins in a file,
> except for the reason of having many plugins doing the same thing, but
> where controls are once streams and once single-events (see for example
> the plugins in the LADSPA SDK).
>
> > > >>> 4.27. Well Known Controls
> > > I would add also trigger control to the standard controls: a generic
> > > trigger. For example it may have values -1 for stop, 0 for hold, 1 for
> > > start.
> >
> > To trigger what?
>
> Anything. For example the start and stop of a sequence in a sequencer
> plugin, the start and stop of a sample in a sampler plugin, etc....
> Having a general purpose standardized trigger allows easier and more
> flexible interconnection between modules (i.e. plugins).
>
>
>
> ----------------------------------------------------------------------
> 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
>
----------------------------------------------------------------------
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:
