Notice: This page contains information for the legacy Phidget21 Library. Phidget21 does not support VINT Phidgets, and will not support any new Phidgets. Phidget21 will be maintained until 2020. We recommend that new projects be developed against the Phidget22 Library.
Difference between revisions of "Language - Max/MSP"
|Line 1:||Line 1:|
[[File:icon-MaxMSP.png|link=|alt=MaxMSP|64x64px]] Max/MSP, developed by [http://cycling74.com Cycling74] is a visual programming language for creating music and media applications.
[[File:icon-MaxMSP.png|link=|alt=MaxMSP|64x64px]]Max/MSP, developed by [http://cycling74.com Cycling74] is a visual programming language for creating music and media applications.
Revision as of 17:28, 20 April 2012
|Max/MSP, developed by Cycling74 is a visual programming language for creating music and media applications.|
- 1 Introduction
- 2 Quick Downloads
- 3 Getting started with Max/MSP
- 4 Windows (2000/XP/Vista/7)
- 5 OS X
- 6 Follow the Examples
- 7 Code Snippets
- 8 Common Problems and Solutions/Workarounds
If this is your first time working with a Phidget, we suggest starting with the Getting Started page for your specific device. This can be found in the user guide for your device. That page will walk you through installing drivers and libraries for your operating system, and will then bring you back here to use Max/MSP specifically.
Max/MSP is capable of using most of the Phidget API, including events. All the supported functions for Max/MSP will be documented in the
.help files. We also provide example code in Max/MSP for all Phidget devices.
Max/MSP can be developed with Windows and OS X.
Only Max/MSP 4.5 or higher is supported.
You can compare Max/MSP with our other supported languages.
Just need the Max/MSP documentation, drivers, libraries, and examples? Here they are:
.helpfile(Windows - same file as Max/MSP Examples and Libraries)
.helpfile(OS X - same file as Max/MSP Examples and Libraries)
- Example Code (Windows - same file as Max/MSP Documentation and Libraries)
- Example Code (OS X - same file as Max/MSP Documentation and Libraries)
Libraries and Drivers
- Max/MSP Libraries (Windows - same file as Max/MSP Documentation and Examples)
- Max/MSP Libraries (OS X - same file as Max/MSP Documentation and Examples)
- 32-bit Windows Drivers Installer
- 64-bit Windows Drivers Installer
- Windows Driver and Library Files (Zipped)
- OS X Drivers Installer
Getting started with Max/MSP
If you are new to writing code for Phidgets, we recommend starting by running, then modifying existing examples. This will allow you to:
- Make sure your libraries are properly linked
- Go from source code to a test application as quickly as possible
- Ensure your Phidget is hooked up properly
Instructions are divided up by operating system. Choose:
Description of Library Files
Max/MSP programs on Windows depend on the following files. The installers in the Quick Downloads section put only the
phidget21.dll into your system. You will need to manually put the
PhidgetXXX.mxe onto your system.
phidget21.dllcontains the actual Phidget library, which is used at run-time. By default, the installer places it in
PhidgetXXX.mxeis the Phidget library for your specific device. XXX denotes the name of your device, Please make sure the
.mxefile corresponds with the device you are using. For example, if you are using the PhidgetInterfaceKit, you will need the
PhidgetInterfaceKit.mxe. It is to be placed in the same directory as your Max/MSP application or anywhere in the Max/MSP search path.
Use Our Examples
Please start by downloading the Max/MSP Examples and Library and unpack them into a folder. These examples were written in Max/MSP 4.6, but any version above 4.5 are also supported.
Here, you will find example programs, in
.help format for all the devices. If you aren't sure what the software example for your device is called, check the software object listed in the Getting Started guide for your device.
The only thing left to do is to run the examples! Open the
.help file in the Max environment.
Once you have the Max/MSP examples running, we have a teaching section below to help you follow them.
Write Your Own Code
When you are building a project from scratch, or adding Phidget function calls to an existing project, you'll need to configure the Max/MSP environment to properly link the Phidget Max/MSP libraries. To begin:
.mxe in the same directory as the patcher, or anywhere in the Max/MSP search path. You can verify the search path locations by navigating to Options → File Preferences.
The best way to start writing your patch is to modify an example, and saving it as a
If you wish to start a new patch. All you need to do is create an object named PhidgetXXX where XXX is the name of your device. For example, the PhidgetRFID device will have the
PhidgetRFID object name.
The project now has access to the Phidget function calls and you are ready to begin coding.
The same teaching section which describes the examples also has further resources for programming your Phidget.
Max/MSP has excellent support on OS X.
The first step in using Max/MSP on Mac is to install the Phidget library. Compile and install them as explained on the getting started guide for your device. Then, the OS - OS X page also describes the different Phidget files, their installed locations, and their roles....
Follow the Examples
By following the instructions for your operating system, you probably now have a working example and want to understand it better so you can change it to do what you want. This teaching section has resources for you to learn from the examples and write your own.
First, let's explain how to operate the example.
The above screenshot is what shows up when you open the example for the PhidgetInterfaceKit. If you are using a different device, your example patch will be different, but the idea is the same.
For this particular example, the Max object is called
PhidgetInterfaceKit, which is located in the center of the screen. Objects/message boxes are connected to the inputs and outputs of the PhidgetInterfaceKit object. The input objects will either cause a property of the device to change or request for a property to be retrieved. The output objects return the retrieved information. All the supported features of the device are shown in the
Try it for yourself! Click on the
getSerial message box to request the Phidget to retrieve the serial number of the device. You should see the last output object of
route changed to the serial number of your device. All devices support the
getSerial object, and is the easiest way to determine if the Phidget libraries are correctly set up, and whether the Max/MSP application is connected to your device.
If your example contains the
read message box, click on it. This will return device specific values to the screen.
If your example contains the
start message box, you can continuously poll for events. Set the sample rate input for the
setSampleRate object. Then, press the
start message box to start sampling. When a noteworthy event occurs on a Phidget(i.e., when an analog sensor senses a change in the environment), the value will be displayed onto the screen. Press the
stop message box to stop sampling.
For the PhidgetInterfaceKit example, there also a
setoutput message box. Clicking on the check boxes will cause the digital outputs of the PhidgetInterfaceKit device to change. Your example may contain device specific message boxes/objects to click on. See for yourself what they do!
For information regarding calls specific to your device, please see the API for your specific device. Please note that some device functionality are not supported in Max/MSP; the
.help example shows the complete list of functionality supported under Max/MSP.
Common Problems and Solutions/Workarounds
Crash: When a patch file is closed in the Max/MSP environment, the program crashes
If in your Max/MSP environment, you have more patches(of the same Phidget object) than you have of the actual hardware device, the Max/MSP environment may crash. This is due to the fact that a single Phidget Max/MSP object only corresponds to a single Phidget device hardware. For example, your Max/MSP environment may experience unexpected behavior while you have one PhidgetInterfaceKit device connected to the computer, but you have a two seperate patches opened with a single PhidgetInterfaceKit Max object in each one.
Likely Fix: Please ensure that you do not use more patches(of the same Phidget object) than you have of the actual Phidget device.