Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!ucbcad!ucbvax!vax135!cjp
From: cjp@vax135.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: The LIVE Digitizer from A-Squared...
Message-ID: <1785@vax135.UUCP>
Date: Fri, 29-May-87 20:48:32 EDT
Article-I.D.: vax135.1785
Posted: Fri May 29 20:48:32 1987
Date-Received: Sat, 30-May-87 11:48:37 EDT
References: <8705290639.AA04316@ingres.Berkeley.EDU>
Reply-To: cjp@vax135.UUCP (Charles Poirier)
Organization: AT&T Bell Labs, Holmdel, NJ
Lines: 29
Summary: Takes over machine...?

In article <8705290639.AA04316@ingres.Berkeley.EDU> hatcher@INGRES.BERKELEY.EDU (Doug Merritt) writes:
>In article <149@l5comp.UUCP> scotty@l5comp.UUCP (Scott Turner) writes:
>>2. If it takes over the machine does this mean it WON'T work with my hard
>>disk drive?
>
>It *cannot* work simultaneously with a hard disk. It takes over the machine
>because there are just *exactly* enough memory cycles available to read in
>the video data at the same time that the screen display is maintained. The
>handle it (that I know of, anyway).
>...
>The intention of LIVE is to fill memory with video, and THEN dump it to
>hard disk (or floppy...).

I just hope they were sane about how they "take over" the machine.
Ideally LIVE would be "wired" *only* while it was digitizing.  I'd want
to be able to keep other processes alive (tho frozen) while running
LIVE.  Anyone know if this is the case?

Actually, I wonder if they could allow other tasks to run (at lower
priority?) if the user were willing to select a *lower* frame rate.  As
an example, you might want to have a process that can get frames from
RAM, examine or do stuff to them, and spit them back to the screen
*while* LIVE is running.  Have an option to turn off LIVE's screen
during this scenario.  This would allow people to roll-their-own
Very Vivid / Mandala type programs.
-- 
	Charles Poirier   (decvax,ucbvax,ihnp4,attmail)!vax135!cjp

	"The road to Hell is paved with good opinions."