woyteg

The trigger object has some undocumented behavior (as far as I can see).

I know it can trigger/let tthrough signals by writing [t signal].

I'd like to trigger something after a matrix is received but

(I know I can get this behavior by just putting the processes in a left to right alignment in the patcher since max is executing opperations based on location in patcher if not explicitly ordered by [t] or similar. I'd like to avoid tis.)

Hi,
The trigger object has some undocumented behavior (as far as I can see).
I know it can trigger/let tthrough signals by writing [t signal].
Is there a jitter matrix equivalent?
I'd like to trigger something after a matrix is received but
[t b matrix]
[t b jit.matrix]
[t b jitter]
don't work.. Any help appreciated!

(I know I can get this behavior by just putting the processes in a left to right alignment in the patcher since max is executing opperations based on location in patcher if not explicitly ordered by [t] or similar. I'd like to avoid tis.)


trigger-matrix

The 'list' or 'l' argument to trigger will pass a matrix. The Jitter matrix patch cord is actually passing a message with a reference to the matrix name, in the format:

You can see this if you connect a matrix (green) patch cord to the print object.

The 'list' or 'l' argument to trigger will pass a matrix.  The Jitter matrix patch cord is actually passing a message with a reference to the matrix name, in the format:

You can see this if you connect a matrix (green) patch cord to the print object.


trigger matrix