<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 1/29/2017 3:18 PM, Alexandre Torres
Porres wrote:<br>
</div>
<blockquote
cite="mid:CAEAsFmjjC8h==7RRa36YcTAEtiUrAX6kM9ARgndQqiyqMKWYXw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">2017-01-29 17:53 GMT-02:00 Ivica Ico
Bukvic <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ico@vt.edu" target="_blank">ico@vt.edu</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> I also think
unthreaded should be default to maintain determinacy in
sync with Max</div>
</blockquote>
<div><br>
</div>
<div>hi, sorry, i dont think i get what you mean, can you
elaborate on what "determinancy" is? I was asking about it
in my earlier messages, I wasn't sure before and now I
really don't I get what it's supposed to mean.</div>
<div><br>
</div>
<div>cheers</div>
</div>
</div>
</div>
</blockquote>
<br>
It means that threaded version will report a bang when done loading
in clock_delay(0) way. In other words as soon as possible but not
necessarily in the same cycle of handling non-audio messages. So, if
you issued a bang to load a coll file that fans out into a trigger
with two bangs, in a determinant (non-threaded) way one bang hitting
the coll would be followed by coll pushing out a done reading bang,
and then the second bang from the trigger would come out. In a
threaded way, the second bang could potentially come out before the
done reading bang which breaks the order of execution but also
ensures there are no dropped samples.<br>
<br>
HTH<br>
<br>
Best,<br>
<br>
Ico<br>
</body>
</html>