From Cycling '74 Wiki
Jump to: navigation, search


message online refpage

Using the message object

The message object is one of the most basic and useful objects in Max. Despite its simple looking nature, message has a deep set of features. Max programming is made a lot easier by understanding all of the ways the message object can be used.

As well as its primary function as a delivery mechanism for messages and a list parser, the message object is a handy substitute for the Max Window. When you wish to debug a stream of data. You may connect a patch cord to the right most inlet of a message box and observe the flow of messages and other information.

The Max environment itself may be configured through the use of specially formatted messages. To find out more about this, please see Messages to Max

The keyboard shortcut for creating a message box in a patcher is the letter "m"

message Tutorials

message Tips and Workarounds

Third-Party Max externals similar to the message object listing for the message object

People who looked at/used this object also looked at....

Errors or Clarifications

(please list things that you believe to be errors or omissions from the existing ref page)

BUG: Empty String value is not stored in patcher file (Max 6.1.9)

When a message object holds a value of an empty string (by typing "" in the message object), then when the patcher is saved, closed and reopened, then the empty string value is gone, and instead we get an empty message. The difference between an empty message and a message with an empty string value, is that when clicking (or banging) a message with an empty string value, the it outputs an empty string message, while when clicking (or banging) an empty message, nothing is being output.

A workaround is to create a Java class which extends MaxObject, and have this class output an empty string whenever it is banged. Use this class with the mxj object.