Gary Fitzpatrick

I am creating a polyphonic synth using the poly~ object. Is there any way of editing all instances of the poly at once?

I have a simple FM synth patch built, frequency input,modulation index, amplitude envelope. What i had in mind was being able to open up the patch in a window, change the modulation index for example, and this would then be reflected across all the instances of the patch. Is this possible?

I know i havnt explained this really well but if possible, any help would be greatly appreciated!

Hi!
I am creating a polyphonic synth using the poly~ object. Is there any way of editing all instances of the poly at once?

let me explain a little better.
I have a simple FM synth patch built, frequency input,modulation index, amplitude envelope. What i had in mind was being able to open up the patch in a window, change the modulation index for example, and this would then be reflected across all the instances of the patch. Is this possible?

editing-polys

[send] -> [receive]
or
[send~] -> [receive~]


Quote: Gary Fitzpatrick wrote on Mon, 19 January 2009 13:30

----------------------------------------------------

> I am creating a polyphonic synth using the poly~ object. Is there any way of editing all instances of the poly at once?

Yes. Send the message "target 0" to the left inlet, and then any messages to the poly~ go to all instances.

There's one gotcha though: often people will be using the "note" or "midinote" messages to have poly~ use the next available voice to play a note. As soon as that message is received, whatever voice is selected becomes the active target, so you would have to send "target 0" every time you want to control all instances. I use a [trigger] object to ensure that "target 0" is immediately before any message to control all instances.

IIRC Chris Muir's "StupidSynth" is a good example: 

Quote: Gary Fitzpatrick wrote on Mon, 19 January 2009 13:30
----------------------------------------------------
> I am creating a polyphonic synth using the poly~ object. Is there any way of editing all instances of the poly at once?
>

There's one gotcha though: often people will be using the "note" or "midinote" messages to have poly~ use the next available voice to play a note. As soon as that message is received, whatever voice is selected becomes the active target, so you would have to send "target 0" every time you want to control all instances. I use a [trigger] object to ensure that "target 0" is immediately before any message to control all instances. 

IIRC Chris Muir's "StupidSynth" is a good example: http://www.xfade.com/max/examples/
I can dig up an example later if needed.


Quote: LoneMonad aka don malone wrote on Mon, 19 January 2009 13:48

Careful, in Max 5 if you are splitting the poly~ instances across multiple CPUs, I believe this can cause problems. 

Quote: LoneMonad aka don malone wrote on Mon, 19 January 2009 13:48
----------------------------------------------------
> [send] -> [receive]
> or
> [send~] -> [receive~]
>

Careful, in Max 5 if you are splitting the poly~ instances across multiple CPUs, I believe this can cause problems. 


> Careful, in Max 5 if you are splitting the poly~ instances across multiple

> CPUs, I believe this can cause problems.

Even in Max 4, using [send~] and [receive~] to cross the [poly~] barrier is

not recommended. You have to really know what you are doing. Be prepared to

potential surprises when you mute voices. There are extensive discussions of

these problems in the archives of the forum.

[send] and [receive] should be ok, though I never tried between different

cores. With a single name in all the voices, all voices will receive the

message. If there are problems with several CPUs, let us know!

>> [send] -> [receive]
>> or
>> [send~] -> [receive~]
>>
>
> Careful, in Max 5 if you are splitting the poly~ instances across multiple
> CPUs, I believe this can cause problems.
>
Even in Max 4, using [send~] and [receive~] to cross the [poly~] barrier is
not recommended. You have to really know what you are doing. Be prepared to
potential surprises when you mute voices. There are extensive discussions of
these problems in the archives of the forum.

[send] and [receive] should be ok, though I never tried between different
cores. With a single name in all the voices, all voices will receive the
message. If there are problems with several CPUs, let us know!

>I use a [trigger] object to ensure that "target 0" is immediately >before any message to control all instances.

Ahh trigger, that would have saved me a lot of time and space in my patches, instead of having identical message boxes everywhere.

>I use a [trigger] object to ensure that "target 0" is immediately >before any message to control all instances. 

Ahh trigger, that would have saved me a lot of time and space in my patches, instead of having identical message boxes everywhere.


editing polys