Jonathan Schmitz

So I have this patcher that is supposed to fill a coll object with a number (can be changed) of random number pairs (coordinates).

However I have to make sure that there are no duplicates, so I check back every generated number pair with a dump of all the already stored number pairs in my coll object using the zl.compare object. If there is a match the pair is discarded and a new one is generated. Until x amount of number pairs is generated.

It works fine when requesting a coll with around 45 pairs, however trying anything above causes a "zl overflow" and causes Max to freeze for 10 seconds.

What is wrong with this object? Or am I overseeing something in my patcher?

So I have this patcher that is supposed to fill a coll object with a number (can be changed) of random number pairs (coordinates).
However I have to make sure that there are no duplicates, so I check back every generated number pair with a dump of all the already stored number pairs in my coll object using the zl.compare object. If there is a match the pair is discarded and a new one is generated. Until x amount of number pairs is generated. 

It works fine when requesting a coll with around 45 pairs, however trying anything above causes a "zl overflow" and causes Max to freeze for 10 seconds. 

zl-compare-causing-unusual-overflow

I didn't get deep into your patcher, but you have two [random 7] objects, so you get ony 7*7 combinations of numbers. If you want the 50th pair of numbers, Max tries hard to find it, up to stack overflow. OTOH I try to avoid recursive algorighms in Max, as there are no optimizations for such algorighms, and the stack isn't that deep.

My intent is to only get number pairs from 0 0 to 77 and inbetween.

What do you mean by "If you want the 50th pair of numbers, Max tries hard to find it, up to stack overflow" though?

Are you suggesting that the problem is that shooting more than 50 numbers into the zl.compare object is the problem? I mean 50 isn't such a high number, so to generate 50 number pairs zl.compare would only have to do 1274 comparisons, which should be doable.

My intent is to only get number pairs from 0 0 to 77 and inbetween.
What do you mean by "If you want the 50th pair of numbers, Max tries hard to find it, up to stack overflow" though?
Are you suggesting that the problem is that shooting more than 50 numbers into the zl.compare object is the problem? I mean 50 isn't such a high number, so to generate 50 number pairs zl.compare would only have to do 1274 comparisons, which should be doable.


no, there are ony 49 possible number pairs: each random generates number in the range of 0 to 6 ([random 7] means there are 7 different integer values to be picked from, counting from 0). [zl compare] doesn't impose any limitations, because it compares only two number pairs at a time.

no, there are ony 49 possible number pairs: each random generates number in the range of 0 to 6 ([random 7] means there are 7 different integer values to be picked from, counting from 0). [zl compare] doesn't impose any limitations, because it compares only two number pairs  at a time.


If you want only integer number pairs there is much simpler way:

Ah and again, it is something simple I didn't realize. Thank you so much.

Thank you even more for that excellent alternative. I'll be sure to use it.

Ah and again, it is something simple I didn't realize. Thank you so much.
Thank you even more for that excellent alternative. I'll be sure to use it.


zl.compare causing unusual overflow