Thanks for pointing out Multi-Size images! That's a good idea to try!
I remember reading about it before purchasing jb pro, but for reasons unknown to me I completely ignored it ;-)

Steven @ Juicebox wrote:

I think your issue is a direct consequence of setting enableLooping="TRUE".

Yup, tried it. That is the reason for preloading No.9 after No.1!

Since I want to have looping that brings me to the next question: Can I tell juicebox somewhere "along the way" to enable looping.
E.g.: I start juicebox with enableLooping = "FALSE" and before the last image (or after the third image, or whatever) I tell jb to enableLooping = "True".

I have a gallery with sequentially named images (1-9). The gallery has autoplay with looping and the images are displayed accordingly.
Strangely my Browser (Chrome) loads No. 9 right after No.1.

The problem is, on slow connections loading image No. 9 takes away too much bandwidth, so each following picture is "late" and therefore not shown in the gallery (The gallery only shows the "picture frames" with thumbsnail dots and loops these).

You can see the loading behaviour in the attachment (simulating a slow connection):
http://www.pstoehs.at/Data/Unbenannt.JPG

So my question is: Can juicebox be adapted to tell the browser to load the images sequentially (by name)?

Unfortunatly this method also does not work. I might try setTimeout if necessary.

I have also resorted to smaller images already. This just is the No.1 performance parameter...

Anyway, one really anoying problem is the way the browser loads images. (...using Chrome at the moment).
Even thought the images are labelled in ascending order the browser ignores this and loads some images from the back of the gallery first. This blocks the needed images at the beginning, and so all other images come late, meaning I never see anything until the gallery cycles back to Image No.1.

Basically my problem is starting to go off topic and therefore I will start another thread for this.

Hi, thanks for the quick answer!

Unfortunatly your suggested solution 1 doesn't work. The gallery always starts playing without waiting for the images to load.

I tried some debugging: The toggleAutoPlay command works as expected. But the onInitComplete event does not seem to wait for images. I assume this event only checks that the gallery functions are ready, and not if the gallery content (= images) is loaded.

My assumption is kinda backed up by the description of the onInitComplet event: "[...] The Api is now available".

One more thing I'm not sure about, is the use of the config.xml file. As it contains the same statements...do I have to change anything in this file?

Hi there!

I would like to delay autoplay until the first image in the gallery is loaded. The problem is, with slower connections the images are not loaded fast enough and the gallery already starts playing "empty". So it can happen that the first image to appear is image 2 or 3.
(There is no need to load all images, but No.1 should definetly be available before the gallery starts playing)

I have relatively large images (~1MB) and I have adjusted Pre-loading to "ALL" since I have small galleries. I fully understand pre-loading and image size and I would like to keep it this way.

Any suggestions?

Thanks,
Patrick