@Christoph-Hart
I tried it out a little today, and it's not that the modulation is deleted when a DAW project is loaded, but rather that the modulation is reset to the state with which the plug-in was exported.
So:
If the plug-in was compiled with modulation of a parameter, it will also be loaded with modulation when the DAW project is reloaded. It doesn't matter if the actual user preset was saved without modulation. And vice versa.
My ideas for a workaround:
I create a panel in whose value I store the modulation matrix data (ScriptModulationMatrix.toBase64()). The panel is saveInPreset.
Saving takes place in ScriptModulationMatrix.setConnectionCallback.
I create a load callback (ScriptPanel.setLoadingCallback) for the panel. When loading is complete, I load the data stored in the panel's value into the modulation matrix (ScriptModulationMatrix.fromBase64(String b64)). I hope this does not create an infinite loop. I could also try UserPresetHandler.setPostCallback, but I don't know if this will also be executed when the plug-in is loaded with the DAW project without a user preset being loaded.
I'll let you know if the workaround works.
