Questions on the "Patch Settings" module

[Vincent]

Hi,
I'm wondering about the "enabled" inlet of this module.
It corresponds to the enable switch in the toolbar header and it's fine to have access to it. But what is the real difference between a non enabled patch and a patch with a "patch On/Off" module set to off (specially regarding CPU load and threads)?
If there is no difference except the greyed interface of the patch, could the "patch On/Off" module also turn the interface to greyed when it's Off?
If there is a difference, could this "patch On/Off" function be also founded in the "Patch Settings" module, since to be On or Off is some kind of setting ?
Thanks for your answers!
Vincent

[La Tenaille]

The patches are supposed not to be calculated when disabled, but I'm too interested in a precise staff answer

[Vincent]

When you connect a switch to the enabled inlet, you can turn this 'off' and disable the patch. And when it's off, you cannot turn it 'on' anymore (because the patch is disbled!). The module Patch On/Off works differently.
It's confusing...

[La Tenaille]

You're right. I've never used modules to disable a patch. I only use the enabled pin of subpatches.

[Vincent]

Yes, it is the simplest way.
But sometimes it's necessary to do some stuffs in the subpatch just before disable it (like mute audio to prevent from looping the last audio block). That's the reason why I also use this module Patch on/off connected to an 'on' inlet or to a switch with two links: one direct and one passing through a 'wait one bloc':

Code: Select all

Switch_________________Patch On/Off
      _____Wait1_____/

sometimes this WaitOneBlock module is replaced by an enveloppe tracker that falls to 0 when the module has finished with delays or reverb.
Anyway, some precise answer will be welcome!