Fellow ChucKists, Dear Dan.<br><br>It seems like LiSa is ignoring .rampDown() while in .track(1) mode and .rampUp() becomes equivalent to .play(1).<br><br>Consider the following example, this should generate a tone that fades in over the course of a second, then fades out. Instead we get a extended test-tone and no fades at all;<br>
<br>//-------------8&lt;--------------------<br>//boring test-tone recording<br>SawOsc s =&gt; LiSa l =&gt; dac;<br>second =&gt; l.duration;<br>1=&gt; l.record;<br>l.duration() =&gt; now;<br>0=&gt; l.record;<br><br>s=&lt;l;<br>
<br>//boring tracking signal<br>Phasor p =&gt; l;<br>second =&gt; p.period;<br>1 =&gt; l.track;<br><br>//issue starts here<br>second =&gt; l.rampUp;<br>second =&gt; now;<br>second =&gt; l.rampDown;<br>hour =&gt; now;<br>//-----------8&lt;---------------------------<br>
<br>I believe that this isn&#39;t the intended behaviour; for one thing the relevant examples also use .rampDown() in combination with .track(), mysteriously there too the ramps don&#39;t work. Likely ramping in combination with track() got broken in a update since these examples were written, that would probably help narrow down the search for the nature of the issue. Then again; this could be a artefact of .track() being intended for single voice usage (I believe this was mentioned) and the ramps being functions of voices?<br>
<br>I&#39;ll add this to the WiKi once it&#39;s been established that this is indeed a bug and not intended behaviour.<br><br>Yours,<br>Kas.<br>