Path: utzoo!attcan!uunet!wuarchive!cs.utexas.edu!bryan
From: bryan@cs.utexas.edu (Bryan Bayerdorffer @ Wit's End)
Newsgroups: comp.sys.amiga
Subject: Re: Commodore De-interlacer
Message-ID: <239@mohawk.cs.utexas.edu>
Date: 5 Nov 90 18:12:01 GMT
References: <5463@crash.cts.com>
Reply-To: bryan@cs.utexas.edu
Organization: Spam Detection & Removal Squad, Austin, TX
Lines: 15
Spam-Content: Negligible

In article <5463@crash.cts.com> seanc@pro-party.cts.com (Sean Cunningham) writes:
=- 
=-I found that if you'd go into your OVERSCAN preferences and position the
=-settings box exactly ONE pixel below the top line, then you won't even notice
=-the frag is there.
=- 
	That's fine for the workbench, but what do you think happens when some
program comes along and opens a custom screen without looking at the prefs?
You guessed it.

	Every time this subject comes up, I ask why the C-A deinterlacer can't
handle the first scan line in whatever way the flickerFixer does.  I've never
seen any answer to this.  I'd just like to know whether the problem is due to a
design or manufacturing error, or is the deliberate result of some cost
reduction measure.  In either case, is it with us forever?