Hello there. I'm fairly new at Pure Data, so I'm sure there's a lot of things I haven't put into perspective or use as of now , so please say if something sounds off.

I've got two things I need help with.

1. Unique abstraction names and send/receive paths. I'm slowly making small user-friendly abstractions out of the patches I make, if they're widely used tools, such as small interfaces for filters, gainstages, delays and what not, so I can easily use more of them in a single patch if needed.
   Usually the sends are called something like "gainsend1" or something. But as soon as I use more than one instance of the module, I have to rename every new instance of the patch and its subpatches to, say, "gainsend2". Is there an effective way to sort this out? I've been trying to see if I can add a number atom in the abstraction gui to choose what numerical variable is applied to the given abstraction. "sendname $1". Is there some message that allows me to easily change this? A "set xxxx $1" message or sorts?

2. When creating and working with visual sliders in abstractions, I'd like for the max and min values to be set by a number atom next to the slider, to make the module more easily customizable for wider use, i.e there's no need for me to have a standard hslider going from 0 to 3000, if I for the given patch, only need to work within 0 to 10, and thus making it harder to discern the difference in the slider's position.
   Is there not a "set max $1"/"set min $1" message? or am I looking at this the wrong way?

On advance, thank you.

M.

Hi and welcome to the forum,

1. You should add a $0 to the name of you sends and receives in order to make them unique in each abstraction. Please read more about it here: http://en.flossmanuals.net/pure-data/ch043_dollar-signs/ (and notice that $0 is a completely different beast than $1, $2, $3, etc... )

2. Use the message [range <min> <max>(. E.g.:

Hope this helps, cheers!
Gilberto

Thank you very much, Gilberto.

So is $0, in this particular case, only used as a replacement variable that doesn't receive or send input to another $0unless it's located in the same subpatch?

M

Another thing I just noticed, is that if I try to use $0 in the send/receive options for an object, i.e a visual slider, it discards the $when I close the properties tab.

@Hasselbalch Hello Hasselbalch..........
If you use the name $0-gainsend1 then for each abstraction a different value is assigned to the $0 and everywhere in that abstraction it will be the same value.
so in abstraction 1 it will become 1003-gainsend1 and in abstraction 2........ 1004-gainsend1 etc. (for example....... the problem? later is that you cannot know in advance the number)....
In the properties box I think you have to put #0 instead of $0 if I remember correctly (it's a quirk)...
David.

@gsagostinho, I suppose that screenshot is pure data running under linux. Does the patchcords curve naturally in that version or is that a modification one can download?

@whale-av, I think #0 did the trick. Thank you.

M

@Hasselbalch There are basically two uses of $1, $2, $3 ...: 1) when dealing with abstractions, you can use these signs with objects such as [f $1], [+ $3] so they are replaced by the n-th arguments of the abstraction, and 2) when used in a message such as [range $1 $2(, they are replaced by the n-th item in a list arriving to that message (such as in the [range $1 $2( example I posted above).
As David explained above, $0 is actually a fixed number which is unique to each instance of an abstraction. You can find out which number is being given to an instance by banging a [f $0] like this:

So basically when you create a send or receive named $0-foobar, you are actually telling each instance of an abstraction to substitute the $0 for whatever number it has been assigned to. So while one instance have $0 as let's say 1023 (and therefore the send/receive name set as 1023-foobar) the other may have something like 1047-foobar, hence why the messages get deliver only locally.

About the curved cables, I am using Pd-l2Ork on Linux, which is a distribution of Pd that has curved cables. But AFAIK it's available only on Linux as of now.

Cheers,
Gilberto

Hello. I just wanted to say thank you, I got all the help I needed.
M.