patternmusic

I am building a sequencer that stores an ordered collection of notes in a coll object.

A major difficulty I run into with coll is that different types of output in response to different messages is sent to the same outlet.

For example, "length" sends the number of items in the collection to outlet 1. But "dump" also sends output to outlet 1. I need to make sure that the logic that responds to the output from "length" doesn't receive input from a "dump" message.

I can use a gate in front of the logic for processing output from "length". And likewise a gate in front of the logic for "dump". But since these messages may be sent asynchronously I have to make sure I close the gate following receipt of any expected data. I use a trigger to close the gates following receipt of the result data.

But there are some messages to coll that do not always result in an output. For example just inputing an address value as a presence test (i.e. is this note in our collection?). Data is only sent from the outlet if there is data at that address. Otherwise there is no output. So there is no trigger to close the listener gate.

is there a general pattern for selecting output listening paths that would work better than a listener gate with a close trigger (which is an incomplete solution)? Am I missing something obvious or some object that does this for me?

For example, "length" sends the number of items in the collection to outlet 1. But "dump" also sends output to outlet 1. I need to make sure that the logic that responds to the output from "length" doesn't receive input from a "dump" message. 

I can use a gate in front of the logic for processing output from "length". And likewise a gate in front of the logic for "dump". But since these messages may be sent asynchronously I have to make sure I close the gate following receipt of any expected data. I use a trigger to close the gates following receipt of the result data. 

But there are some messages to coll that do not always result in an output. For example just inputing an address value as a presence test (i.e. is this note in our collection?). Data is only sent from the outlet if there is data at that address. Otherwise there is no output. So there is no trigger to close the listener gate. 

outlet-listener-pattern-uses-gates-to-control-routing-of-output-from-coll-object

 [coll] to close the gate. Here's a quick example:

Use the messages sent to [coll] rather than the output received from [coll] to close the gate. Here's a quick example:


Or simply use separate references to the named [coll].

Ah! Thanks so much. The multiple references to a single named coll worked like a charm and simplifies my life greatly.

Also, dumb newby question: How do I get your example patchers into Max? I am using this Forum from my browser and the patchers just show up as an ASCII stream with ---begin_max5_patcher... etc?

https://cycling74.com/forums/common-max-arcana

Outlet listener pattern uses gates to control routing of output from coll object