Sorry I am not quite following, and it seems to me you are describing the module backwards (clicking the button to deactivate the module, what you describe as OFF, would mean the module values are NOT applied, when deactivated the button is unlit)
There are 3 context menu options that control how the module acts when it’s state changes, and these 3 options interact with each other, so, I’ll try to describe all the different combinations of use you might need:
-
you have a patch without Bright-Idea
- The Rack settings apply, you can change them from the View menu, the values are saved into the settings.json file, they are not saved in the patch file
- If you load any patch that does not include an active Bright-Idea module, the Rack settings will remain the same
-
you add the Bright-Idea module to the patch
- the module is active by default but the option
Override Rack
is OFF by default, so when you add the module to the patch, the module will set it’s parameters to the Rack settings, then take control of the settings
- you can no longer change the values from the View menu because the module is controlling them, you can change them directly on the module using the knobs, or via CV
- the module parameters and its state (active or deactivated) will be saved in the patch file, so if you load any patch with an active Bright-Idea module, it will immediately change the values
-
you deactivate the module by clicking the Active Toggle
button (or toggle the button with a CV trigger)
- By default, the
Deactivation Defaults
option is ON, this means when you click the button and the module becomes deactivated (the button is unlit), the Rack default settings will be applied. The module will no longer control the settings, if you want to change the settings you can do so via the View menu, you can still change the knobs on the module but this will not affect the values.
- This is also true if you right-click and
bypass
the module, but note that this is independent of the Active Toggle
button, if the module is deactivated when you bypass the module, it will remain deactivated when you un-bypass the module
-
you activate the module by clicking the Active Toggle
button (or toggle the button with a CV trigger)
- By default, the
Override Rack
option is OFF, this means that when you reactivate the module, it will set it’s parameters to the current Rack settings, which will be the default settings if you have not turned OFF the Deactivation Defaults
option, or not modified the values via the View menu while the module was deactivated. So effectively you will see no change.
- If the
Override Rack
option is turned ON, this means that the values of the module parameters will be set as the Rack settings. I think this is the situation you are confused by, if you want the module to save it’s values and apply them when it is reactivated, you need to enable this option.
-
you open the module browser
- The
Module Browser Deactivation
option is ON by default, which means that the module will be deactivated when the module browser is open. However, if you have also turned OFF the Deactivation Defaults
option, when the module is deactivated, the values will not be changed from what the module parameters are at the instant of deactivation (you might be modulating the parameters with CV). So potentially, if the Room Brightness was low, it would remain low in the module browser.
Hopefully you can see from this explanation that the 3 options control how the module works, and what the combination you need is.
It is possible that the behaviour you desire is for the Module Browser Deactivation
option to be independent of the Deactivation Defaults
option, so that when the module browser is open, the Room Brightness is always max.
This would be possible to code, but would add another context menu option, and clearly the usage is already leaning towards the complex side, so let see what the public consensus is before I add that.
Another alternative would be to make the Override Rack
option ON by default, the consequence of which would be that the module would immediately change the Rack settings to default when it is added to any patch, I thought this would be unexpected and not desired by most users.
Or another alternative, I could make the Override Rack
option ON by default, but, make the module deactivated by default when it is added to a patch. But again, this may be confusing to the user, adding a module that doesn’t do anything until you activate it.
Possibly I could also change the dynamic text on the module when it is deactivated, to make that clearer?