-
mjmogo
@ddw_music These envelopes are being used on modulation signals, not directly on audio signals.
And as far as the output of 'function', yes, I know I can change it. My comment was more a flag for myself if it actually is a bug in 'envgen~', then I need to be prepared to handle this workaround until the bug is fixed.
Mike
-
mjmogo
@ddw_music said:
@mjmogo said:
In using the following list for the breakpoints, and setting the suspoint to 3,
[0 100 1 300 .7 1000 .2 3000 0 (
Looks like a bug. suspoint works as expected when you have an even number of floats in the list.
Delete the first 0 and use suspoint 2.
hjh
And thank you for the reply. It works as you would expect it to... My only issue now is that I need an envelope that doesn't assume you are starting at zero on the envelopes...
Ok, and it appears the solution to my problem is to use an initial time of 0...
Looks like using else/function as an editor for what I need won't work, because it always has the initial value at the start of the list.
Thanks again!
-
mjmogo
https://en.wikipedia.org/wiki/Linear-feedback_shift_register
While I don't know if this is implemented in Pd, but the Turing machines I've seen are based on the linear feedback shift register.
-
mjmogo
I've recently been looking into the ELSE library, and specifically the envgen~ object. In creating a simple ADSR-like envelope, I was trying to set the 'suspoint', and found some curious behavior.
In using the following list for the breakpoints, and setting the suspoint to 3,
[0 100 1 300 .7 1000 .2 3000 0 (
when I execute this it starts the envelope and it stops when it gets to the .7 value, and when it is released, it immediately goes to the last stage, bypassing the .2 value.
But when I set the suspoint to 4, the envelope operates properly and stops at the .2 value. Then when I release the envelope, it just stays at the .2 value, and does not execute the last stage.
Next I tried to add one more stage and run using the same suspoints of 3 and 4... when I run it with stage 3, upon release it uses the time from the following stage (segment 4), not the last.
Am I missing something here? It seems to me that the first one (set to stage 3) is operating correctly, but when the stage is set to 4, it ignores the last stage upon release.