Eric Sheffield

I'm working on a synth that uses multiple adsr~ provided envelopes for a single note.

Right now I'm just triggering them all at (nearly) the same time by sending a 1 to all three of them from the same unpack object. Is there a better way I should be doing this? Thanks.

Hello.
I'm working on a synth that uses multiple adsr~ provided envelopes for a single note.
Right now I'm just triggering them all at (nearly) the same time by sending a 1 to all three of them from the same unpack object.  Is there a better way I should be doing this?  Thanks.

multiple-adsr

I realize that I need to fix my receive objects. :)

P.S.
I realize that I need to fix my receive objects.  :)


The triggering looks ok to me. My only question is why one adsr~s mute output is connected to thispoly~ while another adsr~s signal output is connected to thispoly~? Should these both be from the same adsr~? What happens when one of the shorter envelopes controls thispoly~ (Well, we know what happens, the sound is abruptly cut off...)

So...maybe another way is to have each of these signal to adsr~s inside its own poly~. Perhaps that's overkill.

Each adsr~ is always going to be one of three lengths- long, short, and extra short (pink noise).

I'm trying to recreate both the sounds of metal objects and large toms being struck. The short adsr~ takes care of the initial attack, the long one provides a little more sustain, and the pink noise is there for a little extra percussive attack if needed. The pink noise adsr~ is the first activated (right to left order) and shortest, and the longest adsr~ is the one to mute thispoly~ when it's finished. All of these attack and decay lengths are being provided from outside of the poly~ in the main patch.

It seems like function would work better for sounds like this, but I was actually having a little better luck with this method, and since the sounds are supposed to mimic acoustic sounds, this seemed like a simpler, more approachable way to create the overall envelope. The sounds are being triggered by a MIDI drum pad, so using only the attack and decay stages seemed to make the most sense.

Thanks for your input! Here is a slightly revised version of the first patch I posted.

And here is what the system providing data to the poly~ looks like:

The forward objects are meant to transmit the respective data once an acceptable sound is achieved.

Ah, yes.  Good observation.
Each adsr~ is always going to be one of three lengths- long, short, and extra short (pink noise).
I'm trying to recreate both the sounds of metal objects and large toms being struck.  The short adsr~ takes care of the initial attack, the long one provides a little more sustain, and the pink noise is there for a little extra percussive attack if needed.  The pink noise adsr~ is the first activated (right to left order) and shortest, and the longest adsr~ is the one to mute thispoly~ when it's finished.  All of these attack and decay lengths are being provided from outside of the poly~ in the main patch.
It seems like function would work better for sounds like this, but I was actually having a little better luck with this method, and since the sounds are supposed to mimic acoustic sounds, this seemed like a simpler, more approachable way to create the overall envelope.  The sounds are being triggered by a MIDI drum pad, so using only the attack and decay stages seemed to make the most sense.
Thanks for your input!  Here is a slightly revised version of the first patch I posted.

The forward objects are meant to transmit the respective data once an acceptable sound is achieved.


Argh. The muting in this poly~ is not working. Help, please? :)

It's triggering just fine. I used the print object to see what was going on, and it just keeps spitting out "mute 0" every time I play a note...

Argh.  The muting in this poly~ is not working.  Help, please?  :)
It's triggering just fine.  I used the print object to see what was going on, and it just keeps spitting out "mute 0" every time I play a note...

It was because I was using the adsr~ in the poly~ without the sustain, but had not actually sent the "maxsustain 0" message. Therefore, it was never sending the "mute 1" message. 

Seems to work now that I've given them all the maxsustain 0.

Ah!  :)
Nevermind.  Figured it out.
It was because I was using the adsr~ in the poly~ without the sustain, but had not actually sent the "maxsustain 0" message.  Therefore, it was never sending the "mute 1" message.  
Seems to work now that I've given them all the maxsustain 0.
