Jiegel

Okay, here is a sample patch that a Max genius (who you have all heard of) put together for me in about 10 seconds. (please read down)

notice that when you click the toggle button, the function graph always starts and ends at 0 (thus avoiding pops/clicks due to overlap.

I essentially copied it directly into another patch, changed random to drunk, and changed the "/" number to related to the metronome speed (which is variable).

So WHY ON EARTH isn't my version going back to zero? Here is the code copied from my patch:

Okay,  here is a sample patch that a Max genius (who you have all heard of) put together for me in about 10 seconds. (please read down)

So WHY ON EARTH isn't my version going back to zero?  Here is the code copied from my patch:

what-is-wrong-with-this-want-function-to-go-back-to-0

So WHY ON EARTH isn't my version going back to zero?

put a print out of your messages [$1 0.] and you will see some messages like that :

So if you set the "hi domain display value (X-axis)" of your functions to something like 100000., you'll see it is actually going down to zero... :)

Hmm..you're right. But then why is it still clicking when it plays? How would I go about changing it to, say, lop off the first 20 milliseconds on both ends? I'm sorry to be a pest but this piece of the patch is beyond my understanding...

Hmm..you're right.  But then why is it still clicking when it plays?  How would I go about changing it to, say, lop off the first 20 milliseconds on both ends?  I'm sorry to be a pest but this piece of the patch is beyond my understanding...


it probably makes clicks if you trigger your function too early. 

it has something to do with the fact that my patch uses DRUNK instead of RANDOM. Can anyone tell me why that would be? Literally if i change absolutely nothing but swap drunk and random for one another it only works for random. Can anyone suggest proper range / step sizes for me to go with on drunk to make it so it never clips like that?

it has something to do with the fact that my patch uses DRUNK instead of RANDOM.  Can anyone tell me why that would be?  Literally if i change absolutely nothing but swap drunk and random for one another it only works for random.  Can anyone suggest proper range / step sizes for me to go with on drunk to make it so it never clips like that?


as the range of your [drunk] is 1000, you should first try to divide its output by 1000. and not by 570. Does that solve the issue?

What is wrong with this? Want function to go back to 0