When are changes saved to plugin pseudo-presets?

Hi Guys,

Just to clarify some things here. Firstly there seems to be confusion about the terminology.

A “Pseudo Preset” is a special kind of preset implemented by Cantabile when the plugin in question doesn’t support more than one preset itself. In this case Cantabile fakes the presets list by managing a set of saved plugin states externally to the plugin. Mostly this is completely transparent and as best I can tell in unrelated to this discussion in that the same applies for Presets as does Pseudo Presets

As for when presets save, I think that’s the wrong question - individual presets don’t get saved (unless we’re talking about exporting an FXP, which I don’t think we are).

I think what you’re asking is when do racks get saved. In which case the answer is a) when you explicitly save the rack from the File menu, or b) when you save a song that has the rack loaded.

Having said that, I do have a task to provide better control over this including:

a) the ability to lock a rack so that it’s never saved unless you explicitly, manually save it.
b) the ability to reset the parameters of a rack’s plugins to their originally loaded values. For performance reasons this would only reset parameters - ie: values that might have been tweaked by controller assignments during performance.

See also this and this.

Brad

1 Like