Jonathan Schmitz

Since the most recent Max Update (7.2.5) I have observed the join object (configured as "join @triggers 1") outputting (when receiving input in the 1st (cold) inlet) the message that was previously received by that inlet joined with the message that was just put in.

See the picture (click to see full picture):

Event #601 was received by the join object in the left (see the highlighted patchcord) inlet.

Then in event #602, the object suddenly generates output.

This only happens in some instances though. I can't seem to find out what the reason is.

Since the most recent Max Update (7.2.5) I have observed the join object (configured as "join @triggers 1") outputting (when receiving input in the 1st (cold) inlet) the message that was previously received by that inlet joined with the message that was just put in. 

See the picture (click to see full picture):
Event #601 was received by the join object in the left (see the highlighted patchcord) inlet.
Then in event #602, the object suddenly generates output.

This only happens in some instances though. I can't seem to find out what the reason is.
Anybody got an idea?


join triggered by cold inlet [bug]