Please note that this article is not complete as it cannot contain the required images. Please visit the associated journal to see the required images.
You've had the idea, you've built your emotes, you've put them all together in an animated GIF which you upload for the world to enjoy. The comments start coming in; "Sweet", "Cute", Love it", "Why is it so slow?". All well and good, apart from that last one.
So you take a closer look and either:
So what's the problem? The answer is Stupid Browsers. Simple as that. Our browsers are just rubbish at rendering fast animated GIFs.
An animated GIF file consists of a number of image blocks, each with it's own control block. The control block includes how long (in 1/100s of a second) the image should be displayed before moving on to the next image.
The GIF Programming Reference[1] has this to say about the frame delay:
and
All very simple, the rendering engine should simply wait for the specified delay before moving on to the next image. No exceptions! A delay of 0 should be interpreted as instantly displaying the next image and is of no practical use for creating animations. Some programs, JASC Animation Shop for example, will not allow a 0 delay. As each frame in a GIF can have it's own local colour map, some programs have even used the 0 delay to create static GIFs with more that 265 colours[2].
Imagine a series of animated GIFs that all show a progress bar. These GIFs are identical except for the frame delay. The first has a delay of 1/100 seconds, the next has 2/100, the next has 3/100, etc. When the first bar has finished the second should be half finished, the next only one third finished, etc. If you took a screenshot you should see this:
Sorry, image not available in this news article
So that's the theory. After a number of people had mentioned problems with their animations being slower than they had build them, I decided to investigate and put together a test page containing the GIF progress bars described above. I then loaded this test page into a number of browser/OS combinations to see what happened. What I found was a remarkable example of piss poor programming.
The figures below show screenshots of the test page displayed by various browsers on different platforms (this test page is available here - you may find this test works best if you download it and run it locally).
Sorry, images not available in this news article
If all the browsers followed Safari's example and just stopped making the delays faster then there would not be too much of a problem. If you ask Safari for a delay of 1/100 seconds and it delivers 3/100 then the animation might not be as fast as you wanted, but it will probably be fast enough. However, asking Internet Explorer and the Mozilla browsers for 1/100 and getting 10/100 is a significant problem.
So what delays should you use when animating GIFs? Well never 1/100 or 0; imagine what would happen if one of the popular browsers decided to honour the 0 delay! As over 2/3 of visitors[3] are using Internet Explorer I'd suggest not dropping below 6/100. If you really need to go faster than that (and I have seen a few emotes that were stunning at 2/100 in Firefox) then make it clear on your description what browsers it is suitable for. If you're feeling generous then you could always provide an alternative IE version.
Never, never, never use delays of 0 or 1. Avoid 2 - 5 if possible.
1. GRAPHICS INTERCHANGE FORMAT Version 89a www.w3.org/Graphics/GIF/spec-g…
2. Wikipedia's GIF entry describes True Colour GIFs en.wikipedia.org/wiki/Gif
3. Browser share data provided by leSicilien
The Problem
You've had the idea, you've built your emotes, you've put them all together in an animated GIF which you upload for the world to enjoy. The comments start coming in; "Sweet", "Cute", Love it", "Why is it so slow?". All well and good, apart from that last one.
So you take a closer look and either:
a) you scratch your head and think "it wasn't that slow when I built it"
b) you think it looks fine but other people are still saying it's slow
So what's the problem? The answer is Stupid Browsers. Simple as that. Our browsers are just rubbish at rendering fast animated GIFs.
The Theory
An animated GIF file consists of a number of image blocks, each with it's own control block. The control block includes how long (in 1/100s of a second) the image should be displayed before moving on to the next image.
The GIF Programming Reference[1] has this to say about the frame delay:
Process each graphic in the Data Stream in sequence, without delays other than those specified in the control information.
and
Delay Time - If not 0, this field specifies the number of hundredths (1/100) of a second to wait before continuing with the processing of the Data Stream. The clock starts ticking immediately after the graphic is rendered.
All very simple, the rendering engine should simply wait for the specified delay before moving on to the next image. No exceptions! A delay of 0 should be interpreted as instantly displaying the next image and is of no practical use for creating animations. Some programs, JASC Animation Shop for example, will not allow a 0 delay. As each frame in a GIF can have it's own local colour map, some programs have even used the 0 delay to create static GIFs with more that 265 colours[2].
Imagine a series of animated GIFs that all show a progress bar. These GIFs are identical except for the frame delay. The first has a delay of 1/100 seconds, the next has 2/100, the next has 3/100, etc. When the first bar has finished the second should be half finished, the next only one third finished, etc. If you took a screenshot you should see this:
Sorry, image not available in this news article
The Truth
So that's the theory. After a number of people had mentioned problems with their animations being slower than they had build them, I decided to investigate and put together a test page containing the GIF progress bars described above. I then loaded this test page into a number of browser/OS combinations to see what happened. What I found was a remarkable example of piss poor programming.
- Mozilla's rendering engine seems to have taken the line that, as screens cannot refresh faster than 90Hz, no one will ever use a delay of 1/100. So a 1/100 delay is changed to 10/100. Not what you asked for. Mozilla's answer to the 0 delay is to ignore the specification and use a delay of 10/100.
- Internet Explorer is even worse. Any delay less than 6/100 is changed to 10/100. This is probably based upon the assumption that if 15fps is good enough for cartoons then it's good enough for animated GIFs.
- Opera is the worst of all. Every delay below 10/100 is displayed at 10/100.
- Safari is the best as far as delay cropping is concerned. It does crop below 3/100, but it crops to 3/100, not back to 10/100.
The figures below show screenshots of the test page displayed by various browsers on different platforms (this test page is available here - you may find this test works best if you download it and run it locally).
Sorry, images not available in this news article
Conclusions and Recommendations
If all the browsers followed Safari's example and just stopped making the delays faster then there would not be too much of a problem. If you ask Safari for a delay of 1/100 seconds and it delivers 3/100 then the animation might not be as fast as you wanted, but it will probably be fast enough. However, asking Internet Explorer and the Mozilla browsers for 1/100 and getting 10/100 is a significant problem.
So what delays should you use when animating GIFs? Well never 1/100 or 0; imagine what would happen if one of the popular browsers decided to honour the 0 delay! As over 2/3 of visitors[3] are using Internet Explorer I'd suggest not dropping below 6/100. If you really need to go faster than that (and I have seen a few emotes that were stunning at 2/100 in Firefox) then make it clear on your description what browsers it is suitable for. If you're feeling generous then you could always provide an alternative IE version.
Summary
Never, never, never use delays of 0 or 1. Avoid 2 - 5 if possible.
References
1. GRAPHICS INTERCHANGE FORMAT Version 89a www.w3.org/Graphics/GIF/spec-g…
2. Wikipedia's GIF entry describes True Colour GIFs en.wikipedia.org/wiki/Gif
3. Browser share data provided by leSicilien
).
but I suspect I would have had to shave my head to match the riders 
.
). Some software does not seem to support comments at all (I'm looking at you, Fireworks 
).
Like my new avatar? 
:origin()/pre00/2596/th/pre/f/2014/127/e/6/portrait_preparation_tutorial_by_thewholehorizon-d7hefqc.jpg)
:origin()/pre00/86ab/th/pre/f/2010/349/c/6/expressions___intro_by_mistytang-d34xbrb.jpg)
:origin()/pre00/a361/th/pre/i/2014/066/8/b/mbti__how_to_function___how_to_guide_to_functions__by_lpskippy-d79c7wr.jpg)
:origin()/pre00/162b/th/pre/i/2013/088/9/9/moonlight_highlight_shading_tutorial_by_diamermaeani-d5zribf.png)
:origin()/pre00/ca6a/th/pre/i/2014/090/3/a/wine_notes_ref_by_xenalollie-d70jefz.png)
:origin()/pre00/3829/th/pre/i/2014/252/2/2/envy_ref_sheet_by_xenalollie-d7yj8dk.png)
:origin()/pre00/0834/th/pre/i/2014/151/1/1/blind_eye_ref_sheet_by_xenalollie-d7kfhed.png)
:origin()/pre00/8ddc/th/pre/i/2016/162/e/c/phae_ref_sheet__open__by_xenalollie-d7n91dt.png)
:origin()/pre00/4355/th/pre/i/2014/272/9/b/mutt_ref_sheet_by_xenalollie-d811yud.png)
:origin()/pre00/f3d3/th/pre/i/2014/196/d/5/lollie_goat_by_xenalollie-d7qrw45.png)
:origin()/pre00/3889/th/pre/i/2015/119/b/8/icecream_cat_by_xenalollie-d8rhdjl.png)
:origin()/pre00/3561/th/pre/i/2015/089/7/a/yeen_kid_by_xenalollie-d8ns1el.png)
:origin()/pre00/c60f/th/pre/i/2016/161/9/6/boulder_opal_by_xenalollie-d8m14ye.png)
:origin()/pre00/d225/th/pre/i/2015/103/c/1/3000__done_time_by_xenalollie-d8pnft3.png)
![.:Reference Sheet: Sabil:. [main alter] by maitoenkeli](https://t00.deviantart.net/iEsaOGcNKaLvJVemozRNn9LFAqs=/300x200/filters:fixed_height(100,100):origin()/pre00/a845/th/pre/f/2014/236/2/a/__reference_sheet__sabil____main_alter__by_nix_wingedone-d7kcgff.png)
:origin()/pre00/9aab/th/pre/f/2007/275/a/9/emoticon_tutorial_by_jamaal10.jpg)
:origin()/pre00/0cd3/th/pre/f/2007/041/f/3/emoticon_faces_by_dumnezeu.jpg)
:origin()/pre00/3937/th/pre/f/2011/006/3/5/emoticon_shading_tutorial_by_ledmaiden-d36k6fe.png)
:origin()/pre00/ca9b/th/pre/i/2011/150/2/b/___dark_splitter____by_darkeagle2011-d3hkwz2.jpg)
:origin()/pre00/765a/th/pre/i/2011/259/e/2/ivory_glass_by_deviantria-d4a1683.png)
:origin()/pre00/2f34/th/pre/i/2009/289/2/9/windows_7_glowing_logo_by_yaxxe.png){kind=logo}
:origin()/pre00/748a/th/pre/f/2016/365/9/3/93f99a906ba6a730cc767dbf39eeb1ad-datjzku.png)
:origin()/pre00/470f/th/pre/i/2010/345/6/8/android_smartphones_icon_pack_by_davinci1993-d34nkzu.jpg){kind=icon}
:origin()/pre00/d90c/th/pre/i/2012/160/1/1/boot_directly_to_desktop___windows_8_by_dm_moinmoin-d52tr5z.png)
:origin()/pre00/e33e/th/pre/i/2012/052/0/e/windows_freaks_v1_by_arceusdazown-d4q86vm.jpg)
:origin()/pre00/5ba1/th/pre/i/2003/6/7/c/emoticon_tutorials_-_animation.jpg)
Anyone able to verify that?
I tried 0.01 and was getting the same result. After reading your thread I tried 0.03, so at least people with safari will get the full effect..and guess what. Mozilla Firefox 2.0.0.4 renders 0.03 second delays!!!
mytest [link]
offtopic: if anyone knows the author of the original sexy robot girl picture, please let me know!
How about artists like =sereneworx though? His emoticons seem to be utilizing a fast animation speed without too many problems on Firefox (and perhaps Internet Explorer). Is it a similar situation with the Peacock Display emote?
In any case, great job *humpy77, yet another great article!
If you let me know which of your animations you're having this problem with (and what browser you're using) then I'll see if I can spot any problems.
I have noticed, however, that when I use Adobe ImageReady, my uploaded emotes move as fast as they do when I optimize and save them as GIFs, which is the speed I want them to be.
I've watched both your GIFs in FireFox 2, IE7 and Jasc Animation Shop and they all ran at similar times (with the browsers running a little slower than JAS).
It sounds as if Fireworks may be running slower than it should. You could try a little test by building an animation that has something like 100 frames with a 0.10 second delay. This should loop every 10 seconds so you could time how long it takes in Fireworks. You could also try asking some people who use Fireworks if they've seen the same problem.
Hope this helps
I really appreciate the help and advice! Thanks!
and also its worth noting that older versions of internet explorer play all gifs on the same page at the same framerate (I dont know how it decides what framerate, but its usally pretty crap)
I'll bet those older IE versions were chopping at 0.10.
Anyway, stuff it all! I'm starting to think that Flash is needed for anything that wants fast, accurate timing.
this is as most animations and stuff in flash is rendered in realtime, so the performance between differnent computers can vary much more than gifs in browsers.
like all things you just have to balance it all out, if you want to be really sly though you make the animation first, and just put the frames in flash, but then you have to play with your compression...
hmmm, one day you think they will make something that is surefire?
Well, animation rendering engines aren't exactly a competitive field so I'd guess there's not much development happening. For example, the MNG specs have been out for 6 years and got nowhere. The GIF format should be fine (for small scale work) if the developers bothered to follow the standard. Flash is probably the way forward as it's come from one source that produces it's own (reasonably consistent) implementations.
Good investigative work.
So the rule would be;
Never, never, never "no delay" or 0.01. Avoid 0.02 - 0.05 if possible
The alternative option would be to use swf. Adobe are claiming that 98% of web users have Flash Played installed ([link]) so this is now a viable option. You just have to have a look at something like Bertie ([link]) to see how good flash can be.