On Fri, 16 Jan 2009, Michael Hawkins wrote:
> For example, we might decide that we want the envelope to change
> behavior when the velocity was above 63. Below 63 the envelope would
> behave in one manner and above 63 it would behave in some other way (for
> example, reducing the attack time by some offset).
==============
that'd be cool, especially if the level could be part of what's different.
it's kind of a 303-ish approach.
another way that might work... ∗if∗ i understand it correctly and ∗if∗
there's enough RAM and if we can accept a decrease in velocity resolution
from 127 to (let's say) 16 or 32... can we precompute 16 (or 20, 24, 32,
64?) envelopes, and based on velocity pull the appropriate precomputed
envelope from a table in RAM? the precomputation would have to take place
when a patch is loaded or an envelope is edited (and would take time), but
it seems like it could be a workable time/space tradeoff if the conditions
can be met...
--
...atom
________________________
http://atom.smasher.org/ 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
-------------------------------------------------
"Politics would be a helluva good business
if it weren't for the goddamned people."
-- Richard M. Nixon