Re: Timer resolution

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

> Remember that, in an NTSC video system, the exact capture time is
> essentially irrelevant. Frames had better be coming in at exactly 29.97
> Hz. Many capture devices compute the frame time by counting the number of
> frames and dividing by 29.97. You basically "round" the current time to
> the nearest multiple of 33.3667 milliseconds.

Really? Am I too blind to see something obvious or is it just plain broken?
Any frame drop in this case will result in clock drift. For long running
systems with inevitable frame drop this can result in significant difference
between reported clock and what should've been reported.

-- Max.


.

Relevant Pages

  • Re: Timer resolution
    ... >> Remember that, in an NTSC video system, the exact capture time is ... >Any frame drop in this case will result in clock drift. ... >between reported clock and what should've been reported. ...
    (microsoft.public.development.device.drivers)
  • Re: Timer resolution
    ... You mean well designed devices? ... > Well designed systems will give you an empty frame in place of a dropped, ... >> Any frame drop in this case will result in clock drift. ... >> difference between reported clock and what should've been reported. ...
    (microsoft.public.development.device.drivers)
  • Re: Timer resolution
    ... Well designed systems will give you an empty frame in place of a dropped, ... > Any frame drop in this case will result in clock drift. ... > difference between reported clock and what should've been reported. ...
    (microsoft.public.development.device.drivers)