Dan Nigrin

I have a self-developed Pluggo which has lots of pp objects to allow 

for host automation; I have limited the number of programs to 1 (in 

the plugconfig object), though, as I'd just like to have one default 

set of parameters loaded upon first plugin startup, and then I will 

manage my presets using the pattr family from there.

However, in some plugin hosts, if you save a session with active 

plugins, it will remember both the preset you had loaded in the 

plugin, as well as any changes you made to the parameters after 

loading the preset, and load your plugin in exactly the same state 

I hope I made my request clear - is this kind of parameter saving 

behavior possible with a Pluggo? Or do users of my plugin have to 

remember to save a pattr-based info first, and then manually recall 

202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X

I have a self-developed Pluggo which has lots of pp objects to allow 
for host automation; I have limited the number of programs to 1 (in 
the plugconfig object), though, as I'd just like to have one default 
set of parameters loaded upon first plugin startup, and then I will 
manage my presets using the pattr family from there.

However, in some plugin hosts, if you save a session with active 
plugins, it will remember both the preset you had loaded in the 
plugin, as well as any changes you made to the parameters after 
loading the preset, and load your plugin in exactly the same state 
the next time you open the project.

I hope I made my request clear - is this kind of parameter saving 
behavior possible with a Pluggo? Or do users of my plugin have to 
remember to save a pattr-based info first, and then manually recall 
it each time the plugin is loaded??

Thanks,
Dan
-- 
Dan Nigrin
Defective Records
202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X
http://www.defectiverecords.com
http://www.jackosx.com


best-preset-approach

when you want to be able to recall preset 1 in order to

go back to default settings, but you also want changes

to be saved with the project, your best bet is to use

(preset #1 will also have the default settings, but will 

when you want to be able to recall preset 1 in order to
go back to default settings, but you also want changes
to be saved with the project, your best bet is to use
preset #2 for the default settings.
(preset #1 will also have the default settings, but will 
be used to save it with the song.)


At 11:02 PM -0600 8/7/06, Roman Thilenius wrote:

Yes, the report I got was from an SX3/Nuendo3 user, but I assumed 

that many other hosts behaved that way; is that not the case? How do 

other hosts do it? They just leave saving the plugin's settings up 

to the end user, and just recall the actual preset that was selected 

at the time, and not any subsequent UI changes that might have been 

>when you want to be able to recall preset 1 in order to

>go back to default settings, but you also want changes

>to be saved with the project, your best bet is to use

>(preset #1 will also have the default settings, but will

So does the host actually change the plugin's presets? Or does it 

just remember which preset was selected, and then any subsequent 

At 11:02 PM -0600 8/7/06, Roman Thilenius wrote:
>i assume you need to work it in SX.

Yes, the report I got was from an SX3/Nuendo3 user, but I assumed 
that many other hosts behaved that way; is that not the case?  How do 
other hosts do it?  They just leave saving the plugin's settings up 
to the end user, and just recall the actual preset that was selected 
at the time, and not any subsequent UI changes that might have been 
made?

>when you want to be able to recall preset 1 in order to
>go back to default settings, but you also want changes
>to be saved with the project, your best bet is to use
>preset #2 for the default settings.
>(preset #1 will also have the default settings, but will
>be used to save it with the song.)

So does the host actually change the plugin's presets?  Or does it 
just remember which preset was selected, and then any subsequent 
changes to that preset?

best preset approach