Forums > MaxMSP

trigger problems with uzi and coll


Sep 27 2013 | 12:32 am

Hi,

Im trying to use two uzis together to create an iterated list like the following, while querying coll for its data and combining the 3 together.

However, im really struggling to try and trigger the coll output.

The output should be

0 0 1
1 0 2
2 0 3
3 0 4
etc.

Where the 3rd element is an iter’d list from the coll output. It doesnt seem like coll is getting further than 2 iterations before it outputs

-- Pasted Max Patch, click to expand. --

really grateful for any help with regard to how to trigger this.

Cheers

Sep 27 2013 | 1:23 am

I did it with counter the other way around in the end

<code>
-- Pasted Max Patch, click to expand. --

</code>

Sep 27 2013 | 4:54 am

I know you already got it to work, but here’s a way to create the list using only 1 uzi and no coll

<code>
-- Pasted Max Patch, click to expand. --

</code>

Sep 27 2013 | 7:10 pm

Hi Rick,

Unfortunately, coll (with some different data) is a requirement for this patch. However, I really appreciate your solution. Its given me a much better way of triggering the process, which is exactly what I was looking for.

Cheers Rick.

Sep 27 2013 | 9:27 pm

This is definitely turning out to be the hardest thing ive done in max so far.

It seems impossible to synchronise the iterated data coming out of coll with the pack object. A little demo beneath show the complexity. Is there any way to do this with bondo maybe?

The data should be coming out like

0 0 1
1 0 0
2 0 1
3 0 0
4 0 1
0 1 0
1 1 0
2 1 0
3 1 0
4 1 0

<code>
-- Pasted Max Patch, click to expand. --

</code>

Sep 28 2013 | 7:13 am

well you’re iterating twice, of course the patch can’t really know when the zl iter 1 is outputting a new value here.

If you include your data in the coll and share that with us we can set it up right – this doesn’t need to get overly complicated, I don’t think.

Sep 30 2013 | 2:31 am

Hello,

In your most recent patch, the [zl iter] object runs through ALL its iterations before the other two values are sent to the [pack] object.This is because of Max’s Right – Left precedence and the resulting lists will only be those containing the last element of each list from the [coll].

You need to modify the patch so that the [zl iter] object triggers the [pack] object each time it iterates. (An ordinary [iter] object will do this too).

Here’s an illustration:

<code>
-- Pasted Max Patch, click to expand. --

</code>

best

Richard

Sep 30 2013 | 6:05 am

I’ve just looked at the original patch and maybe this doesn’t quite do what you want.

What’s the format of your desired output?

It seems to be

index of value within coll o/p list,
index of o/p list within coll,
value;

Is that right?

Richard

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

Forums > MaxMSP