Just some extra requirement about 2 or 3 things : The Host will take in charge (GUI and processing if possible): - The A/B setting (or more A,B,C,D...) of the effect (copy to A etc..) (method defined by GMPI) the goal is to avoid to the plug-in to have its own A/B, compare, reset, copy to A stuff on its own GUI and so on. it's boring for the plug-in maker, and because it's never the same on every plug-in, it's also boring for the user . - MUTE , BYPASS, ON/OFF Mute will send an order to the plug-in to pass in mute mode (ouput = 0). bypass send an order to the plug-in to make a bypass (without zypper noise : processing done by the plug-in) on/off : the host disconnect effect from the chain , without destroying it (it allows to save DSP power without boring the user). - The preset/bank management in a portable file per plug-in (defined by GMPI) the goal is to allow the user to port preset or bank of preset from a host to an other one. This not forbid to the plug-in maker to make his own preset/bank management if needed, but it is very handy Vincent Burel ---------------------------------------------------------------------- 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