🚀 go-pugleaf

In article <11561@sun13.scri.fsu.edu> Chris Green,
chrisg@cbmvax.cbm.commodore.com writes:
>	Has anyone ever attempted to take advantage of the 
>"infinite-frame-rate" of raster scan devices, particularly video?
>What I mean by this to render your animation with the knowledge
>that each pixel is (for instance) 35ns later than the preceeding
>pixel, and that each scan-line is ~63uS later than the preceeding
>one. 

I can't think of anything directly related, but here are a couple 
indirectly related items:

- Many video games and other tightly coded interactive programs
use a technique called "beam chasing" to schedule screen updates
and interaction.  The idea is to be aware of the position of the
CRT beam in order to avoid writing a graphic to the screen while
the beam passes through it, producing a "tearing" effect.

- In a talk given by Pacific Data Images several years ago, one of
the developers there discussed how they produced interlaced animation
for video.  Since they knew that when the work was reproduced the odd
scanlines would appear 1/60th of a second after the even ones (or 
vice-versa, I'm not a video expert) they updated the positions of
moving objects between interlace scans.  I've also heard people say
that being aware of the interlacing is important for getting motion
blur to look correct on video.  The PDI talk was written up in a
SIGGRAPH course notes ages ago ('82 or '84; something like that).

Cheers,
jp

--
Moderated by SCRI Vis <>           Submissions to: graphics@scri1.scri.fsu.edu
Guy, John R. Murray   <> Administrivia to: graphics-request@scri1.scri.fsu.edu