Disable and Bypass

[0x51ec04bf7baf7]

Hello everyone.

Is there a utility that allows the disabling of a module, but still allows the audio to run through it like a bypass.

I am aware of bypass modules. Would like to actually disable and bypass.

I am aware of aux sends. This need extends beyond effects.

Thanks in advance for your time

[almostEric (Eric)]

not sure how that would even work, but maybe @stoermelder has some ideas

[0x51ec04bf7baf7]

Yeah I feel like I’ve been bugging him for weeks.

Most of my issues tend to come down to stoermelder utilities.

Sorry Ben.

[almostEric (Eric)]

what you are proposing sounds simple, but runs into the reality of how modules work. What does bypass even mean? Internally, every port you see is an in or out - even CV ports, there is nothing that signifies that an input is special other than how the module is written to do something with those inputs and outputs

[0x51ec04bf7baf7]

Yes your right. I understand.

[stoermelder (Ben)]

What Eric said, plus „bypass routing“ will come in Rack v2.

Rack development blog

Various minor features for Rack 2.0: Red clip lights on VCV Audio when signal goes beyond ±10V. [2019-11-25-162904_414x458_scrot] Add module bypass routing API, which replaces module disabling, so developers can specify direct routes from inputs to outputs when users “bypass” the module. Add infinity and NaN protection to cables, so they won’t propagate non-finite values from badly behaving modules. (Performance not fully tested, could be removed.) Duplicating modules also duplicates…

[0x51ec04bf7baf7]

Thanks for this. So even if an active feature, all current modules do not support?

[Squinky]

Only the module itself can know what it would even mean to “bypass” it.

[almostEric (Eric)]

Like it says in the notes “Developers can specify…” that means we need to now, well, specify Unfortunately, we can’t do that until the 2.0 API is released.