Node For Max is primarily managed through a single Max object: node.script.
When the node.script object receives a message, it will start a Node process defined by the file or package folder specified by the argument.
- Each node.script object in your Max patch can run a single process.
- Each program run in a node.script object runs as a separate process from all other processes in other node.script objects.
- A program run in a node.script object must be explicitly started with a message before it can accept input/commands.
- Automatically send a message when the program is ready by listening for a “started” notification from node.script.
- Anatomy of an N4M Patch
- Using npm
- Working with Projects and Max for Live Devices
- Differences between the js object and the node.script object
- Stopping, starting and auto-starting a process
- Using the node.debug object
- The node.scriptJS API and max-api Module
- The node.script lifecycle
- Using custom binaries for Node and npm
- Remote debugging
- stdin, stdout and stderr with node.script
There is a range of content available to either get you started with Node For Max, learn more about basic concepts or get inspired by projects other users have been using it for:
- The node.script helpfile offers examples on how to use and integrate Node for Max with your Max patch.
- While the former provides a number of focused examples, the Cycling ’74 GitHub also contains a set of small-sized projects that show typical use-cases. These include examples that integrate a Web Server into your Max patch, or connecting your patch it to the Freesound API. You can download these examples at https://github.com/cycling74/n4m-examples
- If you are looking for even more inspiration - Max users are sharing their projects and patches using Node For Max on a separate repository. Feel free to browse them or maybe even contribute at https://github.com/Cycling74/n4m-community