Maybe there’s a way to do this that I have missed, but I’d love there to be a function with which you could save the preset from a plug-in that has failed to load.
I believe Madtracker used to have this function, and although it might sound a bit strange it has several extremely useful proposes, for instance:
Some manufacturers (ie. Waves) for some reason sometimes subtly change the name of their plug-ins. This silly practice causes the load to fail, even though I actually do still have the plug-in. Exporting the fxp, loading the vst with the new name and importing the fxp again would solve the problem. (The name problem could also happen when using a bridge, like me.)
For plug-ins that you used an older version of in an old song, you could try to get the new version to try to open an “old” fxp, say opening a 1.1 preset in version 1.2. It often works.
You could export the patch/preset to a person/machine that does have the plug-in but does not run Renoise.
Archival purposes.
As the settings are saved with the xrni, it should not be too hard to implement, for instance in the normal way you would export an fxp. You could even have the pop-up that tells you that a plug-in failed have an option to save the preset.
I hope this can be added - I would be very grateful
You might be able to get away with trying to rename the plugin inside the Xrni /Xrns (unzip it, edit the xml file, save it and rezip it).
You need to save one new xrni with the new plugin, so that you can at least pick the Plugin ID and name to paste into the old instrument xml data.
Presets will not automatically load into the new plugin if the plugin vendor changed its ID or name because the plugin then has a unique identity of its own.
There might be a reason for it, e.g. the old presets are not compatible.
