-
1. Re: image buttons in multi-state-object
Bob Levine Oct 28, 2014 5:27 PM (in response to Helene C. Gamper)For starters choose one orientation ONLY. That will cut it in half.
There is zero reason for two orientations and you¹ve just discovered one of
the many reasons not to have them.
-
2. Re: image buttons in multi-state-object
Bob Bringhurst Oct 28, 2014 10:44 PM (in response to Bob Levine)Do you have any Web Content overlays?
Have you tired adding articles one at a time to a different folio to figure out which article is bloating the folio?
-
3. Re: image buttons in multi-state-object
Helene C. Gamper Oct 29, 2014 1:03 AM (in response to Bob Levine)Thanks for your answer. However, I am not the one to decide whether to have 1 or 2 formats, it's a client magazine and the client decides if he wants to offer 1 or 2 formats to his readers.
-
4. Re: image buttons in multi-state-object
Helene C. Gamper Oct 29, 2014 1:10 AM (in response to Bob Bringhurst)I don't have any web overlays, no. Just normal URL links (In-App-Browser opens). I have 1 video file embedded (nearly 400 MB), so I am well aware of that. But 150 MB for the rest when it's only 3 articles (despite having 2 formats) seems a bit too much to me. I did add the articles to the folio once at a time, yes. And it is the article with the many buttons and MSOs (as seen in the screenshots above) that is so big. This is also the article with the video in it, but still. I have the feeling buttons or the images in the buttons are making the folio so big. I often do app magazines with approx. 15 articles and 3-4 videos embedded (200-300 MB per video!) and that is normally 650 MB or so. So comparing that with my 3 articles makes me wonder.
Do MSOs and buttons make a folio big, is that possible? Or is it the images in the 9 big buttons not being resampled correctly (even though the documentation - 2 links in my original post - say something else). When I export the article, I always export it as PDF and when looking at the loading bar, it says "saving as PNG". So that should mean that all my buttons are resampled, I don't have to worry about image file size and it's exported as PNG in the PDF. Hm...
-
5. Re: image buttons in multi-state-object
Bob Levine Oct 29, 2014 6:15 AM (in response to Helene C. Gamper)Pull the video out and see how large it is.
All images are resampled to 108 ppi in a PDF folio unless they¹re in an
image sequence or a pan and zoom. If those three articles are loaded with
MSOs and are image heavy it doesn¹t seem all that large to me with two
orientations.
-
6. Re: image buttons in multi-state-object
Helene C. Gamper Oct 29, 2014 6:24 AM (in response to Bob Levine)ok, will try that. Thanks very much for your help.
-
7. Re: image buttons in multi-state-object
iGeo Oct 29, 2014 7:53 AM (in response to Helene C. Gamper)Hi,
What is the size of your folio? Is it 2048x1536 or 1024x768?
I think 1024x768 pdf folio is enough.
What format did you use for slideshows? It seems to me that raster format makes folio size smaller than vector format does.
-
8. Re: image buttons in multi-state-object
Helene C. Gamper Oct 29, 2014 8:00 AM (in response to iGeo)The size of the folio is 1024x768, it's a pdf folio. I have only 1 full screen slideshow in it with only 2 images, that slideshow is vector.







