Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uunet!viusys!uxui!unislc!dave
From: dave@unislc.uucp (Dave Martin)
Newsgroups: comp.sys.amiga.misc
Subject: Re: CBM Support is GREAT!
Message-ID: <1991Mar15.192217.8496@unislc.uucp>
Date: 15 Mar 91 19:22:17 GMT
References: <19802@cbmvax.commodore.com>
Organization: unisys
Lines: 26

From article <19802@cbmvax.commodore.com>, by daveh@cbmvax.commodore.com (Dave Haynie):
> In article <13397@hubcap.clemson.edu> ddyer@hubcap.clemson.edu (Doug Dyer) writes:
>>
>>Hmm.  Does anyone know what C= plans to do about the A3000 problems
>>(specifically the deinterlacer's flickering black line)?  Is this a bug
>>that they will fix or is it a feature? 
> 
> Technically speaking, it's a feature.  Converting a full NTSC frame the way
> the A3000's Amber chip does it is just guaranteed to give you that flickering
> 1/2 line.  That's an effect of the NTSC standard and the way its different
> frames get displayed.  All this long and short, odd and even frame nonsense
> I don't know all that much about.  It might be possible to fix, I don't know
> if they're planning to or not.  It would certainly require a revision of the
> Amber chip to accomplish.

It would be nice if it were fixed, but its not that bad of a problem (for
me anyway).  I just adjust my monitor so that that line is not visible
behind the plastic border of the monitor.  Of course this requires a
monitor that does overscan, like the 1950.  I tried several monitors
while waiting for my 1950 to arrive and they all had that iky border
around the usable display space.
-- 
VAX Headroom	Speaking for myself only... blah blah blahblah blah...
Internet: DMARTIN@CC.WEBER.EDU                 dave@saltlcy-unisys.army.mil
uucp:     dave@unislc.uucp or use the Path: line.
Now was that civilized?  No, clearly not.  Fun, but in no sense civilized.