Hello,

The problem briefly stated : how can all the number2 objects in a patch can send their value when opening the patch to the whole [+] and [expr] objects without going in a tedious [loadbang] network?

The problem in detail :

I have a nice patch which use lot of [random]. My random objects are used to create a given random sequence between let say M and N (N-M is feeding the right random inlet) and M is then added to random output. This is achieved using number2 objects, some [+] and possibly [expr]. Since I don't know in advance what should be M and N ... I go for few hours of fine tuning the whole patch ... always using number2 objects with the "init" thing turned on.

After saving the patch, going to bed, wake up, turn on the patch. I don't get the results from the fine tuning ... the problem seems to come from the fact that the [+] objects must receive the number out ... which are only sent when banging, or changing the number!!! But, since I have nearly 30 number2 objects to fine tune everything ... I wont go in manually banging every number!

That drive me crazy!!! All the number are nicely set ...

Should I simply create a sending bang (from a loadbang) to every number in the patch? Is their a more elegant way of doing this?

Many thanks!

Bye bye!!

Philippe-Aubert G.

yeah, i can't see why it isn't elegant to send loadbangs to every object:

[loadbang] - [send $1-easy]

and then just make a number2 object, right click on it to change properties - for recieve, type $1-easy...and then copy that same number2 box 30 times, and replace your existing ones with the new ones.

no need for patch cables or anything.

If the number2s only feed nonleftmost inlets, and no inlet is connected from more than one number2, then hardoff's solution is a very nice solution.

It wouldn't work otherwise because the number boxes would need to be banged in a specific order to guarantee the same outcome each time. In which case you could probably factor it into groups of number2s for which it doesn't matter in which order the bangs are received, and then order those groups with [trigger].

I was surely taken by a "deadline fear" yesterday night, I did not even think to the receive property of number objects! I was planing a messy [r] network ...

It work nicely ... at this time at least, although I expect some problems regarding the banging order ... as explained by ClaudiusMaximus ... but regarding this, I plan to replace any small math operation by expr.

Thanks again!

I was surely taken by a "deadline fear" yesterday night, I did not even think to the receive property of number objects! I was planing a messy [r] network ...

It work nicely ... at this time at least, although I expect some problems regarding the banging order ... as explained by ClaudiusMaximus ... but regarding this, I plan to replace any small math operation by expr.

Thanks again!

After dealing with this few minutes, I have found that it worked perfeclty with expr object replacing any simple math objects.

But what a sad feeling to be remembered that when you use [receive symb] in a number2 properties you lost the inlet of the number!

For my own usage it is pretty sad because I also use some external controls from midi, or other type of data, which were passing through the numbers objects to contro lother objects so that when I am satisfied with a patch "state" just keep the number, save and close the patch, open it, and every paramters externally controlled is kept in the patch ...

Maybay my whole approach is not effective ...

Anyway ... number2 without receive_symb properties (thus keeping the inlet) feeding expr object initilizee with a small bang from a global loadbang object gives me what I was looking for ...

Bebye!

yeah that always mystified me as well...what do you have to gain by killing the input?

I really don't why it is like this.

Anyway, this have been quite a nice surprise to use the expr instead of anything else. Because when an expr block is banged it seems that is "reading" (?) the number2 objects which are feeding the expr inlet but without even touching the number2 objects once you open a patch.

I know use expr object with small bang object beside it. Every bang of this type receive a global loadbang. And it work ... while keeping the number inlet opened. ...

Ok, back to work I am just trying to catch up something with fractional delays and block convolution which drive may crazy because it consume time!!!

ha ha, this is weird...

The visual representation of the inlet/outlet in number2 does disapear,
but you can still connect to it just the same as if no receive was
specified. Just pretend there is an inlet/outlet visible and it works as
expected.

With the original number box the inlet does actually disapear, and you
cannot connect anything to it.

(from the pd mailing list)

Again fooled by the apparences, I will take care of this ...

Thks again, bye bye!