Sends a bang to the patcher loaded into the poly object. The result of the message is determined by the loaded patcher.

Performs functions which are specific to the user-designed poly~ patcher itself.

Performs functions which are specific to the user-designed poly~ patcher itself.

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.

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 total number of 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.

Loads a file when dragging a patch from the Max File Browser to a poly~ object.

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).

Reports the voice busy state for the number specified as the argument out the specified message outlet of the poly~ object.

Pass through incoming signals. The first argument specifies the voice, and the second argument specifies the state. To bypass all voices, send the message 'bypass 0 1'.

Double-clicking on the poly~ opens a display window where you can view the contents of a loaded patcher.

Use the down message 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 is not dynamic. DSP must be restarted before the change can take effect. Although both up and down are permissible messages to the poly~ object, the down message takes precedence over up.

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.

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.

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.

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.

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.

Report voice mutes out of a specified poly~ message outlet

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.

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).

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).

The word setvalue, followed by both an instance index (starting at 1) and any message, sends the message to an individual voice of within the MC wrapper. setvalue 0, followed by a message, sends the message to all voices. The setvalue message can be used in any inlet. The instance index specified by setvalue overrides the current value of the target attribute but leaves it unchanged after the message has been sent.

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.

Use the up message 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 is not dynamic. DSP must be restarted before the change can take effect. Although both up and down are permissible messages to the poly~ object, the down message takes precedence over up.

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.