Thanks Zach - ordinarily I'd use a similar script, but here there are quite a few images to preload, and so I'm keen to reduce the download time as far as possible.
Thanks Dave - I (now) understand the problem here, and also the principle of your solution. Unfortunately, even with your dummy page, I'm not up to coding these two functions to work with my images and page. Is there any (simpler) workaround, perhaps?
PS If they didn't know how, they should have...well, posted on a forum! (All those gems of wisdom, lost forever...its criminal.)
Another solution to this problem has occurred to me. I think I am right in saying that, at the moment, the preload script preloads all four of the images that make up i1 first, then the four images that make up i2, then all of i3, etc. Whereas in fact it would make much more sense to preload the first image of i1, then the first image of i2, then the first of i3, etc, and not preload the second image of i1 until all the first images have been preloaded, since this is the order in which the images are actually displayed. And though I'm not up to it myself, this should require only a small tweak to the existing script, rather than a whole new function. Am I right?
PS Dave, did you get my email at your consulting site?
I'm having a similar problem, but the funny thing is it doesn't seem to happen with NS7. Cyberchimp, i looked at your site with IE6 and left the home page open for about 10 minutes, enough time to pre-load w/ a dsl connection right? Well IE6 was sending requests every couple seconds as long as the page was open. Tried your site with NS7 and network activity stopped after about a minute.
I'm just trying to get a simple slideshow working on IE6, here is my latest attempt:
Thanks for taking a look, MrgSkier. I've tried your suggestion, but I get the same problem with my site whether I'm using IE5.5 or NN7. It SOUNDS like (your copy of?) IE is forcing each image to download afresh every time it is required. You used to be able to set this to happen at
Tools > Internet Options... > General > Temporary Internet Files > Settings...
though I'm not sure whether this is still the case - all the options I have now look uproblematic. What setting do you have here (I have the default 'Automatic' setting).
Regarding your slideshow: here I exerience exactly the same problem as you. With NN7 the images all preload happily enough, and then display as soon as I hit the Next button. With IE5.5 though each image has to download EVERY time I hit the Next button. I'm afraid I wouldn't know where to start here - Dave is probably your man...
It would seem that one of two or more things could help you with this problem...
some of those teeny tiny 45 x 45 pics were upto 5.5k and were actually 95 x 95!
need to compress those pics with, as i've found to be the best, macromedia fireworks. i bet you could get the download time/filesize down to 1/3 of the current, if you size them to 45px maybe more.
Not to sound like an advocate, but it would work well, maybe if you put those pics and coding into a flash (*.swf) file you could loop the whole as though it were an animated gif--with a very small footprint.
Thanks very much for taking a look, smallmuscleshir, and for taking the effort to examine the images and code. In fact ALL those images that display at 45 x 45 on the index page (and in the 'Gallery Credits' page) are actually 95 x 95. There are two reasons for this:
(1) They are displayed full size elsewhere on the site (in the 'Revolving Gallery' at the top of each page). By preloading (some of) them here (and 'preloading' all of them on the 'Gallery Credits' page) I'm able to speed up the download of subsequent pages in the site.
(2) There are 60 plus of these images in total (and rising) and I wanted to be able easily to change the images used in the 'animations' on the index page so that different artists can be 'showcased' from time to time.
I did ponder for some while whether this was the best way to proceed - I know that I COULD have made two different images (with different dimensions) for each piece of artwork, but overall this seemed like a less 'cost effective' method in terms of download times. What do you think?
The second point I mention above is also one of the reasons that I wanted to avoid Flash on this particular site. (The other is that the site is principally for academics, and I know from experience that many are using relatively old browsers that don't have Flash of any sort installed).
All images have been crushed ferociously using ImageReady - I'd be interested to hear how you found Fireworks and ImageReady to compare, in terms of image-crushing.
PS Dave, did you get my email to your Consulting site?
I copied one pic and simply opening it in mspaint took off some of the bandwidth girth, but then the third pic is using fireworks and sized it to a tiny 1.15k from the initial 2.53k. depending on just how you code it it could cut your time in half for the preload.<br><img src="http://www.smallmuscleshirt.com/example/your32.jpg"><br><img src="http://www.smallmuscleshirt.com/example/mspaint.jpg"><br><img src="http://www.smallmuscleshirt.com/example/macromediafireworks.jpg">
oh yeah, if you can cut the times for those 95x95's down like that... the the pics would be measurable in bytes rather than kilobytes after being cut down to 45x45 and you could make a layer positioned at say top=(-10000px),left=(-10000px) to still maintain your original plan of preloading your 95x95's only they won't hinder your primary pages performance because it could be in a frame, iframe, the divider could be dead last on the page etc....
Thanks for taking the time to experiment with my images, smallmuscleshir (though I'm afraid I was unable to actually access your efforts - the server seemed to be down when I tried). Rather than reduce the images in size (both in terms of weight and dimensions) I've attempted to preload them during the 'intervals' between each image swap (which, as it turns out, is more than enough even at their current bloated size). The latest version (still getting tweaked) is up now.
Have you found Fireworks to be more effective at crushing images than Image Ready? I'm never sure which to use...
anything to keep away from updating scripts is a pleasure! Yeah, in short, I find that fireworks alog. seems to do a better job compressing the file size and you have an almost unlimited number of variables that you can play with for what size/quality ratio your looking for. Of course the bigger the picture the more dramatic/impressive the difference in the compression alog. becomes... and you can also create you animated gifs with always on top layers as oposed to the usual base image that gets sheided by the new layer, good program! I'll try to post these pics here, however they are still on my server as well.
with fireworks @ 1.15k http://www.smallmuscleshirt.com/exam...afireworks.jpg - you can see a slight blur on it because I didn't really take the time to reset the smoothing, loss, or edging distortions. However since your are all the same size, if you did one to liking, you could batch the rest with that setting...