>and other similar programs and make them run as a plugin. there is no >reason to put the complexity of such programs into each and every GMPI >host. Then we also need a separate flow graph standard, so that my reverb written as a set of both the GMPI plugins and the flow graph descriptions would work in all such flow engine plugins. The machine hierarchy becomes complex: master engine --> GMPI plugin with flow engine --> GMPI plugins What if my reverb wants to use third party late reverberation unit? I should write a simple GMPI host inside my reverb which then either runs a monolithic late reverberator or runs a GMPI plugin with a flow engine which finally runs a graph of a late reverberator. It all would be simpler if the flow graph description would be part of the GMPI. The problem that then each host should have a flow engine is not any bigger than that then each user should have a GMPI flow engine plugin if they want to run my GMPI reverb. Besides, the flow engine need not be a part of the host, it can be a GMPI plugin as you said. But, if the flow graph description is a part of GMPI, the GMPI host could run only one GMPI plugin with a flow engine, not several if users runs multiple copies of my reverb. Juhana ---------------------------------------------------------------------- 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