Recommended Suspend Setting for Bitwig?

[Held]

In Bitwig, there's the option to automatically suspend plugins when they're not active. Given that Melda plugins have their own "Sleep on Silence" functionality, I'm wondering what the best choice would be.

Should I
1) Disable Bitwigs suspension and let Melda plugins decide when to sleep?
2) Disable Melda's sleep on silence and let Bitwig handle the suspension? Do Melda plugins send the necessary background notifications?
3) Or leave both active?

For reference, here's the relevant section from the Bitwig manual.

The Suspend option sets how Bitwig Studio determines when the plug-in is not needed and can be safely suspended for the time being. (When this occurs, the plug-in's "power" button icon turns into a moon, indicating that it is resting and saving CPU cycles.) There are three options for this setting:
› Never - The plug-in remains active perpetually.
› When silent - Bitwig Studio determines when the plug-in isn't needed, based on whether audio is going into and out of the plug-in.
› Trust plug-in (default) - Bitwig Studio uses background notifications from the plug-in to determine when it is not active.

[WasteLand]

In Bitwig, there's the option to automatically suspend plugins when they're not active. Given that Melda plugins have their own "Sleep on Silence" functionality, I'm wondering what the best choice would be.

Should I
1) Disable Bitwigs suspension and let Melda plugins decide when to sleep?
2) Disable Melda's sleep on silence and let Bitwig handle the suspension? Do Melda plugins send the necessary background notifications?
3) Or leave both active?

For reference, here's the relevant section from the Bitwig manual.

The Suspend option sets how Bitwig Studio determines when the plug-in is not needed and can be safely suspended for the time being. (When this occurs, the plug-in's "power" button icon turns into a moon, indicating that it is resting and saving CPU cycles.) There are three options for this setting:
› Never - The plug-in remains active perpetually.
› When silent - Bitwig Studio determines when the plug-in isn't needed, based on whether audio is going into and out of the plug-in.
› Trust plug-in (default) - Bitwig Studio uses background notifications from the plug-in to determine when it is not active.

i can't look under the hood... but the sleep function, i do not know if it is a vst3 thingy, or a melda thingy...
if it is vst3, than trust plugin.
if it is melda, never.

i think it can't do any harm to set both to active, trust plugin. i think.

i don't know the vst3 SDK, but suspend is indeed set by the host, after a notification of a plugin. not by the plugin itself, as in melda's case.

so, i assume; never. because melda puts itself to suspend/sleep.

EDIT: i think i have answered my own question too, melda decides to 'suspend', not the host.

so you have 2 options, set sleep off, and let the host decide.
or turn sleep on, and let the host not decide... (and i believe if trust plugin is used, it will do no harm, in other DAW's, you don't have these options, or only suspend on/off (in cubase for instance)).

i don't know why melda has decided to implement it this way, perhaps because suspend, via host, is not always perfect. is my guess.. or can lead to increased load, even... in cubase... the makers of the SDK... but well, we can't blame only steinberg, also the developers... or blame...

[MeldaProduction]

I'd disable it in Bitwig. Basically, the DAW cannot really know if the plugin is able to generate something on its own. So if the plugin dev decides it is possible, he has to switch the DAW's disabling capability off permanently even if there's no need for that. But Melda plugins are actually detecting whether this may happen and react accordingly, so the savings will be higher and room for error is smaller.

[Held]

I'm not sure I understand your explanation, but I'm going to disable it in Bitwig. Thanks.