Forums > MaxMSP

Coll Ignores entries with same first number?

December 16, 2012 | 11:43 pm

When I try to output part of one coll into another, entries with the same starting values are ignored.

Coll One:
[0, 55 3 2 3 8 3 8 7 8 7 6;
1, 55 6 6 2 0 9 8 1 9 7 7;
2, 46 7 8 2 6 2 3 0 4 7 7;
3, 44 3 1 3 9 6 8 1 7 1 5;]

I clear coll two, goto start on coll one, and use uzi to bang coll one 4 times. Yet my coll two only has three entries! When the entries start with different values, this patch works correctly.

Coll Two:
[55, 6 6 2 0 9 8 1 9 7 7;
46, 7 8 2 6 2 3 0 4 7 7;
44, 3 1 3 9 6 8 1 7 1 5;]

Patch attached. thanks.


December 17, 2012 | 12:22 am

You need to append the index number, at the moment you’re using the first items of the stored list as a new index and you have two entries starting with 55, this is why one of them is being over-written. Here’s an example of what I would do (in Max5, I know that [zl] is a bit different in Max6 but the principle is the same).

– Pasted Max Patch, click to expand. –

December 17, 2012 | 9:43 am

Here’s another example. Also take a look at the refer message to coll, it might be all you need.

– Pasted Max Patch, click to expand. –

December 19, 2012 | 12:41 am

Thank you both. I think I’m going to have to stare at these examples for a while longer before I really internalize how they work.


December 19, 2012 | 6:09 pm

Remember, the first value in a coll’s data row is a KEY: if you do not provide clearly a unique key, the row will be overwritten when the first value (always *seen* as key) is not unique: and coll does not provide this key auto-magically: it is usually sent as first value in row, separated with comma: obviously, if you do not provide a key ("lookup") value, it takes the first data in the sent row as the key, adding in the comma.


Viewing 5 posts - 1 through 5 (of 5 total)