Re: hardware timestamp issues

I actually solved the main issue a while back; thought I'd share it here.

It turns out, my plugin actually WAS recording key frames, but I had to expand
my time window to see them. I was resetting my timestamps when 'record' was
clicked, and so by the time 'play' was clicked, several seconds had passed by.
The time window does not autoresize, but you can manually stretch it (and so I
guess you can program this too)... and so when I pulled it open to a few
thousand frames wide, I found my key frames sitting right there in the middle. I
guess the proper solution is to reset the timestamps when 'play' is clicked (or
is there a better way of doing it)?

This still doesn't answer my question of how the FBDeviceOptical sample is
working. As far as I can see they're still writing software timestamps with
values 0,11,22,0,11,22, etc, and I don't understand why this works.