Manage polyphony/DSP for patchers Use the poly~ to encapsulate a patcher inside an object box, to specify the patcher filename and the number of instances you want to load as arguments to the poly~ object, and to control object processing and routing in the loaded patcher instances. Cycling '74 MSP MSP Polyphony Input 1 of TEXT_HERE Input 2 of TEXT_HERE Name of a patcher to be loaded The first argument must specify the name of a patcher to be loaded which already exists and is in the Max search path. A subpatch window is not automatically opened for editing when a patcher argument is supplied for the poly~ object. Number of patcher instances to be loaded The number of patcher instances corresponds to the number of available "voices" This number can be any number between 1 and 1023, and may be dynamically changed by using the voices message. Enable local DSP scheduling With local set to 1, the poly~ object maintains its own scheduler that runs during its audio processing rather than using the global Max scheduler, allowing finer resolution for events generated by multiple patcher instances. The local scheduler is run immediately before processing a vector of audio, as if "Scheduler in Audio Interrupt" were on within the context of the poly~ object. Local scheduling is disabled by default - Scheduler locality is permanent for any patcher which is loaded, and cannot be changed by sending messages to the poly~ object. Enable local upsampling Use the up argument followed by a number which is a power of two to upsample local DSP processing on the currently loaded patcher (e.g., up 2 specifies 88200 Hz at a sampling rate of 44100 Hz). Upsampling may be dynamically changed by using the up message. Enable local downsampling Use the down argument followed by a number which is a power of two to downsample local DSP processing on the currently loaded patcher (e.g., down 2 specifies 22050 Hz at a sampling rate of 44100 Hz). Downsampling may be dynamically changed by using the down message. Initialize argument values Use the argument args followed by an argument value to initialize any pound-sign arguments in the loaded patcher (e.g., args #1). If used, the args argument must be the last argument word used; everything which appears after the word args will be treated as an argument value. Send a bang to the patcher loaded into the poly object. Sends a bang to the patcher loaded into the poly object. The result of the message is determined by the loaded patcher. Perform patcher-specific functions Performs functions which are specific to the user-designed poly~ patcher itself. Perform patcher-specific functions Performs functions which are specific to the user-designed poly~ patcher itself. Send a list to a poly instance To send a message to a poly~ instance that starts with one of the words used to control the poly~ object itself, begin the message with the word list. For example, the message list target 2 sent to the left inlet of poly~ will output target 2 out the outlet of all in 1 objects, rather than changing the current target instance to the second patcher. TEXT HERE The number of inlets and outlets for poly~ is determined by the patcher that is loaded. The inlets for the patcher loaded by a poly~ object accept both signal and event connections.

The signals are routed inside of the loaded patcher by using the in~ objects for signals or the in object for events. The number of total inlets in a poly~ object is determined by the highest number of an in~ or in object in the loaded patcher (e.g., if there is an in~ with argument 3 and an in with argument 4, the poly~ object will have four inlets. All the inlets accept signal connections even though there may not be an in~ object corresponding to each inlet.

Signal inputs are fed to all instances. Load a file when dragging a patch from the Max File Browser Loads a file when dragging a patch from the Max File Browser to a poly~ object. Disable all currently playing notes Disables all playing notes by sending a message to each instance with a playing note consisting of the MIDI pitch most recently received via the note or midinote message followed by a zero velocity (note off message). Report voice busy states Reports the voice busy state for the number specified as the argument out the specified message outlet of the poly~ object. Open a display window to view loaded patch contents Double-clicking on the poly~ opens a display window where you can view the contents of a loaded patcher. Downsample the audio on the currently loaded patcher Use the up argument followed by a number which is a power of two to downsample local DSP processing on the currently loaded patcher (e.g., down 2 specifies 22050 Hz at a sampling rate of 44100 Hz). Downsampling may be dynamically changed by using the down message. Although both up and down are permissible messages to the poly~ object, the down message takes precedence over up. Exclude a voice from note allocation Sending the word exclude, followed by a voice number and a one, prevents a poly~ instance from being sent messages via note allocation when the poly~ receives a note or midinote message. By default, all voices are enabled for note allocation. The word exclude, followed by a voice number and a zero re-enables the instance to receive messages when the poly~ receives a note or midinote message. Send a MIDI event to a poly~ voice The word midievent, followed by two to four numbers, sends a MIDI event to poly~. The first three number arguments are the bytes of the MIDI message. The fourth, optional, argument is a detune parameter used for MIDI note messages. midievent messages are intended to be used with the polymidiin object. Mute processing for a patcher instance Turns off signal processing for the specified instance of of a patcher loaded by the poly~ object and sends a bang message to the thispoly~ object for the specified instance. Sending a 0 as the second argument turns the patcher instance on. The message mute 0 1 mutes all instances, and mute 0 0 turns on signal processing for all instances of the patcher. If all are muted using a mute 0 1 message, individual instances cannot be unmuted until all are unmuted with a mute 0 0 message. Open a patcher instance for viewing The word open, followed by a number, opens the specified instance of the patcher. You can view the activity of any instance of the patcher up to the number of voices (set by the voices message or by an argument to the poly~ object). With no arguments, the open message opens the instance that is currently the target (see the target message). Send data to an available voice instance The word note, followed by a message, will send the data to the first in object of the first instance of the patcher that has not marked itself "busy" by sending a 1 to a thispoly~ object inside the patcher instance. Send a MIDI note event or list of values to a poly~ instance The midinote message is followed by two or more values. While note values are ordinarily two numbers that specify a MIDI note number and a velocity value, any numbers may be used for patches which work differently than the standard MIDI model.

If the second note value is not 0, the poly~ object routes the pitch velocity to the first available instance. If the velocity is 0 (i.e. a MIDI note-off message), the pitch velocity will be sent to the poly~ instance that generated the note. To determine which instance of the loaded patcher the midinote message will be sent to, send a 0 (non-busy) or 1 (busy) message to a thispoly~ object located in the loaded patcher. Report voice mutes out of a specified poly~ message outlet Send an individual note control message The notemessage message is used to send messages to each active voice (i.e. an individual instances of a subpatcher loaded by the poly~ object). The message is sent directly to the poly~ object by means of in objects (When addressing a poly~ object, the first in object in the subpatcher is reserved for midinote messages). Sequentially, notemessage messages follow a note message - the first argument of that message being taken as a pitch for the ID of subsequent notemessage messages. The notemessage messages can be of arbitrary length, and may be unpacked and routed inside the subpatcher. In situations where a note-off message that involves a time duration before its completion (e.g. by the use of an adsr~ object), notemessage messages will be received for processing until the voice is turned off.

Note: The only way to turn a voice off properly when using a notemessage is to use a signal to a thispoly~ object in the subpatcher loaded by the poly~ object (if a signal is not connected to the thispoly~ object , the MIDI note-off message turns off the voice assignment immediately). MPE Event Message The MPE event message is a list composed of the symbol mpeevent, followed by 6 integers which specify the Zone First Channel, Zone Index, Voice Number, Channel Number, MIDI Message Number, and Data. This message can be sent to a patch encapsulated in a poly~ object using the polymidiin object. Upsample the audio on the currently loaded patcher Use the up argument followed by a number which is a power of two to upsample local DSP processing on the currently loaded patcher (e.g., up 2 specifies 88200 Hz at a sampling rate of 44100 Hz). Upsampling may be dynamically changed by using the up message. Although both up and down are permissible messages to the poly~ object, the down message takes precedence over up. Set the number of threads used to divide poly~ instances' audio processing The word threadcount, followed by a number, sets the number of threads used to divide poly~ instances' audio processing. The default is the number of processor cores available in your computer. Typically, the number of threads should be set to the number of processor cores in your computer for best performance. This can also be accomplished by sending the message threadcount 0. If a poly~ object has sixteen instances and the threadcount is 4, four of the poly~ instances will process audio in each of four threads. Close a numbered patcher instance's window Closes the window for the numbered instance specified by the argument. If no number argument is used, wclose will close the patcher window with the highest numbered index. Arguments for the Loaded Patch When using messages to specifie arguments for a poly~ object's loaded patch, the patch must be reloaded by setting the patchername attribute for new arguments to take effect after initial load. Send MIDI Events to All Voices When midimode is set to '1', all MIDI messages sent to poly~ will be sent to all voices. Note that this does not apply to mpeevent messages. In order to send all mpeevent messages to all voices, use a '-1' value for the voice argument, eg: 'mpeevent 1 1 2 210 117' (an aftertouch message to all voices). Use MPE Channel as Voice When this attribute is set to '1', poly~ will perform direct voice allocation based on the voice argument of an mpeevent message. Parallel Processing Toggle When this attribute is set to enable parallel processing, the poly~ object enables the use of multiple threads to run audio processing for all patcher instances. If disabled poly~ runs all patcher instances in the audio processing thread. The DSP chain must be restarted whenever the parallel attribute is changed. This attribute is disabled it when Max is hosted by the Live application.

Note: At this time, you cannot specify a single subpatcher on a different core. When enabled, this attribute splits up the number of voices between the number of processors available. It is primarily intended for patches that use a significant amount of CPU within multiple voices of the same poly~ object, and the multithreading overhead is primarily useful for larger signal vector sizes (at least 32 or greater). Other situations will not benefit. Using the default threadcount (which is equal to the number of physical cores) is best. Patcher File The filename of a patcher file loaded into the poly~ object. Use Resampling Filters Toggles the use of high-quality resampling filters. These filters are enabled by default. Voice Stealing Enable Voice stealing enable causes the poly~ object sends the data from the note or midinote messages to instances that are still marked "busy"; this can result in clicks depending on how the instances handle the interruption. Voice stealing is disabled by default. Target Voice Number The poly~ instance that will receive subsequent messages (other than messages specifically used by the poly~ object itself) arriving at the poly~ object's inlets - for example, The message target 2 routes messages to the second instance. If the target message specifies a value greater than the current number of instances (copies) of the loaded patcher, the message will be sent to the highest numbered instance (e.g., sending the message target 2 to a poly~ object containing only a single instance will send subsequent messages to the first instance). The message target 0 sends input to all instances, and using any negative number value with the target message will disable input to all instances. Number of Voices Signal Vector Size for the Loaded Patch Specifies the signal vector size for the poly~ object's loaded patch. The signal vector size will be set on the next compilation of the DSP chain. The vs message does not force a recompilation of the DSP chain. vs 0 specifies no fixed vector size. The default is the current signal vector size. MPE Zone Select Use this attribute to set the MPE 'zone' that the poly~ will listen to. The default is '0' (ignore zones). The poly~ object directs signals and events (messages) received in its inlets to in and in~ objects inside patcher instances, and handles the output of signals or events from instances of the poly~ object using the out and out~ objects. The number of outlets of a poly~ object is determined by the sum of the highest argument numbers of the out and out~ objects in the loaded patcher. For instance, if there is an out 3 object and an out~ 2 object, the poly~ object will have five outlets. The signal outputs corresponding to the out~ objects are leftmost in the poly~ object, followed by the event outlets corresponding to the out objects.

Signals sent to the inlet of out~ objects in each patcher instance are mixed if there is more than one instance and appear at the corresponding outlets of the poly~ object.