Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!van-bc!outbound!patrick_meloy From: patrick_meloy@outbound.wimsey.bc.ca (Patrick Meloy) Message-ID: Organization: Outbound Communications Newsgroups: comp.sys.amiga.graphics Subject: Re: DCTV Date: 20 Apr 91 09:11:37 PDT > You're dreaming. The 300K file contains nowhere NEAR the >resolution as the 24 bit Toaster image. The catch is that the >NTSC display is only slightly better than the DCTV image so the >difference is hardly noticable. HOWEVER, if you compared the DCTV >conversion of the 24 bit Toaster file with the output from an RGB >24 bit frame-buffer, you would notice the difference. > Be sure that DCTV is slightly worse than NTSC, I belive >mainly in vertical resolution. Although I'm not certain what is >in that 300K and what is in that 700K file, there is no way that >NOTHING is lost when you remove 4/7 of the file. Well, consider this. The toaster output I work with is the 768x482 (non full size image). That gives a total maximum number of colours of 370,176 on screen. What is to keep them from just saving THAT data to the 300k file and tossing the rest of the information that is not used? Or, could they be doing something sneaky and actually do a compression on the file? I can Lharc up files and save as much as 95% on space. Couldn't that be done with a 24 bit pic too? Find a Toaster, Render a pic, load it into DCTV and save as display file. Then reverse the process and look at the pic on the same toaster and compare it to the original file. THEN tell me I'm dreaming :) --------------------------------------- | patrick_meloy@outbound.wimsey.bc.ca | | 'The Outbound' BBS Vancouver BC | ---------------------------------------