Bypassing a plugin in a properly implemented plugin eliminates audio processing by that plugin thereby reducing the CPU usage by whatever amount was used by audio processing of that plugin.
Not sure what other resources you think would be impacted.
1 Like
Great, didn’t know if RAM is cleared of samples at that point but CPU is important as I am hoping to keep Latency at a minimum. Wife wouldn’t appreciate wanting to replace my Surface Pro 4. 
Follow-up to this: here is a pick of my values which seems to indeed release the bypass almost immediately when raising the fader. However, it reacts strange as sound doesn’t start until the fader reaches higher than -10db. It works fine when used to just with volume but when tied to the Bypass parameter, this is what happens. I’ve tried different combinations to no avail. Any thoughts?
Think about that — if RAM was cleared of sampled and you unbypassed, you would have to WAIT for samples to be reloaded. You don’t want that under normal circumstances
2 Likes