What does "Bypass" mean?
Posted: Sun May 31, 2020 5:17 pm
I'm curious about how CA and the dev community feel about this.
When a module is in the newly established 'bypassed' mode what should the module do? It's pretty obvious that an oscillator should stop oscillating and a noise source should shut up, but what about a filter or other processing type module? In the guitar pedal sense, "bypassed" means it passes the signal through unaltered. If this is not the intention, and processing modules should not pass the dry signal to all outputs, then I would suggest that the term "bypass" is a misnomer and I would suggest changing the term to "disabled" instead. Whadya think?
When a module is in the newly established 'bypassed' mode what should the module do? It's pretty obvious that an oscillator should stop oscillating and a noise source should shut up, but what about a filter or other processing type module? In the guitar pedal sense, "bypassed" means it passes the signal through unaltered. If this is not the intention, and processing modules should not pass the dry signal to all outputs, then I would suggest that the term "bypass" is a misnomer and I would suggest changing the term to "disabled" instead. Whadya think?
Open Module Designer, check ”Can be bypassed” in the module properties, and then look for the ProcessBypassedSample() function in the code, it’s all explained there in the commented text.