Tom;<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Yeah, it's not always an answer, but sometimes it is! And it's easy.<br>
So I try it!<br>
<div class="Ih2E3d"></div></blockquote><div><br>:¬) I'll be sure to when there is a need. I don't think there is here, I think we can safely mix voices before the reverb instead of mixing 15 or so reverbs together, as long as we make sure all voices have the right "wet" and "dry" amounts. This will lead to slightly more involved control at starting sounds but it should be much cheaper on the CPU. If I understand all of this correctly saving CPU will mean running the whole thing at a higher rate.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
</div>It'd probably be similar to .chan() syntax.<br>
<div class="Ih2E3d"></div></blockquote><div><br>Yeah. I'd like something like that; channels beyond .left() and .right(), they would be nice for this, for state-variable filters and perhaps even for modulation inputs.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"><br>
<br>
</div>I think it's just to get the particular sound you get when a new voice<br>
is fired at regular intervals... I don't know what kind of noise he's<br>
recording, but when I tried it sounded kind of nifty. 'Cause his code<br>
differs from the example script he seems to have copied.<br>
<div><br></div></blockquote></div><br>I think so, I didn't know the SMS was so different; that's why I asked. <br><br>Yours,<br>Kas.<br>