![]() 1.57 11.Nov.2009 gifsicle: Don’t throw away totally-cropped frames with 0 delay, since most browsers treat 0-delay frames as 100ms-delay frames. 1.58 14.Jan.2010 gifsicle: Fix optimizer bug reported by Dion Mendel. I also optimized the animations with Gifsicle, so they're quite a bit smaller than the original. gifsicle -O2: Optimize away entirely-transparent frames when possible. Here are two versions of the animation with 0.06 seconds per frame: fast (20 frames, 1.2 sec/loop) and slow (40 frames, 2.4 sec/loop). That should give consistent speed in all major browsers.Įdit: I went and did that for you. Added -no-warnings (-w) option to inhibit warning messages. Speed improvements in optimization and colormap quantization. It doesn't any longer furthermore, it will generate those kinds of transparent index, which can mean smaller colormaps and smaller GIFs. My recommendation would be to increase the per-frame delay to 0.06 seconds (and to remove every second frame if you want the animation to run fast). Gifsicle formerly ignored these transparent indices. ![]() And the cutoff for what counts as a "very short" delay varies between browsers: Firefox apparently accepts anything down to 0.02 seconds per frame, while IE ignores delays below 0.0 6 seconds per frame. The problem seems to be that many browsers will ignore very short per-frame delays and replace them with a default delay (often 0.1 seconds). That should give it a nominal runtime of 1.2 seconds per loop, which matches what I'm seeing here in Firefox. Your GIF animation contains 40 frames, with a 0.03 second delay specified between each frame.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |