Andrew;<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Understand that times are represented as a delta of the number of<br>
samples since the VM (or maybe it&#39;s the shred) started executing.<br>
Again, the time itself doesn&#39;t carry any information about how it was<br>
created, []</blockquote><div><br></div><div>Sorry for the late response; I haven&#39;t been at home over the weekend and my hosts were dealing with a LAN issue. Just catching up on mails here.</div><div><br></div><div>You are quite right here, and I&#39;d like to add that time is always expressed as samples since the origin of the VM. Instantiating a new variable of type time will have it refer to &quot;time 0&quot; being the origin of the VM. This is the same for all Shreds, no matter when they were sporked or added. &quot;now&quot; is a special case (of type time) and always refers to the amount of time that has passed since the start of the VM.</div>
<div><br></div><div>It&#39;s also interesting to note that while time and now are quite universal things they are expressed in samps yet obviously the duration of a samp depends on the settings used. It&#39;s probably not a good idea to perform any calculations (but dsp) expressed in samps as your code won&#39;t be portable from machine to machine. BPM and/or tuning may change if you do.</div>
<div><br></div><div>Hope that clarifies. Likely this was already well known to many but it&#39;s such a important point that I didn&#39;t want to gloss over it.</div><div><br></div><div>Yours,</div><div>Kas.</div></div>