Hi, > Lets repeat how I would write my reverb: > -I would write a multitap plugin; called as multitap() > -I would write a late reverberator; called as laterev() > -I would write a bandsplit filter; called as bandsplit() I think we've already discussed this, but here's my reguritaion of my personal opinion... I suspect effect-design is better done in a specialist program like Reaktor, Tasman or SynthEdit. IMHO The target of the GIMPI plugin system is the user who thinks "This song needs a reverb", click, click done. NOT the person who thinks "I want to design a new type of reverb, where's my comb filter?". On the surface these two things are similar ( a graph of audio processing objects ). But when you get down to the details, the requirements diverge sharply. An interface like VSTi or DXi needs to be simple to implement and efficient. I predict GIMPI will use block-based processing? Yet, software like Reaktor, Tasman, or SyncC modular where you can design an individual filter, NEED single-sample feedback to create recursive structures (filters, delays, and physical models). In order to remain efficient, you need to support single-sample processing, which is TOTALLY different to implement. It is also crucial to support 'silent' samples and CPU-saving techniques at the plugin level. And don't mention polyphonic support... The user draws the graph once, but the host has to duplicate a sub-graph for each voice of polyphony. Not the entire graph, the host performs complicated analysis to determine which objects are polyphonic, and which monophonic. As the writer of SynthEdit, I've written both types of code. I honestly believe that if GIMPI trys to be too general, everything to everyone. It will be an over-complicated mess. GIMPI needs to stay focused and tight. There's plenty of software for low-level design already, and it all supports being imbedded in an existing hi-level plugin standard like VST. Best Regards, Jeff www.synthedit.com ---------------------------------------------------------------------- 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