Use MUX VST to optimize CPU usage in your host

[MuTools]

Using MuLab's Auto Bypass function (fka Smart Bypass), you can avoid wasting precious CPU cycles by temporarily bypassing VST plugins that are only processing silence. As soon as the VST plugin receives input again, the auto bypass is switched off and the plugin processes the input, so nothing lost, only CPU gain This works for both effects and synths!

The Auto Bypass can be setup via the VST plugin's context menu. By default it's set to "Off", but by setting the "Auto Bypass Threshold" to eg 500 ms then the auto bypass will be switched on as soon as the plugin's output is silent for 500 ms and the plugin does not receive any new input. Of course it depends from plugin to plugin, and even from patch to patch what threshold value is best. Just as an example: A filter plugin may be ok with a threshold of 10 ms, but a delay plugin will need a threshold that is at least as long as the delay time.

When the Auto Bypass function is enabled and it is effectively switched on (thus bypassing silence) the processing LED for that VST plugin is dimmed. That way you can clearly see the Auto Bypass function in action.

Theoretically this Auto Bypass function should also already have worked fine in MUX Modular VST, but due to a missing code optimization it was not yet working as intended in previous MUX VST versions. Now with the new M6.5.43 the Auto Bypass also works fine in MUX Modular VST and so it can be used to spare CPU if your host does not have such function. To do so wrap CPU-heavy VST plugins in MUX VST and set their Auto Bypass threshold time to a good value. Check it out!

You can download the MUX VST 6.5.43 patch from http://www.mutools.com/mux/app-patch/Read%20Me.html

[runaudio]

does mutools already have this function with mux inside already

[MuTools]

Yes.
The relevant doc page is here: http://www.mutools.com/info/docs/mux/us ... ugins.html

[focusrite]

Brilliant!

Just need auto pdc to be implemented and I will be able to get rid of other plugins and just use mux.

[focusrite]

Just got round to trying this today. Works with some vst, not others it seems, even when not connected to any audio sources. Most vst emit zero noise so is this a bug?

If I manually disable / re-enable it works, as the on light goes dim and the affected plugin re-activates on start

[MuTools]

If a VST always emits an ultralow noise so to avoid denormalization, and that noise is above -379 dB then indeed the auto bypass feature cannot be used for such VST as it produces audio above the smart bypass threshold level for detecting audio.

[pljones]

Would picking a cut off just above 24 bit floating point dB minimum (about -145dB) be a better one? I don't know what the issues are, of course, as to how that might affect other processing.

If I mute a rack, does the auto-bypass prevent the entire rack getting processed (because of silence on its audio out)?

[MuTools]

Would picking a cut off just above 24 bit floating point dB minimum (about -145dB) be a better one?

I also searched for a way to raise that threshold but taking performance into account didn't find it yet. I'll keep it as is for now so to keep main focus on the M7 plan.

If I mute a rack, does the auto-bypass prevent the entire rack getting processed (because of silence on its audio out)?

No not yet in M6. But i want to work on that.

[focusrite]

Thanks for clarification

There is a workaround if your daw supports it, is to automate the master bypass using a tack envelope during periods when the track is silent. That way you can stuff mux with vsts and bypass the lot with just 1 track envelope.

[cloudspell]

Click on the VSTi you want to auto bypass for example NI MASSIVE launch the plugin and at the middle top there's a big sprocket icon that tells it is the option button look for "Setup auto bypass" set the number to 500

[AC222]

Thank you!!!! Huge innovation and exactly what I was hoping for...