Objects			page : 1
bbcomment.js	Javascript (jsui)		pseudo-BBcode comment object an extened comment object implemented using jsui enabling pseudo-BBcode scripting for text layout. Updated, in particular to enable color changes.
comment	External		Text comment in a Patcher Comments have no function except to label or explain things in a Patcher. You can change the font and/or size of a comment with the Font menu.
ep.binSpat~	Abstraction		handles binaural spatialization for use with headphones through the use of hrtf's. ep.binSpat~ version 0.16 29-03-2006 ep.binSpat~ is an msp object (abstraction) that handles binaural spatialization for use with headphones through the use of hrtf's. It can virtualy position a monoaural source on a horizontal plane 360 degrees around the listeners head by dynamic control of two parameters: direction and distance. It doesn't control vertical positioning. Thanx to soundHack for sampling the HRIR's. Some theory info: http://interface.cipic.ucdavis.edu/CIL_tutorial/3D_HRTF/3D_HRTF.htm Only tested on OSX 10.4.4 with MaxMSP version 4.5.6. Heard from others that it works on OS9 and Windows XP too, though. download at http://www.eude.nl/maxmsp please send comments/reactions to: edo@eude.nl
oddfm~	Abstraction		an odd use of the tap object for frequency modulation goodness. the patch is in the detailed description. max v2; #N vpatcher 123 44 330 267; #P window setfont "Sans Serif" 9.; #P newex 63 79 31 196617 +~ 1; #N comlet out~; #P outlet 10 178 15 0; #N comlet index (signal/float); #P inlet 129 45 15 0; #P newex 63 115 27 196617 *~; #N comlet modulator ~; #P inlet 63 45 15 0; #N comlet carrier ~; #P inlet 10 45 15 0; #P newex 10 140 44 196617 tapout~; #P newex 10 79 38 196617 tapin~; #P comment 10 27 44 196617 carrier; #P comment 63 27 53 196617 modulator; #P comment 129 27 43 196617 index!; #P comment 74 157 100 196617 cheap and delicious!; #P connect 6 0 4 0; #P connect 4 0 5 0; #P fasten 8 0 5 0 68 136 15 136; #P connect 5 0 10 0; #P connect 7 0 11 0; #P connect 11 0 8 0; #P fasten 9 0 8 1 134 102 85 102; #P pop;
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