Objects			page : 1 2 3
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.prime	External		Compute the closest prime numbers to a positive integer. sadam.prime will compute the closest prime numbers to the absolute value of any integer input. It also reports whether the absolute value of the input is a prime or not. Since the smallest prime number is 2, if the absolute value of the input is smaller than 2, the outlet reporting the closest smaller prime will give false results (it reports the absolute value of the input). The object uses an internal prime table to compute the primes which can be printed to the Max window.
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.
SDIF-buffer	External		Store an SDIF stream in Max This object is described by the paper "Supporting the Sound Description Interchange Format in the Max/MSP Environment", which you can find here: http://www.cnmat.berkeley.edu/ICMC99
sdif.pagsemble~	External		PAGS, pitch aligned granular synthesis of a voice group The PAGS resynthesis objects where originally developed in jMax for a virtual choir in Philippe Manoury's opera K... A first porting to Max/MSP was done by Serge Lemouton. Both objects perform resynthesis of PSOLA analysis files in SDIF format (1PSO) containing markers with voiced/unvoiced parameters and require the SDIF-buffer external from CNMAT : http://www.cnmat.berkeley.edu. Distribution/licence: IRCAM Forum
sdif.pagsolo~	External		PAGS, pitch aligned granular synthesis of a single voice. The PAGS resynthesis objects where originally developed in jMax for a virtual choir in Philippe Manoury's opera K... A first porting to Max/MSP was done by Serge Lemouton. Both objects perform resynthesis of PSOLA analysis files in SDIF format (1PSO) containing markers with voiced/unvoiced parameters and require the SDIF-buffer external from CNMAT : http://www.cnmat.berkeley.edu Distribution/licence: IRCAM Forum
tl.vst.helper	Abstraction		GUI helper for vst~. Incorporates common messages (plug, bypass, etc.), a simple way of polling and dumping all parameters for storage in embedded coll file, pattr implementation as list of all parameters (max 256) and reporting changes to single parameters.
v.bounds	External		v.bounds calculates the bounding rectangle of the non-black areas of the image. v.bounds calculates the bounding rectangle of the non-black areas of the image. It has some features to improve its performance where there might be bits of noise outside the area of maximum concentration. v.bounds finds the top- and bottom-most lines and left- and right-most columns such that noise_tolerance amount of the image mass is outside the defined bounds. In other words, if noise_tolerance is 0.1, then the starting value for the top will be the line in which the accumulated total of pixel values becomes larger than 0.1 times the total sum of all pixel values in the image. From this initial bounding rectangle, v.bounds works backwards, expanding to include consecutive lines or columns which have at least noise_threshold total pixel value. This tends t
page : 1 2 3

Libraries
DIPS5v1.01	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='171'Development Group Dips Shu Matsuda Takayuki Rai	DIPS (Digital Image Processing with Sound) is a plug-in software for Max. DIPS, consisting of more than 370 Max external and abstracts objects, is a powerful and user-friendly tool for the creation of interactive multimedia art, supporting interaction between sound events and visual events in Max, using Apple’s Core Image technology as well as OpenGL and OpenCV technologies. DIPS5v1.01 is the most recent release (Oct. 2013) and available from http://dips.kcm-sd.ac.jp . DIPS Development Group T.Rai/S.Matsuda/Y.Morimoto/T.Fukuda/K.Takahashi
LFO Quaternion Objects	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='124'Evan Raskob	Free externals for using and converting Quaternions in Max/MSP/Jitter. Includes source code as XCode project, BSD license.
SuperCollider Compatibility Lib	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='25'Timothy Place	A package of objects to make porting SuperCollider patches to Max/MSP easier... (ca. 2001)