Xref: utzoo comp.graphics:6965 rec.video:7559
Path: utzoo!attcan!utgpu!watmath!iuvax!mailrus!sharkey!atanasoff!jwright
From: jwright@atanasoff.cs.iastate.edu (Jim Wright)
Newsgroups: comp.graphics,rec.video
Subject: interlace (Re: HDTV and ATV Glossary (TN32))
Keywords: 525/59.94, 625/50, NTSC, PAL, SECAM, Component, Composite,
Message-ID: <1346@atanasoff.cs.iastate.edu>
Date: 18 Aug 89 09:55:18 GMT
References: <120919@sun.Eng.Sun.COM> <121076@sun.Eng.Sun.COM> <428@ctycal.UUCP> <12045@ulysses.homer.nj.att.com>
Reply-To: jwright@atanasoff.cs.iastate.edu.UUCP (Jim Wright)
Organization: Iowa State U. Computer Science Department, Ames, IA
Lines: 19

In article <12045@ulysses.homer.nj.att.com> ggs@ulysses.homer.nj.att.com (Griff Smith) writes:
| In article <428@ctycal.UUCP>, ingoldsb@ctycal.COM (Terry Ingoldsby) writes:
| > Interlace can be a real pain if you want to draw thin horizontal lines, or
| > diagonal lines that cause only a single pixel to be illuminated on a scan
| > line.  In these cases the refresh rate is only the frame rate (eg. 30 Hz),
| > not the field rate, and flicker becomes quite annoying.
| 
| I don't think I've ever noticed this.  If this is the kind of argument
| that is being used, I think the industry is putting something over on us.

For a good example of interlace flicker, watch the Neptune transmissions
being shown on TV.  The left 2/3 of the screen is an image of the planet.
on the right is what appears to be a bar-chart histogram.  The bars are
probably one scan line thick, white bars on a black background.  The
interlace flicker is VERY noticable.

-- 
Jim Wright
jwright@atanasoff.cs.iastate.edu