Objects			page : 1 2 3 4 5 6 7 8 9
pitchTrackerBP	Module		an interface for audio and MIDI pitch tracking
pitchTrackerMIDIBP	Module		an interface for MIDI pitch tracking
playbar	External		Standard Quicktime movie play controller as a user interface object Currently, playbar can only be used to control movies. It can also serve as a progress indicator while a movie is playing.
play~	External		Sample playback based on position within a buffer~ play~ is a playback interface for buffer~ that plays back samples based on an offset within the sample. See groove~ for another sample playback interface. play~ is typically used with line, but can be used with any signal that generates a changing position value.
plugmultiparam	External		Define an array of plug-in parameters (pluggo) plugmultiparam is similar to plugparam in that it defines plug-in parameters. However, parameters defined with plugmultiparam are hidden from the plug-in Parameters slider interface, and are intended to work with the multislider object in the configuration shown below.
pp	External		Define a plug-in parameter (pluggo) pp defines the name and index of a parameter for a plug-in. This allows it to be automated by the hosting program and changed with the plug-in slider interface. Values changed in these ways are sent out the object's outlets.
pvar	External		Connect to a named object in a patcher ; send receive pvar lets you build user interfaces in one part of your patcher that are connected to the "process" part in another part of the patcher. pvar does not work globally (as send and receive do). The pvar object and its associated object must be in the same patcher.
qtmusic	External		Interface to Quicktime music architecture
rcx	External		rcx is an interface to the LEGO MINDSTORMS RCX device rcx is an interface to the LEGO MINDSTORMS RCX device. It uses the Ghost API from LEGO to connect to the device, using either a USB or serial port. Note that it does not use the serialX or serial objects for this communication.
recorderBP	Module		an interface for stereo recording from a patch
Rockband Drum Midi Interface	Patch		This patch makes it so that you can just plug your rockband drum controller into your computer via usb and send the midi messages over the IAC Bus or Midi Yoke to whatever midi supported drum machine ( or softsynth or sampler ) you wish to play. Change the number boxes at the bottom of the patch to change the notes which are output, save the note output configurations with the preset object to the right by holding shift and clicking the dot once you have a midi configuration that you like. 1 comment
router	External		matrixctrl-compatible Max message router router is a Max object which lets you patch multiple sources of Max data to multiple destinations dynamically (sort of like a series of nested switches and gates). It is designed to work best with the matrixctrl user-interface object, and uses a syntax equivalent to the MSP matrix~ object.
rtcmix~	External		encapsulates RTcmix, a digital synthesis, signal-processing and scripting/scheduling language Version 1.8 (Max5) of the [rtcmix~] object is available for free download: http://rtcmix.org/rtcmix~/ for Macintosh OS X (10.5/10.6). Windows 7 version coming soon! (maybe…) New features in this release include a number of new 'instruments', a dynamic envelope/control system to allow interactive modification of instrument controls (PFields in RTcmix-parlance), and nice tuning-system and numerical function packages by Joel Matthys. For those who don't know, [rtcmix~] encapsulates the "musicN"-style sound synthesis and signal processing language RTcmix within Max/MSP. RTcmix includes a robust scheduler and large set of pre-compiled synthesis and signal-processing instruments. It also comes with a functional-style ("C-like") programming interface for algorithmic compositional work as well as data storage and mathematical operations. Full source for the object and the language are also on-line. Both Macintosh OSX and Windows XP versions (older) are available. I hope you enjoy using it! For more information about RTcmix, visit the RTcmix web page: http://rtcmix.org/ Brad Garton, Director Columbia University Computer Music Center http://music.columbia.edu/~brad
rytm	External		rytm provides a rich interface to communicate with Analog Rytm MKII through sysex. It has verbose and informative error reporting, inherits all the features of rytm-rs and provides comprehensive documentation. Source code, readme and docs: https://github.com/alisomay/rytm-external Anoucment thread: https://www.elektronauts.com/t/announcing-rytm-the-first-maxmsp-external-for-analog-rytm
sadam.dom	Javaclass (mxj)		A Document Object Model (DOM) interface for Max. sadam.dom will create, read, store or even modify DOM trees. The DOM is one of the possible representations of the contents of an XML document (see http://www.w3.org/TR/DOM-Level-2-Core/.) The object internally uses the default Java DOM parser that comes as an instance of javax.xml.parsers.DocumentBuilderFactory, bringing all the power and almost all of the functionality of a W3C-certified DOM parser to MaxMSP. The kind of Nodes currently not handled by sadam.dom are: Comment, Entity, EntityReference, Notation and ProcessingInstruction. When an XML is parsed, the object will assign a unique ID to each Element of the document, called the Element Index. This index won't get stored and changes each time when the order of Elements in the XML is modified (either by inserting or removing Elements). However, using the Element Index is the preferred (and in most cases, the only) way to address a given element in the XML. The Element Index is sent out the rightmost outlet each time an element is accessed. The Element Index of the Document Element is always 0, the rest of the Elements get their index in their 'order of appearence'. This means that even if an Element is being inserted or removed, the Index of the Elements that come earlier in the Document won't change. When querying Attributes, Text, or CDATA nodes, the requested data will be sent out the appropriate outlets in right-to-left order (in case of Attributes, if more than one Attribute is requested, they will be sent to the output as a sequence like AttributeName1-AttributeValue1-AttributeName2-AttributeValue2-...-AttributeNameN-AttributeValueN, alternating on the appropriate outlets) followed by an error code. When querying Elements, the result will be sent out as a sequence (from right to left) consisting of the Element Index, the Tree Depth of the Element (the Document Element is at level 0, its children are at level 1 etc.), the Element's Tag Name, the Attributes, and finally the Text Content (which is a concatenation of all Text and CDATA nodes). The leftmost outlet serves as an error outlet. After each command sent to the object, an error code is being sent back through this outlet at the end of the execution of the given command. A negative value means that the command could not be executed successfully, while 0 means success. In some cases (typically when one or more Elements are queried) the error outlet reports the number of Elements successfully returned. sadam.dom and sadam.sax are both W3C compliant XML parsers, however, this means some overhead in terms of resources. If you need a lightweight, fast XML parser and you can live with some limitations regarding W3C compliance, consider using sadam.rapidXML.
page : 1 2 3 4 5 6 7 8 9

Libraries
EAMIR - the Electro-acoustic Musically Interactive Room	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='133'V.j. Manzo	The EAMIR project is an open-source effort to enable educators with technology for music education. Software is designed around a common configuration which can be easily implemented by music educators around the world by downloading source code and standalone applications through eamir.org. Users who understand programming can edit the source code and post their new source and standalone applications back to the site for the EAMIR community to use. Much of the EAMIR software is also designed to allow students with physical and mental disabilities to create meaningful music using interfaces that are accessible to their needs. The EAMIR SDK allows users to easily create their own EAMIR-like applications by connecting preassembled interface modules to musical modules. The interfaces include cameras with color tracking, guitar hero controllers, wii remotes and devices, dance dance revolution pads, and other gaming controllers as well as traditional MIDI instruments like keyboards. created by V.J. Manzo www.vjmanzo.com | www.eamir.org
hi.tools	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='158'Max Egger	An alternative to Max/MSP’s hi object, 2010 by Max Egger hi.tools lets you communicate with human interface devices (HID), like mice, joysticks or do-it-yourself usb thingies that follow the HID specification.
iCE	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='82' Dspaudio, Inc.	Sequencing, Recording and Interface Building for Max/MSP
jb.utilities	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='121'Joseph Branciforte	A set of 50 abstractions for performing both common and awkward tasks in Max/MSP. Categories include control, data, list processing, numbers, pattr-family, statistics, strings, and user-interface. Most perform multiple related functions and are unbiased as to data type where possible. Additionally, the download contains help files.
MaxAlea	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='96'Carl Faia	MaxAlea contains various objects for random distributions and functions. MaxAlea was begun as a Max port of an existing PatchWork Library created in 1991-2 by Mikhail Malt. While the distributions and functions found in MaxAlea are similar to those found in the Patchwork version ,there are many differences in their functioning. The environment of Patchwork is static and is not designed for real-time work. Part of the incentive for creating these objects to work with Max was to have a dynamic and real-time environment with which to experiment and work with these algorithms in a manner as simple and straightforward as possible. One can change variables and manipulate the output in many ways in real-time. There are several different versions of the various stochastic models/processes best presented in the now classic references by Denis Lorrain and Charles Dodge. Carl Faia has used a variety of sources for the creation of this library which include the Lorrain, Dodge and Malt implementations as well as sources found on the WorldWideWeb. The externals found in the package include several random distributions, examples of random walks and 1/f noise algorithms, as well as one or two utilities written specifically for the MaxAlea library. Carl Faia wanted to make a coherent collection (as he thought Malt had managed to do in PatchWork) of these various algorithms and provide an interface easily accessible using the Max environment for real-time control. All these algorithms have been created using a seeded version of the random function found in the standard AINSI library. That is, each time the function is first run there will always be a different set of random numbers (unlike the random funtions found in Max, PatchWork and other versions of random number generators).
p.jit.gl.tools	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='123' Pelado	the p.jit.gl tools are designed to provide for easier learning of and experimenting with the many attributes that are available to jitter's gl objects by making them a whole lot more transparent and accessible. patches expose jitter gl object's attributes to interfaces that allow you to immediately edit and change an attribute's value. many of the parameters are attached to blines, which provide smooth changes while rendering, and all settings can be saved and recalled as presets using the pattrs that are embedded in the patches.
suivi	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='88' Ircam	Two externals performing score following on soloist performances using Hidden Markov Models (HMM) Suivi is based on FTM and requires the shared library FTMlib for Max/MSP. Both externals use an FTM track object - a sequence of time-tagged FTM values - to store the score of the soloist performance to be followed. Notes, trills and other elements of the score are represented by FTM score objects (FTM scoob class). For the moment, scores can be imported from standard MIDI files only. An editor for the FTM track class, which will also provide a graphical control interface for the score follower is under development as well as the import of MusicXML files. The suivi object set is distributed within the IRCAM Forum.
tapemovie	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='144'Tom Mays Olivier Pfeiffer Renaud Rubiano	tapemovie is a modular software environment for controlling, processing, and analyzing various media in realtime (sound, video, 3D, lighting). It has stood the test of numerous productions since 2007, for theater, dance, concert performance and installation - enabling precise control and sequencing of media and their interactions while at the same time allowing connections with multiple peripheral controllers and interfaces. It is programmed with Max/MSP/Jitter and exists as a standalone application (free download), as well as in patch version for advanced users.
v001	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='106'--/// Vade	v001 is meant to help bring a structured method for building modular and reusable performance patches for Max/MSP and Jitter - it isnt a complete low level programming system, rather an immediately useful set of pre-made objects and patching methodologies for building modules and automatically creating dynamic and scriptable user interfaces.