@prandam Another way to achieve the same: abacus3.pd

The [mod 10]s are not actually needed for the functionality, they are only to have nice numbers

@jancsika Brute-force gives 4481 and 19641

bruteforce.pd

@ddw_music Yes, this is unfortunate. It is probably better to use [text] for more control.

@ddw_music Does this work for you?

@prandam "texto: multiply defined" means that you have multiple [text define texto] objects open. There should only be one text object with the same name in each patch including subpatches. If you want to use the same name in multiple patches or open the same patch multiple times, you should use $0 in the name to protect against the above error. It is a general advice to use $0 in array and text names as well as in send and receive names.

So using [text define $0-texto] and [text get $0-texto] and so on should solve this issue

@JJLloyd Yes, but it is still possible to use [s]/[r] and the hidden sends/receives in the GUI objects without losing control over the order of operations.

For example, here both number boxes on the left (main GUI) send to the number boxes on the right and the values are stored in [f] objects using the cold inlets.

When the code executes by using the bang, the order of operations is completely defined:

@yannseznec Then the error might be coming not from the array, but from another object with the same name? Sometimes Find > Find last error shows the source of the error

@simorr This uses [cyclone/seq] and [cyclone/midiparse] and should do what you want to achieve: readmidi.pd

This should work. You can use [print] after the [pack] to check. You can also use [array size $2] instead.

@simorr You can do something like that: bangfilter.pd

You can specify the delay time by creation argument or right inlet.