
On my Linux system, the minimum delay is 0.5: convert -dispose none -delay 0.4 newton_%d.png -coalesce output0.4.gifĬonvert -dispose none -delay 0.5 newton_%d.png -coalesce output0.5.gifĬonvert -dispose none -delay 1 newton_%d.png -coalesce output1.gifįor some reason the images seem not to be displayed properly in my browser. So why is the expected gif twice as fast as the actual gif? The actual gif has less delay than the expected gif. convert.exe -dispose none -delay 0 newton_%d.png -coalesce output.gif Then I used coalesce to recombine the pngs into one gif. This surprises me, because I specified that each frame should have 0 delay.įirst I created 36 pngs by exploding the gif borrowed from Wikipedia: -caution: command generates 36 pngs On my browser (Firefox 17), the expected gif runs more than twice as fast as the actual gif. This is approximately the output I expect (courtesy of Wikipedia): I want this gif to loop as quickly as possible. I am using ImageMagick to turn a collection of pngs into a single gif.
