> (g). Plugins have 2 process calls, Process32() and Process64(). By >default in the GMPI headers, Process64() maps directly to Process32 with >casting back and forth. Plugins who wish to override/supply their own >Process64 routine can do so. Plugins who do not wish to do so can simply >implement Process32, and 64 bit will be transparently handled for both >the host and plugin. before discussing how to support 64 bit data flow between plugins, it first needs to be established that there are worthwile benefits from doing so. the best i've seen so far has been ron's point about building modular synths out of GMPI plugins, which was somewhat countered by steve's observations based on LADSPA. otoh, i sort of like this proposal. the problem with it is that a plugin author will spend a non-trivial amount of time on two different versions of their code, which may be rendered wasted by the decision of most hosts to support only one format. even so, it does have merit as a very agnostic policy. please just don't suggest Process32Interleaved() and its couins :)) ---------------------------------------------------------------------- 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