anamaria

I have a max patch that breaks down, when I start to collect numbers into a list at a sample rate of 20 ms.

Why does max break down? Perhaps there is a more effiscient way of making the below patch?

max-breaks-down-problem-with-collect

hmmm ... looking at it closer - it looks like the update-data interferes with the incoming interaction data.

Especially when I replace the "interaction data" generator with the real incoming data that I have. The sample rate of the incoming data is varying, and the update-data message updates the list every20 ms.

... are there any other objects than collect that can be used to add numbers to a list? It seems like max breaks down because it can't handle the stream of numbers that go into the collect object/max abstraction.

If you want to look for another approach to list processing in max, you can give a look to the bach library:

among the others, you have a bach.collect external...

Hi.
If you want to look for another approach to list processing in max, you can give a look to the bach library:
www.bachproject.net
among the others, you have a bach.collect external...
best
aa


However, the thing I am asking for should be simple to just do with the original max objects ... I am afraid that my problem has something to do with the way I add numbers to the list and the way I update the numbers before they are updated to the list ...

max breaks down ... (problem with collect?)