>We also need to address:- will we support plugs operating in a >pseudo-static (visualiser / editor) mode of operation, "offline" hybrids >(including multipass and non-1:1 algorithms), or does GMPI only seek to >address realtime 1:1 or "pseudo-1:1" streaming at this stage? > >My suggestion would be to specify only realtime streaming for now as >that's the most urgent need, but to bear in mind the possibility of >visualisers and editors using the same data representation scheme and >broad API conventions in future. as i just mentioned, i don't think we care what the plugin does. it can do visualization, make candy based on the incoming audio signal, control a 3D polystyrene robot sculptor or whatever. from the perspective of the host, its a chunk of code that the host calls at the appropriate times, has zero or more inputs and zero or more outputs and obeys general RT scheduling: cycles spent in plugin = (A * nframes) + B where A and B are constants. ---------------------------------------------------------------------- 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