Class 02 – Leave a Message at the Beep

This week we looked  further at data flow, discussed hot- and cold inlets and Max’s order of execution as a function of the layout of connected objects in a patch. In Max, messages to connected objects flow in the following order:

  1. right-to-left

  2. bottom-up

This is also described in Max7’s Tutorial #5 which I recommend you to look at on your own.

We then learned about manipulating messages in Max. We learned how to remotely transmit messages and studied the use of variable arguments. We further looked at different ways of storing and retrieving messages and discussed the concept of ‘scope’. Please have a look at Max7’s Tutorial #16.

The ways for transmitting messages were:

  • patch cords

  • send & receive -objects (also the ‘forward’ object)

  • semicolons in message boxes

For (temporary) storage we looked at:

  • value

  • pv

  • pattr

For manipulation of messages:

  • prepend/append

  • $-arguments in messages

  • pack/unpack

  • substitute

  • sprintf

  • zl -family

I recommend taking a closer look at the [zl] object-family, which provides comprehensive set of objects for list-manipulations (e.g. the allow you to segment and join lists, but also perform some basic analysis of lists, e.g. finding the median of a list of numbers, or the number of elements contained).

You can find the patches from this week’s class on the Downloads section. This weeks assignment can be found as usual on the myCourses website.