Dynamic reassignment of effect slots

[Oli Ullmann]

@Christoph-Hart
Great, thanks for the info. :-)

[Orvillain]

Does any kind soul have a snippet that demonstrates how to use Engine.addModuleStateToUserPreset???

[d.healey]

@Orvillain

// In onInit
Engine.addModuleStateToUserPreset("InsertNameOfModule");

[Orvillain]

@d-healey So Do I have it right then.... call that function for every module that I want to save to a preset.... save to a preset in the browser..... then when I load it, those things will be recalled both in the module tree and the connected UI parameters, regardless of if saveInPreset is enabled????

[d.healey]

@Orvillain It will be recalled to the module tree, not sure about the UI parameters but Christoph seems to indicate that with this dynamic effect slot system that it will be.

[Oli Ullmann]

@Christoph-Hart
When I try to follow your advice with a HardcodedMasterFX, I get the following error message:
Can't store modules with child modules

Is it not possible to use Engine.addModuleStateToUserPreset with a HardcodedMasterFX?

[Christoph Hart]

those things will be recalled both in the module tree and the connected UI parameters, regardless of if saveInPreset is enabled????

It will be recalled to the module tree, not sure about the UI parameters but Christoph seems to indicate that with this dynamic effect slot system that it will be.

No UI parameters are not part of the module that is restored with its state so they won't update automatically. But you can call this method after loading a user preset to ensure that all connected sliders are synced to their internal values:

https://docs.hise.dev/scripting/scripting-api/userpresethandler/index.html#updateconnectedcomponentsfrommodulestate

Is it not possible to use Engine.addModuleStateToUserPreset with a HardcodedMasterFX?

Do you have any modulation slots enabled? If yes then this is preventing you from restoring the hardcoded FX because currently you can only restore modules that have no child modules with this function. But I might have to change this to allow it for hardcoded modules as this would be very limiting.

[Oli Ullmann]

@Christoph-Hart
Ah, okay, that's where the problem lies...
Yes, I have enabled modulation slots.

[Christoph Hart]

@Oli-Ullmann Alright this is fixed now - you can call this on modules with child elements now but the child elements will not be modified at all - the rule that rebuilding child elements is dangerous still stands, but this is a valid use case to restore a module without its modulation slots (which are restored by the script modulation matrix anyways).

[Oli Ullmann]

@Christoph-Hart
That's great, thanks! I'll try it out and give feedback if I encounter any problems. Thanks very much! :-)

[DanH]

@Christoph-Hart said in Dynamic reassignment of effect slots:

https://docs.hise.dev/scripting/scripting-api/userpresethandler/index.html#updateconnectedcomponentsfrommodulestate

What if the controls are not connected by Parameter ID etc but via scripting instead (as lots of mine are as they do more than one job...)

[HISEnberg]

@Christoph-Hart said in Dynamic reassignment of effect slots:

Just a small heads up that we have this now:

https://docs.hise.dev/tutorials/ui/index.html#draggable-fx-chain

I noticed one small anomaly about this example. If you add more effects to the example script, you need to set the panel's saveInPreset to false temporarily to update the JSON effect list, then reenable it again!

[Orvillain]

@Christoph-Hart said in Dynamic reassignment of effect slots:

Just a small heads up that we have this now:

https://docs.hise.dev/tutorials/ui/index.html#draggable-fx-chain

As it turns out, that was reasonably easy to add.

[HISEnberg]

@Orvillain Agreed so far I am really happy about this! Very simple to use. Need to test it out in some real world examples still!