Tom;<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">But reading it again now, it<br>
seems like you&#39;re just looking for a way to get a summary of all the<br>
Hid input data that was missed during the last frame?<br>
</blockquote><div><br>No, actually I don&#39;t think we will miss any input as I think there&#39;s a cue for that using; while(my_msg.recv() ) do.something()<br><br>What I want is ChucK to be aware of it&#39;s buffer size in a way accessible from within the language. Right now our programs are unaware of that and I think it can matter in some cases, like the interpolation of more or less continuous data streams, for example from slightly jittery tilt sensors.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Also, knowing your number is interesting. I usually tend toward not<br>
pushing things enough. Though I haven&#39;t used any controllers that need<br>
really tight feedback loops, I usually settle for something closer to<br>
10Hz.<br>
<div><br></div></blockquote></div>Yeah, it depends on the context as well, sometimes a slightly&quot;lazy&quot; feel can even be nice but generally I think a more immediate response leads to more fun and better playing.<br>
<br>Yours,<br>Kas.<br>