We can make a module go into a Bypass state via an MP. But we cannot affect the enabled/disabled state. Is there any reason for this (and has this question been asked before? - sorry if it has)?
I assume that in Bypass state, the module is still consuming resources. If not, then never mind this inquiry. However, if a module that consumes a fair amount of resources (like a delay) is still burning cycles when bypassed, isn't this something we'd like to be able to avoid?
MXXX Question - Disable a Module via Multiparameter
-
- KVRAF
- 2702 posts since 9 Jul, 2015 from UK
When its bypassed it doesn't use up CPU, so no worries there. I believe they cannot be 100% disabled as they still need to report a latency value, as if they are enabled they need to be already in sync.
Jason @ Melda Production
-
- KVRAF
- Topic Starter
- 1759 posts since 11 Nov, 2009 from Northern CA
Great to know! Just what I was hoping to hear. Thanks.jmg8 wrote:When its bypassed it doesn't use up CPU, so no worries there. I believe they cannot be 100% disabled as they still need to report a latency value, as if they are enabled they need to be already in sync.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
Just as jmg8 says. Disabling a module also changes the whole effect structures and since we assume this can be automated, this just cannot happen realtime.
