Mike Lawrence wrote: > After a few more discussions with colleagues, I'm comfortable > concluding from the above code and comments that the best way to > ensure accurate timing is to: > > 1) double flip at the beginning of the trial to ensure timing is > synced to the display > > 2) ensure all desired display change times are integer numbers of > refreshes > > 3) ask for a display change a half refresh before the desired display > change time
You can ask for a display change immediately after your blocking call to flip() returns (waiting of half an IFI seems dangerous in that you'd be more likely to miss your time window). Your frame will be drawn on the next screen update after your previously drawn frame. 4) You cannot rely on the timing of the flip() return to indicate when the image was actually displayed on the screen. There's actually a lag in the pipeline to the display. (This is important when considering synchronization with other hardware, such as button boxes or fMRI machines.) -- Andrew D. Straw, Ph.D. California Institute of Technology http://www.its.caltech.edu/~astraw/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
