@ddw_music As to the waiting problem: I always saw [text sequence -w 1] as a highly specialiced solution for only a specific set of use cases. My tendency would always be to build the logic i want outside of [text].

So another solution to the one @jameslo proposed without [text sequence] could be this:

text_post_wait.pd

@ddw_music Well, with [value], [array] and [text] we at least have nonlocal variables. Nonlocal functions are more difficult, @jameslo built some in the examples above.

This obstacle of course stems from the data flow paradigma. The common solution is to use abstractions: Build your general function as an abstraction and use it in place locally within the data flow.

If you then want shared values or states between abstractions, there are several ways to do it: Update all abstractions via [send] or use central data stores within the main patch.

@MarcoDonnarumma It may also work if you just add the word "zexy" to libraries, not search paths. The reason is that a few externals are called libraries and have to be treated differently.

And yes, there is no way to figure this out by yourself, there is no indication which external is a library and Pd should hide this complexity from the user, as it is of no relevance to the user. Pd is really flawed here. Also [declare -lib] and [declare -path] should just be [declare].

Also Deken should take care of this automatically. It is a mess.

Sorry for the german interface, this is libraries:

@jameslo Yes, and the last one can also be done with [text] to get lists.

@ddw_music List is actually a somewhat variant type, as a list of a single float is just a float and a list of a single symbol is just a symbol. So [text] should be able to do what you want. You can build a timed system with [delay] and use the information out of the [text] to set the delay.

@ddw_music Yes!

@ddw_music With [midifile] this should be somewhat similar, but i don't remember exactly what the output looks like:

@ddw_music This outputs the note/velocity pairs of a midi file almost instantly. For larger midi files it will take a while though.

You can filter for the channel afterwards if it is necessary.

@ddw_music Maybe you can use [pdcontrol] to get the path of the parent patch and use that to construct the message to [seq] within the abstraction.

@jameslo True, since it goes to a cold inlet, the order is not relevant here.