Factory Presets vs. User Presets
-
HI guys, searched along the forum but can't find a way to do editable and not-editable banks on the same preset system.
In this example, I wish Factory Bank to not be editable. And User bank to be editable. Any idea?
-
@hisefilo It has been requested. Christoph mentioned he's be able to set the read-only flag for the presets you create before exporting as a plugin, but I don't think this has been implemented yet.
-
No it hasn't yet. Also there is a strict "no encryption" policy on user presets because I want them to be human-editable for people who know how an XML file works, so there would be no "real" overwrite protection since people might just change that flag manually.
But if you just prevent the users from accidently overriding the factory content, it should be fine. I'll add that one to my list.
-
@Christoph-Hart Yes! a basic flag for prevent editing (not encrypted, just to avoid users to override the initial patches on the UI).
-
Loop hole
- Load your plugin in a DAW
- Load a factory (read only) preset
- Save the DAW session and close the DAW
- Reopen the DAW
- Open the instances of your plugin that you previously added
- Go to the preset browser
- Click save and your factory preset will be saved over
