Objects			page : 1 2 3 4 5
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.
sadam.sax	Javaclass (mxj)		A Simple API for XML (SAX) interface for Max. sadam.sax will parse XML documents using SAX. The output will be sent out for each Element as a sequence (from right to left) consisting of the Element Index (the number of the Element in the XML), 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: if any error happens during parsing, it returns -1, otherwise it returns 0 after finishing the parsing process. 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.stat	External		Get mean and standard deviation of a number sequence. sadam.stat will compute the mean and the standard deviation of a sequence of numbers. With no arguments it will compute these values using all the numbers it received (like the mean object) while by declaring a fixed buffer size N it will do the calculations only on the last N entries.
scale-changer	Abstraction		scale changer Changes one single pitch of a given scale whenever you send a bang to the left inlet. A start scale must be sent to the right inlet frist - note its special format: a list of size 12 consisting only of 0 and 1 where 1 means an active pitch class and 0 a inactive one.
selector~	External		Switch output among several input signals Switch output among several input signals. The selector~ object is a version of the Max switch object for signals. It takes an argument for number of inputs (one is the default) and lets you turn incoming signals on and off by sending an int to its left inlet. If there is more than one input, selector~ shuts off all inputs except the one you select, where 1 selects the input to the right of the leftmost inlet, 2 selects the next one to the right, etc. selector~ can also control the activation or deactivation of part of a signal processing network. For an example, see the begin~ help file. Note: "shutting off" a signal means disconnecting it from gate's output and outputting a zero signal instead. This is different from the behavior of the Max switch object.
sfa.rmd	External		relative mean difference FTM External
St.LoadIfs	Abstraction		Allows you to mimik the behaviour of externals like noteout or counter which have different meanings for parameters according to the number of parameters.
tap.jit.getattributes	External		assistant for building abstractions This object is meant to assist in building abstractions which mimic the gettable attributes of Jitter externals.
tap.rms~	External		root - mean - square of a signal root-mean-square of a signal
udpreceive	External		Send max messages over the network using UDP. Both udpsend and udpreceive support the 'FullPacket' message used by the CNMAT OpenSoundControl external. This means they can be used as drop in replacements for the [otudp] object.
udpsend	External		Send max messages over the network using UDP. Both udpsend and udpreceive support the 'FullPacket' message used by the CNMAT OpenSoundControl external. This means they can be used as drop in replacements for the [otudp] object.
v.age	External		The output from v.age is an image that indicates the number of frames since each pixel was active (non-zero). The output from v.age is an image that indicates the number of frames since each pixel was active (non-zero). Currently active pixels show how long they have been active by outputting positive values. (32 means active for 32 frames). Inactive pixels output a negative value showing how many frames have elapsed since it was last active. The output image is in floating point format so that it can maintain a very long history. v.age will be paired with another object in development to provide motion speed and direction information.
v.components	External		v.components separates a video stream into its component streams. v.components separates a video stream into its component streams. grays streams produce 3 identical grays streams out the three outlets. N.B. For yuv images, the u and v streams are signed. 0 - 127 are positive values and 128 - 255 are actually -128 to -1. This means the u and v images can look noisier than they really are. (Note that this is different from the pseudo-signed images like those from v.motion (signed mode) where 0 - 127 are really negative and 128 - 255 are positive. To convert a signed int8 stream to a unsigned or pseudo-signed int8 stream or vice versa, you can use a v.xor 128 object.
v.noisegate	External		v.noisegate sets all pixels with brightnesses < noise threshold to zero. v.noisegate sets all pixels with brightnesses < noise threshold to zero. The operation can be set to work on pseudo-signed streams (meaning that 128 is assumed to represent 0, and values that are less than noise threshold away from zero (either above or below) are set to 128
page : 1 2 3 4 5

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
Jitter	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='11' Cycling74	Jitter is a set of 135 brilliant new video, matrix, and 3D graphics objects for the Max graphical programming environment. The Jitter objects extend the functionality of Max4/MSP2 with flexible means to generate and manipulate matrix data -- any data that can be expressed in rows and columns, such as video and still images, 3D geometry, as well as text, spreadsheet data, particle systems, voxels, or audio. Jitter is useful to anyone interested in real-time video processing, custom effects, 2D/3D graphics, audio/visual interaction, data visualization, and analysis
SFA Max/MSP Library	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='172'Stefano Fasciani	The SFA-MaxLib is a collection of Max/MSP objects developed in the context of the VCI4DMI. It includes functions and utilities in the form of FTM externals, FTM abstractions and Max abstractions. FTM is a shared library for Max/MSP developed by IRCAM, which provides a small and simple real-time object system and a set of optimized services to be used within Max/MSP externals. List of FTM Externals: sfa.eig - eigenvalues; sfa.inputcombinations - combination generator; sfa.levinson - levinson-durbin recursion; sfa.lpc2cep - lpc to cepstra conversion; sfa.rastafilt - rasta filter; sfa.rmd - relative mean difference; sfa.roots - polynomial roots; List of Abstractions: sfa.bark.maxpat - energy of the Bark bands from time domain frame;sfa.bark2hz_vect.maxpat - Herts to Bark conversion;sfa.barkspect.maxpat - energy of the Bark bands from spectrum; sfa.ceil.maxpat - ceil function; sfa.featfluxgate.maxpat - gated distance on stream of feature vectors; sfa.fft2barkmx.maxpat - utility sub-abstraction of sfa.bark; sfa.fft2barkmxN.maxpat - utility sub-abstraction of sfa.barkspect; sfa.hynek_eq_coeff.maxpat - hynek equalization coefficients; sfa.hz2bark.maxpat - Hertz to Bark conversion; sfa.hz2bark_vect.maxpat - Hertz to Bark conversion for vectors; sfa.hz2mel.maxpat - Hertz to Mel conversion; sfa.idft_real_coeff.maxpat - utility sub-abstraction of sfa.rasta-plp; sfa.maxminmem.maxpat - minimum and maximum of a stream of data; sfa.mfcc.maxpat - MFCC coefficients; sfa.modalphafilter.maxpat - 1st order IIR lowpass on a stream of vectors; sfa.nonlinfeqscale.maxpat - linear spectrum to Bark or Mel scale conversion; sfa.rasta-plp.maxpat - PLP and RASTA-PLP coefficients; sfa.spectmoments.maxpat - 4 spectral moments (centroid, deviation, skewness, kurtosis); sfa.3spectmoments+flatness.maxpat - 3 spectral moments (centroid, deviation, skewness) and the spectral flatness; sfa.spectralflux.maxpat - spectral flux on stream of spectrum vectors; sfa.spectralfluxgate.maxpat - gated spectral flux on stream of spectrum vectors; sfa.std.maxpat - standard deviation; sfa.win_to_fft_size.maxpat - smaller FFT size given frame size; sfa.GCemulator.maxpat – 3D gestural controller emulator;
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.