[chuck-users] dur frame?

[Kassen]

Tom;

But reading it again now, it
> seems like you're just looking for a way to get a summary of all the
> Hid input data that was missed during the last frame?
>

No, actually I don't think we will miss any input as I think there's a cue
for that using; while(my_msg.recv() ) do.something()

What I want is ChucK to be aware of it'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.


> Also, knowing your number is interesting. I usually tend toward not
> pushing things enough. Though I haven't used any controllers that need
> really tight feedback loops, I usually settle for something closer to
> 10Hz.
>
> Yeah, it depends on the context as well, sometimes a slightly"lazy" feel
can even be nice but generally I think a more immediate response leads to
more fun and better playing.

Yours,
Kas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cs.princeton.edu/pipermail/chuck-users/attachments/20090129/49c219e5/attachment-0001.html>