SlotFX (Hardcoded) Persistence?
-
Currently working on a modular FX setup, everything's working but if I save/reload the session in Ableton it resets which FX are loaded into each slot.
Do I have to store the data in a panel or something to get it to save properly? Or is there a more elegant solution?
-
@iamlamprey You could write your values to a json file. That would persist. Im not sure exactly your setup but im sure that will work.
If anybody else has a better solution im sure they'll chime in.
-
@Chazrox The issue with a json/local file is if the end user has multiple instances of the plugin, it would either overwrite (worst-case) or end up making a bunch of loose json files somewhere
-
@iamlamprey you could add the module to the user preset state so it gets recalled correctly.
-
@Christoph-Hart curios. Does this work for MIDI Player? Im trying to save the state without saving tracks.
@iamlamprey sorry to piggy back your post.
-
@iamlamprey I see. I didnt think about that.
-
@Christoph-Hart said in SlotFX (Hardcoded) Persistence?:
@iamlamprey you could add the module to the user preset state so it gets recalled correctly.
Ah cool, I didn't know about this function, thank you.
@Chazrox said in SlotFX (Hardcoded) Persistence?:
@iamlamprey sorry to piggy back your post.
No problem 🥳
-
@iamlamprey as Christoph says this is precisely how I do it:
Engine.addModuleStateToUserPreset(var moduleId)Once upon a time when I worked on my Modular FX system I overlooked this function, and ended up having to rewrite everything to incorporate it and base my system around it.
-
@HISEnberg said in SlotFX (Hardcoded) Persistence?:
Engine.addModuleStateToUserPreset(var moduleId)Yeh this seems to be working, I still have a dereferenced nullptr on the interface somewhere when I try and delete the plugin that I have to track down but otherwise it's doing the thing
