Am 04.07.2011 um 19:10 schrieb Garth Hjelte: > Right. "Dc" I think means Decay Control. When Dc is checked, the > "Time" parameter in the Group is a Note Counter, in milliseconds. > This measures the time between noteon and noteoff. If the Time > parameter is 2000ms, and there was 1000ms (1 sec) between noteon and > noteoff, the release sample will be 50% of the original volume. It's > the "correct" way to deal with RT volume. Some people prefer release > velocity control, but people often don't play with that in mind. > > You program the Time parameter with the actual decay of the sample in > mind. For example, take a piano; look at the actual decay, then put > the Time parameter consistent with it. > Are we talking about the same program here? EXS24 for Apple Macintosh that comes with Logic Pro 9.1.4 and MainStage 2.1.3? ;-) I cannot set Time to 2000. Maximum value is 1000. Also, as I wrote, the amplitude and envelope of the release sample is absolutely independent of the length of the note previously played (the time between note on and note off). BTW, what does RT stand for? Release Trigger? > I believe that the Env2 (Amp) Decay parameter is paid attention to > when considering the release time of the RT. Remember the Sustain > level is still considered in calculating the Decay Time. I believe that the Env2 parameters are completely ignored when Trigger is set to key released. At least that's what the help file says (slightly hidden, under "Envelope 1 Offsets" and "Envelope 2 Offsets"). > When the > Sustain Level is 0, the Decay Time is as-is. If (for example) the > Sustain Level is 50%, you cut the Decay Time in half. (EXS uses > "rate-based" envelopes.) This is where the Group Offsets for the Env2 > (Amp) settings are valuable, you can create your own custom settings > for the RT samples. The group offsets for Env2 aren't accessible as soon as Trigger is set to key released. Ingo [Non-text portions of this message have been removed]
Message
Re: [EXS] Dc parameter?
2011-07-04 by Ingo Debus
Attachments
- No local attachments were found for this message.