Objects			page : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
St.end	Abstraction		A send with changeable destination. But best of all, if a second parameter is set, it will send to this number of named objects when connected to thispatcher, or if the second parameter is a symbol it will compose the destination out of the two parameters.
St.Noteout	Abstraction		A noteout which allows to send the data also to my samplers inside Max.
St.S	Abstraction		alternate send.
St.SampleBuffer~	Abstraction		Used by the St.Buffers abstraction and sends automatically the info about the loaded sample to 'SoundnameInfo' and to the outlet.
St.Unselct	Abstraction		Helps to get around the annoying problem of a focus on an object stealing keypresses an alike. Send anything to St.Unselect and it will switch of the focus after the time set by its parameter. A bang will deselect immediatly. The time can also be set with the right inlet. The output has to be connected to a thispatcher object.
sxformat	External		Format a system-exclusive MIDI message using expr sxformat can make it easier to send system-exclusive parameter change messages. It takes as arguments a list of numbers which are sent out sequentially. In addition, you may use one or more "expr"-style statements, which start with the word "is", which will be evaluated, with the result being sent out. "is" statements need to be separated by slashes. The format of sxformat arguments is similar to statements in a "lib" object script.
sync~	External		Synchronization from tap tempo, MIDI beat clock or audio click tracks. sync~ outputs a 0-1 ramp, like phasor~. The frequency of the ramp can be specified in beats per minute (BPM), or by sending sync~ a tempo reference via tap tempo, MIDI beat clock, or an audio signal containing a 'click track.' Also, sync~ generates MIDI beat clock to synchronize external devices.
tap.auto_thru~	External		Signal Routing Utility automatic switch Essentially an automatic switch, tap.auto_thru~ sends the first inlet's signal thru to the output unless the second inlet has a signal connected to it. If a signal is connected to the 2nd inlet, the first inlet is cut off.
tcpClient atp	Javaclass (mxj)		communicate back and forth over a single persistent TCP/IP socket A Max object written in java (using mxj) to communicate back and forth over a single persistent TCP/IP socket with a TCP/IP server, something the net.tcp objects that ship with Max can't do. Opens a socket, then sends and receives info without closing it. Closes the socket only when you tell it to, or when the server disconnects (ie from inactivity). Useful for connecting to simple hardware network devices like EZ Web Lynx and other microcontrollers/DSPs that don't easily support something nicer like OSC, or any TCP Protocol that sends data back on the same socket. Tested on MaxOS X 10.5 and Windows XP, Max/MSP 5.1.x Developed by Arvid Tomayko-Peters for Your Heaven, LLC™ Thanks to David Reilly for his TimedSocket class.
TeaBoxBridge	Standalone Application		Teabox Bridge application for sending Teabox input out as MIDI or OpenSoundControl Teabox Bridge application for sending Teabox input out as MIDI or OpenSoundControl
thisobject	External		Send messages to a patcher, communicate with an object in an inspector The thisobject object is used inside inspector patches to communicate with the object being edited. It allows you to get the object's current state and send messages modifying the state.
thispatcher	External		Send messages to a patcher thispatcher can be used to modify and/or close a patcher window. It sends a message to the patcher window in which it is contained. The messages currently accepted by patchers are shown below. In addition, you can look at any Max patcher document as text and copy the format for sending messages to "#P" and create new objects and connections right in the window under program control! Also see the bpatcher help file for the use of thispatcher with bpatcher.
thisTimeline	External		Send messages to a timeline Send control messages to the timeline object from within an action patcher
thisTrack	External		Send messages to a timeline track Send control messages to a timeline track object from within an action patcher
tiCmd	External		Interface between the timeline and its action patchers The tiCmd object receives messages from the timeline and passes them to a patcher which is serving as an action. It is analogous to an inlet object (but note that inlet objects do not work with the timeline). It takes the following arguments: first, a message selector which is a symbol that serves to identify the tiCmd object. The selector is followed by any number of arguments that to specify the expected types in the message. Each type specifier argument produces an outlet in the tiCmd object. If a type in the message contained in the timeline is different than what is specified in the tiCmd object, tiCmd tries to convert it. If it doesn't exist, there will be no output at the corresponding outlet. In addition, there are two outlets which send the message bang, the leftmost (triggered after the argument outlets have fired) and the rightmost (triggered when time passes the right edge of the message box in the timeline track).
page : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Libraries
lh_midi objects	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='151'Leigh Hunt	These objects can be utilised to send and receive all types of midi data to and from a max4live device.