Objects			page : 1 2 3 4 5 6 7
Multiple Module Coll Memory System	Patch		An example patcher (tutorial) showing a system for collecting the data from many UI objects in different patchers or bpatchers (“Multiple Modules“) into a single coll file as a program of several lines. An example patcher (tutorial) showing a system for collecting the data from many UI objects in different patchers or bpatchers (“Multiple Modules“) into a single coll file as a program of several lines. Each program can have a name, which appears in a popup menu of all the names for various programs. Programs may be saved, cleared, or entered, sending the various stored values for display in the correct UI objects in the various modules. The entire master coll file can be written to or read from disk, thereby allowing the user to save a complete “bank” of programs. Unlike use of the preset object, your data file can be edited as text, and adding/removing UI objects from the modules as your application grows is far easier than trying to do that with a preset object (which usually stops working after awhile).
mute1~	Abstraction		fade out This abstraction is not to be confused with the standard MSP external object mute~, as the two objects serve different purposes. Back in the early days of MAX/FTS on the ISPW, mute1~ was created as a way to quickly fade out a portion of the signal chain, without causing clicks. Unfortunately, its name is very similar to that of the mute~ object in MSP, which is designed to brutally switch on and off the DSP calculations within sub-patchers.
mute~	External		Disable signal objects in a patcher mute~ provides an easy way to disable only the signal objects in a subpatcher. An alternative is to use pcontrol as shown below, but this disables all objects (i.e. MIDI) and is slightly slower.
mw.lcdrangebar	External		an lcd-based bpatcher which performs a similar function to Max\'s built-in rangebar. This one has some nifty features which the (ageing) rangebar lacks.
namedobjs	External		retrieve named objects in a patcher
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;
onecopy	External		Prevent multiple copies of the same patcher from being opened in the Extras menu
out	External		Define a message output in a patcher loaded by poly~
out~	External		Define a signal output in a patcher loaded by poly~
pass~	External		Elminate noise when listening to a muted subpatcher Elminate noise when listening to a muted subpatcher. Use pass~ before the outputs of a subpatcher you intend to mute. When the subpatcher is disabled using mute~, the pass~ object outputs a zero signal. Otherwise it passes the input to the output. If pass~ isn't used, the output of a muted subpatcher could be any signal, even one making unwelcome noise, because the function of mute~ is not to zero the volume of the output but to eliminate the DSP processing (and therefore the CPU utilization) of the subpatcher. An alternative to using pass~ would be to put a volume control on the output that is set to zero when the subpatcher is muted.
patcher	External		create a sub-patch You can embed a Patcher in another one with a "Patcher" box, as above. The inlets and outlets on the box correspond to the inlet and outlet boxes in the embedded Patcher. You can close the embedded window by clicking in its close box and reopen it by double-clicking the Patcher box below.
patcherargs	External		Get parent patcher arguments The patcherargs object outputs the parent patcher's arguments when a patcher is loaded. "Normal" arguments are sent as a list out the left outlet, while attribute style arguments are parsed and sent out as a series of lists out the right outlet. The patcherargs object accepts additional arguments which will be used in the event that the parent patcher has no arguments.
patcherargs	External		Get parent patcher arguments.
patcheroute	Abstraction		Aid for dealing with patcherargs.
pattr	External		Patcher-specific, named data wrapper. The pattr object can be thought of as an ALIAS for data.
page : 1 2 3 4 5 6 7

Libraries
MegaMax	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='35'Stephen Kay	The MegaMAX™ Collection is a set of 33 external objects for use with Opcode's MAX programming environment. It was created by professional musician and programmer Stephen Kay in an effort to deal with some of the frustrations and limitations of creating a professional looking, feeling and functioning application. But you don't have to be an application developer! The MegaMAX Collection is for anyone who wants to make better-looking and functioning Max patchers at all levels.
QuickStart	debug: SELECT prenom, nom FROM auteurs RIGHT JOIN auteur_libraries USING (id_auteur) WHERE auteur_libraries.id_library='24'Darwin Grosse	A bunch of abstractions and bpatchers that provide useful tools for both beginning and experienced Max/MSP developers.