Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!sdcsvax!hutch
From: hutch@sdcsvax.UUCP
Newsgroups: comp.sys.amiga
Subject: Re:  NTSC standard
Message-ID: <2770@sdcsvax.UCSD.EDU>
Date: Fri, 27-Feb-87 03:08:34 EST
Article-I.D.: sdcsvax.2770
Posted: Fri Feb 27 03:08:34 1987
Date-Received: Sat, 28-Feb-87 08:04:37 EST
References: <1235@husc6.UUCP>
Reply-To: hutch@sdcsvax.UCSD.EDU (Jim Hutchison)
Organization: UCSD EMU Project (Educational Microcomputer Unix)
Lines: 21

<>
Strangely there is little to prevent you from having multiple
resolutions out of a single frame buffer, but it is expensive.
The frame buffer I work on daily has a range of resolutions from
1526x1152 non-interlaced to 1024x512 NTSC (remember NTSC is
analog!) to 512x512 NTSC.  If you want to service them all at
once, no.  Changing the scan rate eats up valuable resources.

Huh, you say?  Yes, the vertical blanking interval is a time of
great fun and speed.  If you shorten it, certain operations will
slow down.  does the blitter use the vertical blanking interval?
Or does it sneak into the horizontal flyback to/instead (now that
would be a neat trick) ?  It can be done, but is expensive.  Not
just larger memory, but faster clocks, and it is then turning into
too much money for me to pay.  Money, yep, that is what it boils
down to (atleast for me).
-
-- 
    Jim Hutchison   		UUCP:	{dcdwest,ucbvax}!sdcsvax!hutch
		    		ARPA:	Hutch@sdcsvax.ucsd.edu
Never seems to be enough resolution, memory, or speed, now why is that?