ethangreene

I'm at my wit's end with a coll problem, so I thought I'd send out a plea for help. Can anyone find a reason why this coll would return to 1 after the 6th index? It seems to go to 6, and then move instantly to 7, back to 6, and finally to 8 -- then it resets. I have tried everything. PLEASE HELP!

Here is the text in my coll (patch also attached):

1, 1. 0 0 0 0 0;
2, 2. 500 1. 1000 3000 0;
3, 2. 500 1. 1000 2000 0;
4, 2. 3000 1.5 1000 4000 1;
5, 3. 8000 3. 0 0 2;
6, 4. 4000 5. 3000 12000 3;
7, 6. 2000 6. 0 0 0;
8, 7. 4000 7. 0 0 0;
9, 8. 18000 8. 0 0 4;
10, 9. 8000 9. 0 0 0;
11, 10. 12000 10. 0 0 0;
12, 11. 16000 11. 0 0 5;
13, 12. 8000 12. 0 0 0;
14, 13. 4000 13. 0 0 0;


coll-bug-2

it works from 1 to 14 in cycles, no problem here.

but many problems with doing coll-operations like this (start, next etc) are caused by parallel instances. the operations don´t work locally on the instance, they treat the coll globally, means every instance of the coll referring to the same name.

What xidance said. As long as you have numerical indices, you could drive it with a counter and achieve independence between instances.

Thanks guys! But I don't have any other instances of the same coll, so I can't understand what's going on. Is there some way I could have a parallel instance without knowing it?

not really, coll is very stable and bug free. i use it since ever and every day.

but i´m not sure what´s oustide the subpatcher you posted, means what triggers the "next"-message. maybe the "goto" interrupts.

See that's the weird thing -- the next message is simply triggered by a bang, which the user has to press himself. It's confounding. I really wish I could figure this out...

Oh my god, I figured out the problem. I was using pattrstorage, and forgot to deactivate the int boxes that were controlling the coll. So stupid!

Oh my god, I figured out the problem. I was using pattrstorage, and forgot to deactivate the int boxes that were controlling the coll. So stupid!
Thanks for your help, guys!


coll bug?