<br><br><div class="gmail_quote">2009/8/14 Hans Aberg <span dir="ltr"><<a href="mailto:haberg@math.su.se">haberg@math.su.se</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br></div>
There seems to be a timing problem with <<< ... >>> in ChucK. So take all that away in all time critical positions, and see if the problem goes away. And report back here, if it does.<br><font color="#888888">
</font></blockquote></div><br>I think the main issue is that printing isn't done by the VM itself and that printing to the screen is expensive, CPU-wise.<br><br>This can have some quite far-reaching effects. I'm not sure it's still like that but a long time ago I noted that when I'd print something, then immediately afterwards quit the shred the printed message sometimes wouldn't show. This could be fixed by advancing a bit of time after the print command. Of course advancing time may not always be possible in all conditions without causing timing issues to the overall program.<br>
<br>Yours,<br>Kas.<br>