On Tue, 1 Apr 2003, Marc Poirier wrote: > Yeah, the graph is all audio / music data. But there's more to deal with > than just the components in the graph (host communication, UIs of any > sort, etc.). Hmmm, I'm not sure I'm following you entirely, though... > I'm thinking to myself, "sure, that's the graph, but if that's all we had > we wouldn't be talking about this," but I'm also feeling like I'm not > quite seeing everything that you're getting at maybe... I guess what I'm getting at is that every music-related change of state in graph objects (music-related meaning things other than the basic connection parameters of sample-rate, pin number, blocksize..., and change-of-state meaning writing to objects rather than merely querying aspects of their state, such as reading parameter values) should be mediated via the graph as far as possible. So, in the control surface example, the control surface initiates a parameter write by sending an event down the graph from its fader, to a midi or other input-port to the plug, which in turn does something with the event and sends a message about its actual changed state on down the graph towards a midi output port, which is in turn connected to the controller. If the control event is a patch change, which will affect a number of parameters, the plug will generate those parameter-change events and pass them on towards the controller. In the case of a morphing plug, it might even generate a series of timestamped events and deliver those to the controller, causing the faders on the control surface to move smoothly... 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