Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!uw-beaver!cornell!batcomputer!itsgw!steinmetz!uunet!wucs1!wuphys!lel From: lel@wuphys.UUCP (Lyle E. Levine) Newsgroups: comp.sys.amiga Subject: Re: dilbm/pilbm/movie: a problem and a workaround Message-ID: <555@wuphys.UUCP> Date: 21 Jun 88 18:50:54 GMT References: <25962@bbn.COM> Reply-To: lel@wuphys.UUCP (Lyle E. Levine) Organization: Physics Dept., Washington U. in St. Louis Lines: 23 In article <25962@bbn.COM> denbeste@BBN.COM (Steven Den Beste) writes: > >Well, the bottom line is this: The documentation DOESN'T tell you that these >programs can only process 320*200 HAM COLOR and 320*400 HAM COLOR and get very >very confused by any other format - but they don't check, they just blow up. >(Actually, dilbm will process anything, it is just that the result doesn't make >any sense. pilbm isn't using the data - it just concatanates it together. movie >tries to open a screen and fails but doesn't tell you why.) > I have used dilbm and pilbm quite a bit and never had this problem. The frames must have the same resolution and palette but that's it. I have used 640x400x4, 640x400x3, 640x400x2 with no trouble. HAM is not necessary. The animations get rather big sometimes (one I made is over 2 Meg in size) but the process works great (if a bit slow). ========== IBM is a Division of Sirius Cybernetics Corporation "their fundamental design flaws are completely hidden by their superficial design flaws." - "So Long And Thanks For All The Fish" Lyle Levine: Paths -> ihnp4!wuphys!lel Best way: (314)889-6379 uunet!wucs!wuphys!lel