Objects			page : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Rreceive	External		receives Max messages from another machine
rs.delos	External		GUI timeline object rs.delos, sort of a crossbreed of the pre-Max5 timeline object with a pianoroll style Midi editor, lets you put events in a timeline and send them out synchronized to a transport object. Each event acts as a container for: - pitch/velocity and duration information, - user definable parameters, - user definable breakpoint functions, - MSP buffer display, - any arbitrary message.
Rsend	External		remote send and receive sends Max messages from one machine to another
rtin	External		Output incoming MIDI real-time bytes Output received MIDI real time messages
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.lzo	External		Loseless data compression and decompression using the LZO library. sadam.lzo will compress and decompress loselessly any arbitrary message you send it. The behaviour (compressor/decompressor) is set by the first argument. The compressed result is a single message that may contain any ASCII value (except 0), so caution should be taken, specially if the result is used outside the native Max world (for example if you pass it to MXJ or you plan to store it in a file on the file system). For these cases you might find useful to encode the result with sadam.base64.
sadam.mutex	External		Mutual exclusion (semaphore) object. sadam.mutex will help you managing the access of shared resources in your patch using semaphores. A semaphore can be locked and released, and while locked, it will prevent messages from passing through. Each semaphore must have an unique name, and instances of sadam.mutex with the same name will access the same semaphore. Each mutex has two modes, they can be either locker or releaser instances to the same semaphore. A locker object will test for each incoming message whether the semaphore is locked and if not, it will lock the semaphore and pass the message to the appropriate outlet. Releaser objects will release the semaphore each time a message arrives to their inlet.
sadam.tcpClient	External		Bidirectional TCP client. sadam.tcpClient will open a TCP connection to a specified IPv4 address on a specified port and will send and receive arbitrary information through this connection. Currently it is only able to manage binary data (either by sending bytes directly to the object or by registering it to a binary stream represented by sadam.stream) but in a later release it will support any arbitrary Max message.
sadam.tcpReceiver	External		Receive data from the network using the TCP protocol. sadam.tcpReceiver will listen to a specified port and output incoming data. Currently it will output everything as pure binary data (by sending out the received bytes one-by-one on the leftmost outlet and, optionally, by adding them to the registered binary streams represented by sadam.stream) but a later release will support any arbitrary Max message.
sadam.tcpSender	External		Send data through the network using the TCP protocol. sadam.tcpSender will send data to a specified IPv4 address on a specified port. Currently it is only able to send binary data (either by sending bytes directly to the object or by registering it to a binary stream represented by sadam.stream) but in a later release it will support any arbitrary Max message. The connection is not kept alive, instead, it is opened each time a message is being sent and closed just afterwards. This makes sure that the underlying operating system would send the messages instantaneously.
sadam.udpReceiver	External		Receive data from the network using the UDP protocol. sadam.udpReceiver will listen to a specified port and output incoming data. Currently it will output everything as pure binary data (by sending out the received bytes one-by-one on the leftmost outlet and, optionally, by adding them to the registered binary streams represented by sadam.stream) but a later release will support any arbitrary Max message.
sadam.udpSender	External		Send data through the network using the UDP protocol. sadam.udpSender will send data to a specified IPv4 address on a specified port. Currently it is only able to send binary data (either by sending bytes directly to the object or by registering it to a binary stream represented by sadam.stream) but in a later release it will support any arbitrary Max message.
selX	External		An enhanced “sel” object, An enhanced “sel” object, with the capacity for more arguments, and the fact that you can change any or all of them on the fly with messages.  Furthermore, it can bang (like sel), or send the items themselves.
send	External		Send messages without patch cords The send and receive objects allow you to send any kind of message between Patcher windows or within a window without using patch cords. The order of reception by two or more receive objects is not deterministic.
send~	External		Send a signal without a patch cord Send a signal without a patch cord. send~ lets you send a signal to another patcher window or to another location within the same patcher window without using a patch cord. In addition, the destination of the signal can be changed on the fly using the set message. A receive~ object with the same name receives the output of send~. Note that if two or more send~ objects are aimed at the same receive~, the signals add together (you can hear this in the example below).
page : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Libraries
boids	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='112' Jasch Sier Eric Singer Wesley Smith	Based on Simon Fraser's implementation of Craig Reynolds' Boids algorithm. Boids is free for non-commercial use. Boids is a bird flight and animal flock simulator. It is based on the same algorithm which was used in Jurassic Park for the herding dinosaurs. Boids takes an integer argument which is the number of boids. Each time Boids receives a bang, it calculates and outputs the new positions of the boids. The output consists of thew coordiantes for each boid, the number and type depending on the mode. The flight parameters can be changed with messages. Use the 'dump' message to output a list of the current parameter settings. For more information about the Boids algorithm, see Craig Reynolds' Web site at "http://reality.sgi.com/employees/craig/boids.html".
BulkStore	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='62'Tom Mays	bulk storage memory device for all values (any message)
Optimized Gates	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='34'Stephen Kay	7 different optimized gates ("bgate" for bangs, "igate" for ints, "fgate" for floats, "sgate" for symbols, and "lgate" for lists. These do not need to do a message lookup, since they only deal with one data type. Also includes "andGate" and "orGate" by David Roach)
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.