• Registered: 2012-12-24
  • Posts: 34

Topic: Bit bigger than 2500px files not importing - what has changed?

Any files which exceed 2500 px (jpegs) are being refused by juicebox and the error message is that they exceed to 4k px limit

Is this a bug which appeared with more recent versions or air (or something)? 

How can get round this and load up to the published 4k px file limit?

thanks

windows 10 (current updated)

  • Registered: 2012-04-24
  • Posts: 5,924

Re: Bit bigger than 2500px files not importing - what has changed?

As you have discovered, JuiceboxBuilder-Pro can handle images of no more than 4095px x 4095px when creating a gallery. This is a limitation of Adobe AIR (the platform on which JuiceboxBuilder runs). Adobe AIR uses Adobe Flash Player as its runtime environment and the largest image size which Adobe Flash Player can handle is 16,777,215 pixels. This equates to a square image of 4095 x 4095. Alternatively, if you have an image with one side being 2500, then the other side can be no more than 6710. Please see this web page for details.

As far as I am aware, this has always been the case (from the first version of JuiceboxBulder-Pro to the current version).

If your image are within these bounds, then perhaps you could upload one somewhere (perhaps to your own web site or a file sharing site such as Dropbox) and post a link to it so that I can try to replicate the problem myself.

If your images are larger than the maximum allowed resolution, then you could perhaps do one of the following.

(1) You could resize your images first in an imaging program (such as Adobe Photoshop) before feeding them to JuiceboxBuilder. (If you do resize your images prior to using JuiceboxBuilder, be sure to deselect the 'Resize Images' checkbox on the 'Images' tab to ensure that JuiceboxBuilder does not resize your images again.)

(2) There are plugins available to create Juicebox-Pro galleries with other programs (such as Adobe Lightroom, Adobe Photoshop or jAlbum) which do not have the upper resolution limit of JuiceboxBuilder. You can find details of these plugins here.
If you have any of the programs for which plugins are available, you might like to try creating your galleries with these programs as an alternative to JuiceboxBuilder-Pro.

  • Registered: 2012-04-24
  • Posts: 5,924

Re: Bit bigger than 2500px files not importing - what has changed?

I should also note that, unfortunately, there is a known issue whereby the error can be generated if the resize image dimensions are too large. This might be the reason for your problem.

The developers are aware of the problem and it has been logged as a bug so it should hopefully be addressed for a future version.
In the meantime, the only workaround is to reduce the resize dimensions until the error is no longer displayed.
I realise that this is not an ideal solution but, until the bug is fixed, there is no way around it (at least using JuiceboxBuilder-Pro).

I do not know the exact nature of the problem (why large resize image dimensions cause the error message to be displayed), but, having experimented with large images myself, the error seems to be triggered when the Max Width and Max Height both exceed a threshold value somewhere in the range of between 2364 and 2504.

If you need to create a gallery with images of a size that triggers the error, then the best course of action might be to do the following:
(1) Create a gallery with JuiceboxBuilder-Pro, using resize image dimensions that do not generate the error. This will at least generate a 'config.xml' file containing the imageURL entries.
(2) Create a set of images in a separate imaging program (such as Adobe Photoshop) at the required size and then copy them into the 'images' folder inside the gallery folder (overwriting the images originally generated by JuiceboxBuilder-Pro). Just make sure that the image filenames match the imageURL entries in the gallery's 'config.xml' file.

I understand that this adds extra steps to your workflow (and should not be necessary) but, until the bug is fixed, it might be the best option.

I hope this this at least helps to explain what you are seeing and provides you with a workaround.