<br><br><div><span class="gmail_quote">On 10/11/07, <b class="gmail_sendername">Martin Ahnelöv</b> <<a href="mailto:operagasten@gmail.com">operagasten@gmail.com</a>> wrote:</span><div> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think you have to wrap it in a while-statement:</blockquote><div> </div><br>Yes, you can and that's a good technique, but you need a shred that runs at the same timing as your looped sample. If you have one of of those then you are in business, if not you need to make one and control the duration from outside of it, possibly with the need for resetting it all if it's a rhythmic loop. At that stage I think LiSa is far more convenient.
<br><br>It's no secret that I'm a big fan of LiSa in general :¬)<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Though, a .loop(true/false) would be cool.
</blockquote><div><br><br>From memory; it has one but it will always loop at the exact length of the loaded file so that requires more planning ahead then LiSa does.<br><br>On the other hand; if you do load a file using SndBuf you can get the amount of samples it has from the buf as soon as it's loaded and that's very convenient if you have -say- a breakbeat loop and you'd like shreds to have the exact period of the drum loop (try that in Ableton!).
<br><br>If LiSa does "learn how to read", I'd like that functionality in LiSa as well. I think that at that point SndBuf would become a bit dated but that's what progress does....<br></div><br><br><br>Kas.
</div>