saving script variable with the workspace

[sm_jamieson]

I am fairly new to VST hosts and VSTi instruments, but as I understand it, when a workspace is saved, it will save the current VSTi settings (presets, effects settings, etc.) using some part of the VST protocols.

I also believe that the current parameter settings of the various modules (switches, faders, etc.) are saved with the workspace - which means that the current values of the script parameters (inputs and outputs) will be saved.

But is there a protocol for a script to request some of its internal state (e.g. global variables) be saved with the workspace ?

Thanks,
Simon.

[shawnb]

I only have a couple of global variables. I use 'const' modules for those.

Main example: to store colors I like. I hook up a color selector to a 'const' input, select a color, then delete the color selector. The values are saved in the const module. Now I can copy/connect that 'const' wherever I want & reuse the color.

(I wish I could rename the 'const' module, that would make it even a little more friendly.)

For sets of values, you might want to read up on the preset manager & preset panel. (Haven't used them yet myself.)
http://www.sensomusic.com/wiki2/doku.ph ... s:preset&s
http://www.sensomusic.com/wiki2/doku.ph ... setpanel&s