[gmpi] Re: GUI and DSP separation
- From: Marc Poirier <marc@xxxxxxxxxxxxxxxxxxx>
- To: gmpi@xxxxxxxxxxxxx
- Date: Tue, 11 Feb 2003 16:28:47 +0100 (CET)
> > This actually sounds exactly like how it's done with AU. The GUI and the
> > DSP are separate executable code, separate DLLs, separate plugins, etc.
> > In Mac OS world, they are called "components" (handled by the Component
> > Manager). The DSP component gives the host, if requested, a list of zero
> > or more IDs for GUI components that are recommended, and then the host can
> > instantiate any GUI components, passing along a Component Manager
> > reference to the DSP component, and then the Component Manager resolves
> > any property setting and getting that the GUI component does. The DSP
>
> Can you explain why its done this way? It also seems useful for the UI to
> express what DSP components it can control. For example, in LADSPA we have
> UIs that can control any (or a subset of) plugins. Possibly both are
> desirable.
Yeah, I can see where you're coming from, sounds like that could be
useful. I guess with AU, there's a sort of exception which is that there
is a generic GUI component (comes with the OS) which you can assume will
work with any DSP component. But that's as far as it goes, so far, in
that direction...
Marc
----------------------------------------------------------------------
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:
