Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!sarah!newserve!bingsuns.cc.binghamton.edu!consp03 From: consp03@bingsuns.cc.binghamton.edu (Kriston J. Rehberg) Newsgroups: comp.sys.amiga.hardware Subject: Re: Productivity was Re: Amiga Video Lamers was Re: (Video) Idiots ? Message-ID: <1991Jun18.200422.9313@newserve.cc.binghamton.edu> Date: 18 Jun 91 20:04:22 GMT References: <1991Jun9.181849.27338@newserve.cc.binghamton.edu> <1991Jun11.035833.23743@news.stolaf.edu> <1991Jun11.184413.10125@newserve.cc.binghamton.edu> <1991Jun13.150555.6140@NCoast.ORG> Sender: usenet@newserve.cc.binghamton.edu (Mr News) Reply-To: consp03@bingsuns.cc.binghamton.edu (Kriston J. Rehberg) Organization: SUNY Binghamton Lines: 44 Nntp-Posting-Host: bingsunm.pod.binghamton.edu In article <1991Jun13.150555.6140@NCoast.ORG>, davewt@NCoast.ORG |> What??? WHAT ELSE ARE YOU RUNNING THAT IS SUCKING UP GAWDAWFULL AMOUNTS |>OF CPU TIME???? I have NEVER EVERE EVERE (that's not in my entire life) |>sen the kind of effects that you are describing on ANY Amiga when using |>interlaced mode (with or without some kind of flicker fixer). The way you talk |>it takes a seccond or so for characters to appear. I can open up a full-size |>Shell window and cat a text file and STILL not see anything that you |>are describing, and I always have at least 4 other things running at |>the same time. What do you have, a 16,000 by 16,000 16-color WorkBench |>opened up with a giant shell window? Calm down a bit! CPU time has nothing to do with how well the deinterlacer works. No, it's more like a fraction of a second, but noticeable when you move the pointer around. Sit yourself down and see for yourself. The scan problems I see are due to the fact that the interlace mode is updated once every 30 Hz (net, not gross). It just keeps the lines not in the current vertical refresh from disappearing, so we get the illusion that the display is updated every 60 Hz when in reality, one vertical scan draws the odd numbered lines (in the first 30 Hz interval) and the next interval gets the even ones. It's not noticeable unless you are animating something like a mouse pointer, and when you're using 640*400 interlaced mode. When you move your mouse up and down, you can see the effect as it turns into something like venutian blinds - kinda snowy. Of course, it doesn't happen in 640*200 mode because the oddd (unused) lines are just copying what the even lines do. (That's a simple way of looking at how scan-doubling works). Where did you get the idea that it was CPU time or bitplane width? |> Dave -Kris +---------------------------------------------------------------------+ | Kriston J. Rehberg, Consultant, SUNY-Binghamton Computer Services | | or | | #include "Hackito ergo sum" - old Latin proverb | +-------------------------------------------------------------- ;-b --+