Forums > MaxMSP

adsr~ Clicks!!

December 6, 2012 | 5:19 pm

Here is the main patch… I will also upload the other patchers.

– Pasted Max Patch, click to expand. –

The synth patcher…

– Pasted Max Patch, click to expand. –

That should be all you will need. I am using a midi keyboard to produce the cycle~ signal. It is polyphonic. Even when I mess with the adsr~ settings, I still get clicking! Please help!!

Attachments:
  1. retrysynth.maxpat

December 6, 2012 | 9:19 pm

hey.
I don’t know, i didn’t have a very close look at your patch(tidying up helps you and us debug..)
Updating the frequency of the oscillator at audio rate (via [sig~]–[mtof~] –[sah~]) would be worth a try. What attack times are you using? Do you have clicks in the transients or attack phase or also at the end of and envelope? Adjusting retrigger time could also help, although the default values shouldn’t click i think.
cheers


December 6, 2012 | 9:36 pm

I have a dial that have an attack set up to 500 milliseconds. I have clicks at the end of an envelope and when I’m playing more than one note at a time. I tried to do something with the retrigger, but it didn’t do anything. Not sure if I was understanding how to do it correctly.


December 6, 2012 | 9:53 pm

About more than one note at a time:
Isn’t it clipping for a short amount of time maybe? i don’t see any scaling in respect to voices.
end of envelope:
too short release?


December 7, 2012 | 7:04 pm

Read the help files about what a target 0 message does to the [poly~ retrysynth 10 @steal 1], because each of the [adsr] wants to get its values, not only the one in the first instance. I Hope that helps.
Cheers.
Stan


December 10, 2012 | 3:34 pm

@woyteg

It is only clipping when a previously affected note is still being played and when I do note off.

@stan

I can’t seem to find the help files for that message. So I’m not sure where to attach it.


December 11, 2012 | 9:04 am

poly~ reference about the target message: Specifies 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.

For sending messages to the [poly~] itself use its first inlet.


Viewing 7 posts - 1 through 7 (of 7 total)