It should not require an external script to convert. Banks (ideally) should have a stamp identifying the version which saved them, so the new plugins should be able to recognise old banks and translate them internally. If they are not stamped in any way, there should at least be an "import" option within the instrument.lnikj wrote:From what I can see from rooting around in folders is that presets were previously stored as monolithic banks, whereas they are now stored individually.DrGonzo wrote: Would be interesting to hear why you changes the preset format (if you can talk about it).
All a preset is is a bunch of values, which is why many devs store them as human readable plain text or XML files. In both cases here they are in an encrypted/compressed format.
If it was a straight conversion, one would imagine it is a case of just decompressing, running a conversion script, and recompressing. A few hours work to package up and release a script to do that.
Clearly it is not though, if it will take weeks or months. So, this might indicate some DSP changes in older plugins? Hopefully.
I am also wondering whether that also means that one cannot replace the versions in an existing project. I assume if it does cannot understand the old preset format, it will also not recognize automation data.
