Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!pasteur!agate!eris!doug
From: doug@eris (Doug Merritt)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Fixing flicker, & future frame rate issues
Message-ID: <8929@agate.BERKELEY.EDU>
Date: 19 Apr 88 06:57:03 GMT
References: <11157@ut-sally.UUCP> <8528@agate.BERKELEY.EDU> <11182@ut-sally.UUCP> <8577@agate.BERKELEY.EDU> <1367@hubcap.UUCP> <3626@cbmvax.UUCP> <11253@ut-sally.UUCP> <3642@cbmvax.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Reply-To: doug@eris.UUCP (Doug Merritt)
Organization: University of California, Berkeley
Lines: 20
Keywords: Point- Counterpoint

Here's one that's short, sweet, and to the point:

In article <3642@cbmvax.UUCP> hedley@cbmvax.UUCP (Hedley Davis) writes:
[ Bryan's comments about fF omitted ]
>You are wholly incorrect. Inutition updates the pointer location at 60
>Hz regardless of whether the display is interlaced or not. So, no matter
>what kind of deinterlacer you have , two feild store, or one feild
>store, the pointer will break up.

So...Bryan may have gotten confused about the issue of the Intuition
pointer itself breaking up. As I said before, that's a nice
counterexample of a situation that simply cannot be effectively
deinterlaced; you'll always get inappropriate breakup.

But note that you're still ignoring all of the *other* types of
cases where Bryan's comments are still to the point. For *some*
applications (both existing *and* written just for a flicker fixer),
fF *could* be improved upon.
	Doug Merritt		doug@mica.berkeley.edu (ucbvax!mica!doug)
			or	ucbvax!unisoft!certes!doug
			or	sun.com!cup.portal.com!doug-merritt