[ thanks for the requirement number ] >>>> >the reason for the tight coupling between the DSP and GUI side of things is, >lets be honest, that it was easy and perhaps in part because windows doesn't >really allow for any other way. ><<< > >I don't see this approach as being particularly tightly coupled. If a >plugin supports a GUI, you invoke it passing in an abstraction of the visual >container for the GUI. The spec defines what this should be for each >supported platform. in some strict sense, you are right that this doesn't mean "tight coupling". but the truth is that in cases where this approach is used, it generally seems means that the GUI is running in the same address space as the host/plugin. yes, one could be on a different machine, and the GUI is still instantiated by being passed an HWND or whatever it is. but that's not what people are thinking of, i think, when they discuss or design for such a scheme. i think the underlying idea is that the host creates a window, and they draw in it using a predetermined drawing API. anyway, to try to summarize little bit here, since there are several tangled issues: 61.a should the GUI code be able assume that it runs in the same address space as the host/plugin? 61.b can the GMPI API for parameter control fulfill everything that the GUI might want do? 61.c can the GMPI API for parameter control be implemented via a network protocol? 61.d what kind of object is passed to a GUI (assuming ron's model)? what API is it a part of? --p ---------------------------------------------------------------------- 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