This is technical...
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
If I Mute a Track Line I get for example CPU 78% while if I mute the Target Rack (on the mixer) of the same Track Line I get a CPU reading of 58%.
I am muting the same Plugin synth!
I know there is a reason but I do not know Mulab that deep yet.
Any idea?
I am muting the same Plugin synth!
I know there is a reason but I do not know Mulab that deep yet.
Any idea?
ABEFLGMOPPRRST 
- KVRian
- 1233 posts since 29 Dec, 2008 from Lithuania
Maybe it's like this:
When you mute a line, you mute just the MIDI line but the plugin (VSTi ?) it's still running and taking resources and Mu.Lab it's still processing the channel.
When you mute the mixer stripe you mute the actual instrument, so it's probably stopping the plugin and sound processing of the mixer stripe.
I don't really know, but the seems logical to me...
When you mute a line, you mute just the MIDI line but the plugin (VSTi ?) it's still running and taking resources and Mu.Lab it's still processing the channel.
When you mute the mixer stripe you mute the actual instrument, so it's probably stopping the plugin and sound processing of the mixer stripe.
I don't really know, but the seems logical to me...
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
What sorohanro writes is true.liquidsound wrote:If I Mute a Track Line I get for example CPU 78% while if I mute the Target Rack (on the mixer) of the same Track Line I get a CPU reading of 58%.
I am muting the same Plugin synth!
I know there is a reason but I do not know Mulab that deep yet.
Any idea?
Note that MU.LAB automatically stops processing a plugin when it doesn't have any input/output during 3 secs (default, but editable via plugin context menu "Setup Smart Bypass"), but that's more relevant for effects than for synths.
Also note that when you mute a track you're muting the events to 1 single target plugin, while when muting a rack, then all post-fader plugins are affected.
-
- KVRAF
- Topic Starter
- 5573 posts since 30 May, 2006 from Hollow Earth
It is logical!
AND now I know what is the Smart Bypass for.
I really need to sit down and get to know this Amazing.Lab better.
You know I am waiting for M3 to dump all my stuff and time in it.
That time is getting closer and closer.
I really need to sit down and get to know this Amazing.Lab better.
You know I am waiting for M3 to dump all my stuff and time in it.
That time is getting closer and closer.
ABEFLGMOPPRRST 
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 2973 posts since 10 Sep, 2003 from Karlskoga, Stockholm, Sweden
About smart bypass..
If i make a superFXmux with
Audio input going to several mixer strips (for gain control) which in turn are sent to various fx's. If i mute all mixer strips but one so that there's only audio going to one of the plugins, will the others not affect the cpu? A little or at all?
By the way, this function is not mentioned in the manual (i couldn't find it when searching for it at least)
If i make a superFXmux with
Audio input going to several mixer strips (for gain control) which in turn are sent to various fx's. If i mute all mixer strips but one so that there's only audio going to one of the plugins, will the others not affect the cpu? A little or at all?
By the way, this function is not mentioned in the manual (i couldn't find it when searching for it at least)
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
It depends what's after the mixer strips, but chance is high you'll indeed benefit from auto bypassing.Crackbaby wrote:If i make a superFXmux with
Audio input going to several mixer strips (for gain control) which in turn are sent to various fx's. If i mute all mixer strips but one so that there's only audio going to one of the plugins, will the others not affect the cpu? A little or at all?
