<font color="#cc0000"><font>Thanks I've changed it to use Vline~<br></font></font><br><div class="gmail_quote">On Sat, Oct 6, 2012 at 12:54 AM, IOhannes m zmölnig <span dir="ltr"><<a href="mailto:zmoelnig@iem.at" target="_blank">zmoelnig@iem.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 10/06/2012 10:37 AM, Claude Heiland-Allen wrote:<br>
><br>
>> count the bangs that [tabplay~] will output via it's 2nd inlet.<br>
><br>
> For long files, yes.<br>
<br>
<br>
</div>probably for "intermediate-sized" files.<br>
with "long" files (those that do not easily fit into RAM; or when have a<br>
number of "longish" files, the total of which doesn't fit into RAM), you<br>
are probably better off using [readsf~]'s last outlet, which gives you a<br>
done bang as well, and count that.<br>
<div class="im"><br>
><br>
> For microloops, I'd prefer [wrap~]:<br>
><br>
</div>[...]<br>
<br>
which is nice as well, and tackles the real problem ("i want to loop a<br>
sample N times") rather than a possible implementation ("how can i count<br>
the number of loops (so i know when to stop)".<br>
<div class="im"><br>
<br>
<br>
> (Is [tabplay] clock-aware? it perhaps could be?)<br>
<br>
</div>not afaik.<br>
however, in many cases you don't need (sub)sample-accurate timing and<br>
evaluation at block-boundaries is sufficient.<br>
<br>
gmd<br>
<span class="HOEnZb"><font color="#888888">IOhannes<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
<a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
</div></div></blockquote></div><br>