Poly~ and ADSR~

Sep 24, 2012 at 8:54am

Poly~ and ADSR~

I know I’m not the first to have trouble with this combination, but I can’t seem to find the answers in the documentation and other posts. I’m hoping someone can help me troubleshoot this one.

I have a simple patch that contains a poly~ abstraction. The poly component works fine. My problem is in the adsr~ object. I seem to get inconsistent results with it, and never a proper envelope with attack, decay, sustain and release. Sometimes I’ll get the attack, but no release, or various combinations like that. Any help would be grand!!


Main Patch:

– Pasted Max Patch, click to expand. –

Poly Abstraction:

– Pasted Max Patch, click to expand. –
Sep 24, 2012 at 9:43am

I have an example, called StupidSynth, that shows using adsr~ in a poly~. It can be found here:


Sep 24, 2012 at 9:51am

Looking at your top level patch, I wonder why you are using poly in addition to poly~?

Here’s an untested simplified version of your top level patch:

– Pasted Max Patch, click to expand. –
Sep 24, 2012 at 12:18pm

Thanks for the reply.

I followed the same method used in the MSP tutorial on

. is used with the target attribute of to route messages to a specific voice of . Maybe what I’m doing is unnecessary. I’ll try to do another method of polyphony without it, since it seems odd to have that to you. Maybe the on/off velocities from the MIDI is being allocated to different voices or something, thus creating problems in the envelope. Thanks for the input and looking at my patch. Always appreciated.

I appreciate another example too. Thanks for posting that.

Sep 24, 2012 at 1:44pm

Ok. Got it. Here’s the working patch – might be helpful for someone else. Obviously you’ll have to connect some of the broken patch cords after you paste it.

Thanks to Chris for noticing the oddity of using the poly object.

Main Patch:

– Pasted Max Patch, click to expand. –

Poly~ Patch:

– Pasted Max Patch, click to expand. –
Sep 24, 2012 at 7:51pm

Also, send/receive is a good tactic for this, since you want to make sure all copies are getting the same info.


You must be logged in to reply to this topic.