Hans;<div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Indeed. But we don&#39;t have to calculate a sample every sample; we only need to calculate a block every block; there is some leeway.<br>
</blockquote>
<br></div>
What are these blocks? I thought Chuck is running in one thread. It is though true that one could free the marker of the memory synchronously, and let a GC in a separate thread collect inasmuch it gets time for it.<div><div>
</div><div class="h5"><br></div></div></blockquote><div><br></div><div>These refer to the amount of samples that are send to the soundcard at a time, it&#39;s set by &quot;--bufsize&quot;. This is universal to addressing soundcards and not related to threading as such. Because of the size of blocks we may have more than a samp to spare (per block) for tasks like GC. Maybe we don&#39;t have that time in some cases but of course; at some point we will be asking the cpu for more than it can provided, no matter the way in which we ask.</div>
<div><br></div><div>Yours,</div><div>Kas.</div></div></div>