> are fundamentally two related plug-ins. If any Digidesign engineers are > reading this, perhaps you could explain how your SDK handles this kind of > thing.. it's rather more elegant than other existing APIs as far as > enumeration goes, but I don't want to say more because of NDA :-( I've never read any digi docs or anything, but this was my thought on enumeration. Each plugin file (.dll, .so, whatever) can hold multiple plugins. You get the list of plugins by calling some exported function within that plugin file (like LADSPA). However, it doesn't return just static descriptors. That API would actually enumerate and return descriptors with arguments. Simple example: A GMPI native plugin might just return it's descriptor, with no arguments. More fun example: A VST wrapper might have an argument 'VSTPlugin'. When it is queried, it would look at your VSTPlugin path, and enumerate all the VST plugins. It can then return it's descriptor with the 'VSTPlugin' argument set to the path of each valid VST. The host would see it as a number of GMPI plugins. In reality, they are all the same plugin, with a different argument. The same can be true of datatype. They are joined by the fact that they have the same base descriptor, but differ by their arguments. If you prefer: s/datatype/GMPI version/ or whatever. And this is WAYY off topic. ---------------------------------------------------------------------- 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