Would it be more simple to write the info to a message object? There is far less risk of cross threading colls this way.

Chris

you should try how the same thing would look like when the colls are outside the poly~ and compare if it is easier to handle.

> new colls get created and destroyed accordingly.

If I understand you correctly, you want colls with no name. Each time a voice is busy, it fills the coll with data and reads it. BTW, as long as the total number of voices doesn't change, the colls will keep their data when the voice's busy state goes to 0. You can, however, explicitly clear them when the voice becomes busy (or better yet, when adsr~'s second outlet goes to 1). Unnamed colls work fine inside and outside poly~.

On the other hand, if you want the colls to refer to preexisting data, and share data with other colls, you'll probably want to use a name. The initial value will be recalled when the number of voices is changed via the voices message to poly~. When a voice changes its thispoly~ status to busy, the colls are not automatically reinitialized. Named colls work fine inside and outside poly~.