Objects			page : 1 2 3 4 5
reson~	External		Bandpass filter controllable by center frequency and Q Bandpass filter controllable by center frequency and Q. reson~ implements the following filter equation: y[n] = gain * (x[n] - r * x[n-2]) + c1 * y[n-1] + c2 * y[n-2], where r, c1, and c2 are parameters calculated from the input center frequency and Q. Q is the filter bandwidth divided by center frequency. Inputs can be floats or signals. The specification is similar to the nres unit generator in cmusic.
rms1~	Abstraction		measures the average amplitude of a signal rms1~ is a measure of the average amplitude of a signal using the RMS (root-meansquare) method. Although MSP already has an amplitude level peak meter (meter~) it is not as useful for amplitude or envelope following as rms1~.
s2m.envfollow~	External		simple enveloppe follower s2m.envfollow~ is a simple enveloppe follower, based on an algorithm given in chapter 7 of U. Zölzer's book "Digital Audio signal Processing". See the help patch for detail.
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.
sadam.rapidXML	External		A RapidXML wrapper for Max. sadam.rapidXML 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 RapidXML 1.13 library (see http://rapidxml.sourceforge.net/,) which is one of the fastest, yet still almost completely W3C compliant, freely available XML parsers. 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. As already mentioned, RapidXML 1.13 (and therefore sadam.rapidXML) is not fully W3C compliant. The main reason is that the parser ignores DOCTYPE declarations. There are also some difficulties with namespace management as well, the parser wouldn't refuse XMLs containing more than one root element and it will allow duplicate attributes for the same element. Also, to make parsing faster, all kind of XML validation is turned off by the wrapper Max object. If you need a 100% W3C compliant XML parser, consider sadam.dom, which is almost identical in functionality to sadam.rapidXML and requires MXJ to run.
slide~	External		Slide filters an input signal logarithmically between changes in signal value. Slide filters an input signal logarithmically between changes in signal value. The formula is y(n) = y(n-1) + ((x(n) - y(n-1))/slide). It's particularly useful for envelope following and lowpass filtering.
smoother	External		First order low-pass/median filter and envelope follower for floats, ints, and lists
swap	External		Swap left and right inlets to outlets Swap swaps the values of its inlets, preserving right-to-left ordering. The first outlets (and second inlets) type follow the argument (or is an int if you give no argument.) The second outlets (and first inlets) type is int or float depending on whether you use the name "swap" or "fswap".
swap	External		Swap left and right inlets to outlets, reverse the sequential order of two numbers Swap swaps the values of its inlets, preserving right-to-left ordering. The first outlets (and second inlets) type follow the argument (or is an int if you give no argument.) The second outlets (and first inlets) type is int or float depending on whether you use the name "swap" or "fswap".
tiCmd	External		Interface between the timeline and its action patchers The tiCmd object receives messages from the timeline and passes them to a patcher which is serving as an action. It is analogous to an inlet object (but note that inlet objects do not work with the timeline). It takes the following arguments: first, a message selector which is a symbol that serves to identify the tiCmd object. The selector is followed by any number of arguments that to specify the expected types in the message. Each type specifier argument produces an outlet in the tiCmd object. If a type in the message contained in the timeline is different than what is specified in the tiCmd object, tiCmd tries to convert it. If it doesn't exist, there will be no output at the corresponding outlet. In addition, there are two outlets which send the message bang, the leftmost (triggered after the argument outlets have fired) and the rightmost (triggered when time passes the right edge of the message box in the timeline track).
tl.envfollow~	External		Envelope following
tm.autofollow	Abstraction		Used to create autofollow cues.
v.bufferpool	External		This object allows you to preallocate buffers of various formats and resolutions to be shared amongst other object. This object allows you to preallocate buffers of various formats and resolutions to be shared amongst other object. Buffer pools can be named or unnamed. Named pools offer their buffers only to objects that have been told to allocate from those pools. Unnamed pools are available to any object without a pool preference. When created, a buffer pool is empty. If an object has declared that it will allocate its buffers from a specific buffer pool and that buffer pool cannot satisfy the request, the object will not try to get the buffers from general memory and the object will bypass itself and send the following message from its outlet: buffer_set_full
v.m.k	Standalone Application		virtual midikeyboard this application lets you simulate a midi keyboard on your computer qwerty keyboard. for laptop-users on the run tired of 'clicking' or 'drawing' their music in midi-sequencers and notation programs. use keys [<] or [>] to change octave and arrow keys left/right for chromatic transposition. the layout is as follows: W E T Y U O P ] A S D F G H J K L ; ' \
v.track	External		v.track follows a specified small object across the video field with sub-pixel accuracy and no delay. v.track follows a specified small object across the video field with sub-pixel accuracy and no delay. Objects are tracked best against a contrasting solid background, and will be lost if they travel faster than 8 pixels per frame. You can also tell v.track to track an unmoving part of the screen, and move the camera (instant steadicam) (Again, if the camera moves such that the image moves more than 8 pixel per frame, you will lose tracking.) If you supply a profile stream (i.e. from v.silhouette’s second outlet), v.track uses the silhouette to define a mask that will cause areas showing no silhouette presence to be ignored in the tracking process, which improves tracking across complicated backgrounds. v.track is best understood by looking at the v.track examples, because it works best when supplied with properly pre-processed streams.
page : 1 2 3 4 5

Libraries
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.
ri.Lorenz MSP objects	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='169'Ryo Ikeshiro	Calculates the Lorenz dynamical system and various modifications at signal rate. Can be controlled by either floats or signal for sample-accurate timing. Currently only available for Mac OS X 10.5 or later (Intel). The following have only been tested on Max 5.
ri.rotatexyz MSP objects	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='170'Ryo Ikeshiro	Calculates 3D coordinates after rotation around the x, y and z axes by performing matrix (mathematical, not Jitter) multiplication at signal rate. Ideal for generating signal rate panning data for use with the rotatexyz message to jit.gl.render. Currently only available for Mac OS X 10.5 or later (Intel). The following have only been tested on Max 5.
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.