[gmpi] Re: Requirements
- From: "Angus F. Hewlett" <amulet@xxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Sat, 15 Nov 2003 09:43:25 -0500 (EST)
Those plugins are category (b) below.
=======================================================
Angus F. Hewlett, Technical Director
FXpansion Audio UK Ltd - http://www.fxpansion.com
=======================================================
On Sat, 15 Nov 2003, Michael Gogins wrote:
> Have we considered that GMPI must do something for those wrapped plugins
> that do GUIs their own way? Are such GUIs totally invisible to the GMPI
> spec?
>
> ============================================
> 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: "Angus F. Hewlett" <amulet@xxxxxxxxxxxxx>
> To: <gmpi@xxxxxxxxxxxxx>
> Sent: Saturday, November 15, 2003 9:29 AM
> Subject: [gmpi] Re: Requirements
>
>
> > On Fri, 14 Nov 2003, Tim Hockin wrote:
> >
> > > I agree with this completely, and it is already required. I'll add a
> new
> > > line to clarify:
> > >
> > > GUIs are not part of a DSP plugin with private access to the DSP
> > > internals. All communication between UI and plugin is via
> standard
> > > control signals. In effect, the GUI is a separate plugin.
> >
> > I would like to modify this to the following:-
> >
> > In an optimal GMPI plugin implementation, GUIs are not part of a
> > DSP plugin with private access to the DSP
> > internals. All communication between UI and plugin is via standard
> > control signals. In effect, the GUI is a separate plugin.
> >
> > However, for legacy reasons, this is not possible for all
> > plug-ins. Therefore, pre-instantiation, a plugin should be able to
> > indicate whether:-
> >
> > - a. it has no GUI and provides only a description of its
> > parameters
> > - b. it has an integrated GUI
> > - c. it has a port/interface to which an external GUI object can
> > connect, and information which the host can use to locate,
> > instantiate and connect said GUI object.
> >
> > The host may choose to reject category (b) plug-ins at its
> > discretion.
> >
> >
> >
> > > > But, of course, for backward compatiblilty with VST, we have to also
> support
> > > > the VST-way.
> >
> > > What exactly IS the VST way? Is it "here is a window - draw on it" ?
> >
> > Yes, more or less.
> >
> > > I agree with your description. But how you draw a GUI is the hard part.
> > > The "here's a window - draw on it" is fundamentally not cross platform.
> >
> > True. But developers that choose to make chromed UIs should frankly not be
> > too worried.
> >
> > > It's not going to be easy, though. Is this how libvstgui works, more or
> > > less? We'd require it to be host-provided instead of a generic dll,
> but...
> >
> > Yes... libvstgui is a very basic crossplatform graphics library. Note that
> > it's linked in to the plugin binary... what you describe is more like a
> > host-side graphics toolkit.
> >
> > Personally, I think if we provide a GOOD generic-parameter info mechanism
> > (i.e. richer than VST's), we don't have to worry too much about the fact
> > that developers that want to make chromed UIs will have to write platform
> > specific code.
> >
> > Regards,
> > Angus.
> >
> >
> > ----------------------------------------------------------------------
> > 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
>
>
>
----------------------------------------------------------------------
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:
