Hey,

Banging my head off a (probably obvious) wall here: making a fader able to be 1) set, 2) fade out, 3) fade back to held value. How next to make the GUI respond to the values without creating a stack overflow? It needs to be the same [vslider]...
fadeout&in.pd

You can use set for this. set sets the value of the slider without having it being output. See also the help file of the slider.

fade-out-in.pd

@ingox Thanks so much for your help here, this works beautifully. However I'm still stuck on the next step: I'm writing a patch for MobMuPlat and when I send the values from your bottom-most number I get into a feedback loop. Is it possible to convert your patch into a subpatch with an external slider that responds to fade up and down levels?
Thanks again!
Seán

@Seán Where are you sending the number or where does the feedback loop come from? And what do you mean by 'responds to fade up and down levels'?

@ingox Here's a patch to explain. I'm really trying to get the same one fader to respond and output the numbers of the fade up or down. If that makes sense? Your fader on the right in this patch sets the number but doesn't output it. Apologies for not 100% sense here! and thank you!
fade_out_in.pd

@Seán You cannot use the same fader to output, as that will always cause the overflow.
You can fake it like this........ with an abstraction (or a sub-patch...... I stand corrected by @ingox)
new.zip
David.

Ah ok, thanks, I did have it working in Max so I'll make a workaround. Many thanks to you both! Seán

@Seán Yes, you can do it with an abstraction, you can do the same with a subpatch.

Here are two additional ways to protect against stack overflow:
stack-overflow-protection.pd
[change] will let the same value through only once. The downside is that it is set to zero from the start, so if you want to allow zero to come through from the beginning, you can use the second case which is like [change] but is set to -1 (assuming that -1 is not used as a value).

But if you think about it, my example above already does almost exactly what you want, using sends and receives to separate the GUI from the program logic. In my humble opinion, if you think GUI and program logic separately, it frees the mind.

GUI objects have one send and one receive, so everything else has to be done outside. Here is a slightly modified version of the above patch to illustrate that. You can of course rename the sends and receives to your liking: fade-out-in2.pd