Packages script to remove ~/Library/Application Support/ data
When you launch it it checks if the AppData folder exists and only if it doesn't exist it extracts the presets.
I'm wondering what everyone is doing with their installers when they release new presets? If a plugin is already installed, it sees the previous appdata folder at launch and doesn't extract new presets.
I assume you can make a script to remove this folder during install. Anyone have the details?
@dustbro You don't want to remove that folder, you'd be deleting any changes the user had made. You could provide the additional presets separately and allow the user to install them through the drop down menu in the preset browser. Or perhaps your installer could add the new presets to that folder, and maybe it could rename existing presets so not to remove the user's changes. Or it could just ask the user if they are happy to overwrite existing presets with the same name.
@d-healey The plug will only contain factory presets. The user wont have the ability to save their own. Is there anything else in that folder that would be jeopardized?
@dustbro Anything they've changed in the plugin's settings, if they have access to them.
Just reviving this old discussion as I'm trying to think of how user presets might be updated when rolling out updates to a plugin.
Version 1.0 of a plugin has a total of 10 presets
Version 2.0 of a plugin has a total of 19 presets (9 of which are new)
What's the best way to add the 9 new presets to the plugins 'Preset Folder'?
If doing this on installation is still the only way, what installers are people using to achieve this?
I've found that InstallForge is limited as it doesn't allow the creation of an installation exe that can install files to mulitple folder destinations.
This is a requirement as the installer will need to:
A. Install plugin vst/component to plugin directory
B. Install the new presets to the presets folder
I'm thinking about how this might done on Windows and Mac.