[gmpi] Re: Topic 1: Audience for and users of plugins

  • From: Paul Davis <paul@xxxxxxxxxxxxxxxxxxxxx>
  • To: gmpi@xxxxxxxxxxxxx
  • Date: Fri, 14 Feb 2003 13:07:46 -0500

>What about MIDI/music data editors and wave editors?
>It will be convenient to plug 3rd party piano roll or step sequencer to MIDI
>block of your modern super-sampler.It often nessesary to run wave editor
>plug-in to edit loop points etc.
>Such modularity may reduce time-to-market (especially for multi-platform
>products) and it gives opportunity for end user to work in familiar editors

i think we are discussing the audience for GMPI.

this issue falls under questions of what kinds of plugins to support,
in particular whether to support just the in-process model, or to
support out-of-process model. for those who are not clear on these
terms, the former covers all(?) existing windows/macos plugin APIs,
where code is loaded into the process context/address space of the
host and executed there. the latter covers a design involving
inter-process communication between the host and "plugin" ("client" is
perhaps a better term here).

i would suggest that we delay discussion on that issue and remain
focused on the audience. defining the developer side as "developers of
audio, MIDI and some kinds of video software" is good enough for me.


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: