Snapshots and partial plugin saves

dhjdhjdhj's icon

Based on a suggestion from Andrew Pask some time ago, I'm trying to redesign a large Max based system so that instead of loading VST plugins on demand, I'm going to load them all in one go and just change "patch settings".

So that means I will have about 25 [vst~] objects instantiated in a "global" patcher. For each song that I want to play, I will load a patcher that (among other things) will just reference the 4 or 5 [vst~] objects that are needed for the particular song.

The parameters for those vst objects are saved in fxp files.

Andrew also suggested that I look at snapshots as a more convenient approach for storing VST parameters. From what I've read however, it looks like a snapshot will save the state of all the loaded VST plugins which would have some significant performance issues for me in both time and RAM usage (e.g, I don't want a ton of samples reloaded into a plugin that's not actually being used in a particular song)

Is there (or will there be) a way to designate on a per-patcher level, which [VST~] parameters will actually be saved?

dhjdhjdhj's icon

OK --- from a quick test it seems that the snapshot process only works for patchers that actually contain VST objects.

So that approach is unfortunately no good to me ---