Very big images sizes because of a "jpeg to png 32 bit to json" workflow?
Hey guys,
I'm struggeling with an issue for a long time now, that causes very big file sizes for images.
My HTML5 course is 1280 x 720 pixels, and therefore I have some images I use for the background. They are also 1280 x 720 pixels big.
What I figured out:
- The file size in the output is more than less indepented to the compression of the input jpeg image (for input png there is the same problem).
- While exporting the course you can notice in the dr folder that captivate first produces a new png file (32 bit) of the jpeg image, after a while it produce the json file.
For example I created a new blank project with one slide and one big image (1280x720px):
| Input file | passing file in dr folder | output file in dr folder |
|---|---|---|
| jpeg normal compression (0.2 MB) | png (1,6 MB) in 32 bit | json (0,7 MB) |
| jpeg high compression (0.05 MB) | png (1,3 MB) in 32 bit | json (0,6 MB) |
| jpeg high compression and small resolution + Rezise to 720p in Captivate (0.01 MB) | png (1,1 MB) in 32 bit | json (0.5 MB) |
In this example you can tell, no matter what you do, for a big image you get a big json file.
Is that because captivate produces this big png files with 32 bit first?
What is your strategies for this issue? Because I want to keep the file size as small as possible for mobile purposis.
Best wishes
Flo
