Any way to *instantly* bypass / un-bypass a VST plugin?

[beammy]

I've just started having a play around with Usine, and I love how powerful and flexible it is.

One problem that I'm encountering, though, is that when you switch a VST plugin between "bypassed" and "not bypassed", say by patching a switch into its "bypass" input, there's about a quarter-second delay before a change to this takes effect. Is there any way around this?

I really do need to deactivate the VST itself, to save CPU usage - simply routing the audio past the VST wouldn't be a workable solution.

Thanks!

[hesspet]

Build you "own" bypass.

Route the signal around your VST.

The patch of a VST created by Usine



and here's one possible solution:



There are many other ways to do so. (eg. put a fader in front of the vst and set the fader only 0 & 100%)

This solution is fast. Disadvantage: the vst is not stopped and sucks CPU performance during the bypass time.

[woodslanding]

In the example above, you can wire 'my bypass' to the bypass of the vst and get the cpu savings and the bypass all with one button.

For me, I put the vst in a subpatch and use a patch on/off module instead of bypass. I think some vsts still use cpu when bypassed (not sure....)

-e

[hesspet]

Yes, it depends on the VST.
There is no rule!

[beammy]

Thanks for the replies! It turns out that most VSTs actually do bypass virtually instantly - the one I was testing just had a slight delay. Silly - I should have tested more.