The saver checks for the existence of gif-tables and flips into a special save mode (save GIF source as GIF).We could attach many tables and record frame numbers, but that sounds like a lot of work for probably very marginal gain. If there is a single global table, it attaches it as metadata, eg. In this case, you probably would want to recompute the colour tables. For example, a watermark might be drawn on a few frames. The difficulty comes if processing is more than a simple resize. The encoder could then just reuse that rather than finding a new table - at least the result would be no worse. Something we discussed a few months ago is getting the GIF decoder to attach the colour tables from the source image. Yes, resizing will make new in-between colours, since it effectively averages pixels. Hi thanks for these interesting examples. LCDF Gifsicle Found you a couple examples! □ But that filesize difference is quite a bit, especially because the source is only 570KB. Using gifsicle: gifsicle -resize-fit 1400x_ -o test_gifsicle_out.gif test.gifĪgain, Gifsicle's image is not as nice looking. This is a 570KB file, and if I run it through vips to resize to 1400px wide: vipsthumbnail "test.gif" -size 1400 -o test_vips_out.gif ![]() Gifsicle returns a less nicer-looking image, but it's ~1MB: gifsicle -resize-fit 200x_ -o example_gifsicle_out.gif example.gif Vipsthumbnail (using cgif) returns a 3.5MB image: vipsthumbnail "example.gif" -size 200 -o example_vips_out.gif This doesn't seem to be the case for all gifs, but i haven't been able to figure out why it's seemingly much worse for some files. I have a few example gifs that seem to really increase in filesize when run through libvips.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |