<div dir="ltr"><div>Perry, I think I've confused things for everybody. Here's a recap.</div><div><br></div><div>- ADSR.setAllTimes effectively misinterprets the decay times.</div><div><br></div><div>- Correcting ADSR.setAllTimes is simple but changes the behavior of all existing calls.</div>
<div><br></div><div>- With the correction, the resulting decay times will be what the caller specifies but this is</div><div>different (usually) from current effective decay times.</div><div><br></div><div>- If that difference results in a perceptible audio difference, the calls to ADSR.setAllTimes could be modified, changing the decay argument to match the "incorrect" decay time that ADSR has been producing.</div>
<div><br></div><div>- However, expecting that all existing calls to ADSR.setAllTimes from outside the SDK would be modified is impractical.</div><div><br></div><div>I want to make it clear that as a total newbie to the SDK I'm not proposing whether a change should be made or not. It seems like a quandary from the standpoint of backward compatibility.</div>
<div><br></div><div>Bob H</div><div><br></div><div><br></div></div>