Namespaces

Variants
Actions

message

From Cycling '74 Wiki
(Difference between revisions)
Jump to: navigation, search
Line 21: Line 21:
 
* Sending messages to {{maxword|name=buffer~}}  - [http://cycling74.com/2011/07/25/week-22/ Did You Know #22]
 
* Sending messages to {{maxword|name=buffer~}}  - [http://cycling74.com/2011/07/25/week-22/ Did You Know #22]
  
* Messages to Max  
+
* [http://www.cycling74.com/docs/max6/dynamic/c74_docs.html#messages_to_max Messages to Max]
  
 
==Third-Party Max externals similar to the {{maxword|name=message}} object==
 
==Third-Party Max externals similar to the {{maxword|name=message}} object==
Line 34: Line 34:
 
* {{maxword|name=send}}, {{maxword|name=receive}}
 
* {{maxword|name=send}}, {{maxword|name=receive}}
  
* [http://www.cycling74.com/docs/max6/dynamic/c74_docs.html#messages_to_max Messages to Max]
+
 
  
  

Revision as of 17:56, 30 April 2013

Contents

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 messages and other data in your patcher.

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

message Tutorials

message Tips and Workarounds

Third-Party Max externals similar to the message object

Maxobjects.com 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 refpage)