Well, I did some testing and bypassing an effect (outside of this plugin) does not seem to cause any problems. However, I still think having the bypass option within this plugin is necessary because if you are using effects (or other plugins) that use a lot of resources, such that you do not have enough resouces for 7 effects, then you need a way to make this plugin work with less effects (i.e. if one of the send/return's is not connected to anything, then it breaks the chain, and thus you would get no sound at all without a bypass option (basically to tell it to skip that effect slot)). Here is an example screenshot: http://tinypic.com/aze9mq.gif The outputs of the effects look as though they are not connected to anything, but that is just because they are going straight back to the return inputs of this plugin. Notice the resource usage in the pic. With that setup I am almost max'd out on resources. BTW: The name is just temporary, we can think of a better name later. Also don't forget that in addition to the 7 effect slots, you can also connect effects to the in and out connections, thus allowing more effects in the chain (you just will not be able to change the order of those effects, but that is good for effects that are typipcally always first or last in the chain... and obviously you can chain mutiple effects to any send/return as well). I think another option that would be good, is being able to rename the effects in the effect list, such that you can change the names to match the effects that you have connected (although they will not be able to be saved in a preset list, they would be able to be saved along with a DSP config, etc). Anyway, I am still working on the bypasses. It is a little tricky, whenever I think I have it working, some combination of changing paramters doesn't work right, so I then have to go and redo it, almost from scratch again, and then test various scenarios again, etc.