mehum wrote:Very nice synth but unfortunately unusable, at least in Reaper, since it won't retain settings on save/load. Seems to be some problem with the instances getting mixed up. Things like duplicating a track will use the last edited instance instead of the instance on the track.
The synth doesn't recall its contents through the DAW project but through the patch files alone. Try if it makes a difference when you have the patches saved, using a unique filename for every instance.
It reminds me of the Tunefish round, juggling those patch text files
Anyway, the main thing to remember is, the patches are not saved with the project. I tested this in Live, and when doing a project save, the plugin instances automatically just save over the patches they have loaded in them, writing over the corresponding named patches in the patch directory. So if you have duplicate patch names (everything saying "init", for example), it will mess up. If all patches are individually named, and preferrably already saved in their current state to be sure
, the project is always correctly recalled.
Note that if you change a patch in any one project and save that project without changing the patch name, you will be altering the patch for all projects
using that same patch, eh. Similarly, if you duplicate a track or plugin instance without saving the patch first, the duplicate will most probably load the latest state of the patch that is actually in the patch file of that name
Always save a patch using a unique name before altering something for a different sound / different project. And after altering it, save that altered version using a unique name for the alteration.
It's a throwback to an earlier time for sure
, but that's how it sometimes is with experimental/outlier software.