[Csnd] table for attack time
Date | 2009-10-13 09:15 |
From | Stefan Thomas |
Subject | [Csnd] table for attack time |
Dear community, I would like make a dependency between amplitude and notnum and attack-time. The louder, the shorter, the lower (the midi note number or the frequency) the longer. I guess, the best is, to do it with a table? Or do You have ohter ideas? And, how can I do it with a table? Thanks for any hint, Stefan |
Date | 2009-10-13 09:33 |
From | victor |
Subject | [Csnd] Re: table for attack time |
Not necessarily. For instance
iamp ampmidi 0dbfs
ifreq cpsmidi
iatt = 1/(iamp*ifac1) + ifreq*ifac2
where ifac1 and ifac2 are factors that relate
amplitude and frequency
to attack time. You tune these to get the desired
effect
(for instance if ifac2 is 0, att is only related to
amplitude)
Victor
|
Date | 2009-10-13 11:44 |
From | Victor Lazzarini |
Subject | [Csnd] Re: Re: table for attack time |
Or also (and perhaps better): iatt = ifac1/iamp + ifreq*ifac2 On 13 Oct 2009, at 09:33, victor wrote:
|
Date | 2009-10-13 14:34 |
From | Aidan Collins |
Subject | [Csnd] Re: Re: Re: table for attack time |
I think it should be pretty straight forward to do it with a table too. The ixmode parameter on the table or tablei opcode can be set to look for the index normalized between 0 and 1. So you could have a table with a line or exp. curve in your f table, and then just divide the incoming velocity and notenumber by the range you are expecting and use that as the normailized index. ivel / 127 for full range velocity, inotenum/88 for a full range keyboard. The easiest I think would be to have a separate look up relating to velocity and note number and then add them together to get your attack time. On Tue, Oct 13, 2009 at 6:44 AM, Victor Lazzarini |