Deru

sorry if this has been dealt with before...

so i've built a few plug-ins using pluggo and all is fine and dandy, except that when i go to hit "save" in Nuendo, all of my GUI knobs/sliders and number boxes reset back to their default values. also, when i close and open up the session again none of my values are saved either.

could this have something to do with the "plugconfig" file?

i'm using the latest Nuendo. msp 4.5.7. pluggo 3.5.4

hey all,
sorry if this has been dealt with before...

could this have something to do with the "plugconfig" file?
thanks!!! any help is great.

i'm using the latest Nuendo. msp 4.5.7. pluggo 3.5.4


my-plugin-settings-reset-when-i-hit-save-in-my-sequencer

btw, here's my plugconfig file, if it helps:

#C setprogram 1 "Program 1" 0 1. 0. 1. 0. 0. 0. 0.;

#C useviews 0 1 1 1;
#C numprograms 18;
#C preempt 1;
#C sigvschange 1;
#C sigvsdefault 32;
#C setsize 269 340;
#C defaultview Interface 0 0 0;
#C dragscroll 1;
#C infotext;
#C setprogram 1 "Program 1" 0 1. 0. 1. 0. 0. 0. 0.;
#C uniqueid 128 157 227;
#C initialpgm 1;


i figured it'd probably be something fairly common/easy.

has this issue never come up?
i figured it'd probably be something fairly common/easy.
thanks!

so for everyone else, when they quit their sequencer (using Pluggo's that they have made) and open back up their sessions, all their settings are intact?

oh man, i would kill for that right now. this is driving me nuts!

Do you have all your sliders and whatnot hooked up to pp objects?

I guess because you have some data in the preset part of your plugconfig you perhaps do.

Show us a part of the patch which is not restoring correctly....

yes, all of my sliders and number boxes are hooked up to pp's.

i've never sent anyone a max patch via this forum so hopefully this works. let me know if not. i've saved it as a text file and i'll upload it here. i guess the other option is just copying and pasting the text here. i guess i've seen people do that too. let me know if one's better than the other.

it's a simple sample/hold bit-reduction plug-in so it's a good example of what i'm talking about. it happens with a few plugs i've built. all the sliders reset to the first stored preset when i hit "save."

hey Andrew, 
yes, all of my sliders and number boxes are hooked up to pp's.
i've never sent anyone a max patch via this forum so hopefully this works. let me know if not. i've saved it as a text file and i'll upload it here. i guess the other option is just copying and pasting the text here. i guess i've seen people do that too. let me know if one's better than the other.

> yes, all of my sliders and number boxes are hooked up to pp's.

in your patch only the output from pp is connected to the gui. how is 

the pp supposed to 'know' the current value of the gui if you don't 

also watch out, that you have the correct value range set in the pp.

e.g. [pp Rate 1. 22050.] in your patch is connected to a uslider with 

look at this (select the text, and copy. go to max and choose file- 

> hey Andrew,
> yes, all of my sliders and number boxes are hooked up to pp's.

in your patch only the output from pp is connected to the gui. how is  
the pp supposed to 'know' the current value of the gui if you don't  
send it to pp?
also watch out, that you have the correct value range set in the pp.
e.g. [pp Rate 1. 22050.] in your patch is connected to a uslider with  
range 0 700

look at this (select the text, and copy. go to max and choose file- 
 >new from clipboard):

"oh, it does not know? why doesnt it just look it up?"

thanks Andrew. this makes perfect sense now. i knew it was probably something simple i was overlooking. i didn't think about sending back the pp values. of course this seems stupid now. THANK YOU!!!

it seems that people very often run into this trap, and 

maybe it is because the tutorials and examples are very 

they all use this numberbox connected to the pp.

i have never usedit in a plug-in, but see it in many 

peoples patches - they copy it from the tutorials because 

two more useful ways of making parameters (or "classic", 

or "common" if we want to call it like that) will look

... i am trying out the attachment upload from the 

it seems that people very often run into this trap, and 
maybe it is because the tutorials and examples are very 
confusing here.
they all use this numberbox connected to the pp.

what is that numberbox good for anyway? 
i have never usedit in a plug-in, but see it in many 
peoples patches - they copy it from the tutorials because 
they tink its needed somehow.

two more useful ways of making parameters (or "classic", 
or "common" if we want to call it like that) will look
like this:

 ... i am trying out the attachment  upload from the 
forum now. :)

yeah, that's exactly where i got the number boxes. it's much cleaner without them as well.

is the point of going out of the "trigger" object in the second example just to make sure you're always getting values from the pp to avoid my mistake?

the attachment worked great (on OSX at least). it came up as a text file. it's probably really useful for big patches.

hey Roman,
yeah, that's exactly where i got the number boxes. it's much cleaner without them as well.

no, the trigger in the second example will only make sure

that automation data from the host program is getting

as fast as possible to the signal object.

this is pontless for a multislider - but it gets 

interesting when you are connecting some hughe java- or 

lcd-based interface object as actual parameter, especially

when the messagepath is interrupted by "set" messages and

then it is modular thinking - you can now exchange the

multislider with a numberbox as GUI without disconnecting

no, the trigger in the second example will only make sure
that automation data from the host program is getting
as fast as possible to the signal object.

this is pontless for a multislider - but it gets 
interesting when you are connecting some hughe java- or 
lcd-based interface object as actual parameter, especially
when the messagepath is interrupted by "set" messages and
stuff like that.

then it is modular thinking - you can now exchange the
multislider with a numberbox as GUI without disconnecting
the delay~ object. :)

awesome, that makes sense.
good to know this stuff!!

my plugin settings reset when i hit save in my sequencer...