Objects			page : 1 2 3 4 5 6 7
op.recognize	Javaclass (mxj)		Speech recognition and segmentation. Recognize is a speech to text based on Sphinx4. It translates the incoming audio signal into text and can give dates of words and phonemes in a buffer~. Uses JSGF grammar file and ngram model languages. No special voic
p.jit.gl.texture	Abstraction		wrapper for jit.gl.texture
psw.textdisplay	External		displays a text in a separate window
psw.utextlist	External		a textlist editor
reanimator~	External		an audio texture mapper
rezumai	Javaclass (mxj)		Natural Language Processing. Speech tagging, automatic text summarizer, html, doc and pdf parser, text "explainer". Summarization, categorization, key phrase generation, part of speech tagging, anaphora resolution (i.e., matches proper names with pronouns), identification of place and human names, and sentence boundary detection. - Uses bayesian classifier from Classifier4J (Version 0.6) - Uses Natural Language Processing KBtextmaster (Version 2.0)
rs.textbutton	External		a button/toggle with text
rst	Abstraction		Filter for symbol and text...
sadam.base64	External		Base64 encoder & unencoder object. sadam.base64 will encode and unencode any message you send it (actually it takes into consideration only the first element of the message if the message has multiple elements). Since the base64 encoding contains only alphanumerical characters and a few symbols (which are: +, / and =), the encoded string can safely be used outside the native Max world (for example, with MXJ or in text files). Combined with sadam.lzo it can be used to safely transmit huge amount of data over network using for example the MXJ-based jit.net.send object, or for storing (originally) binary data in an external text file.
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.
searchtweet	Javaclass (mxj)		Returns a specified number of most recent twitter posts that contain a given keyword, #hashtag, or @usertag. Searchtweet.class is a mxj external that searches Twitter with a given keyword and returns a desired maximum number of most recent posts, with username, date and twitter text body routed to separate outlets. Searchtweet uses twitter4j library (http://twitter4j.org) programmed by Yusuke Yamamoto.
SpeakTest	Javaclass (mxj)		The SpeakTest class "reads" the text provided by the setText message. In this example the java class SpeakTest provides control information for up to eight oscillators based on the test it is provided with.
speech	External		speaking a text
page : 1 2 3 4 5 6 7

Libraries
FFTexternals	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='3'Nathan Wolek	A small collection of externals used for various spectral processing. Includes objects for computing amplitude in decibels and a few complex math functions.
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
loadbang.net SQL	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='99'Nick Rothwell	A Java library for communicating with SQL databases from MXJ. We currently support MySQL and HSQLDB. The HSQLDB system includes an embedded database instance, so it runs automatically from text files in Max\'s search path; no external database server configuration is necessary.
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;