Possible Bug in ID5.5 When Exporting Images to ePub

Just wanted to relate my experience with exporting images to ePub in InDesign CS5.5. I've already spent the better part of two weeks trying to find a resolution for the problem with Adobe's customer service techs in India. Nice guys, but so far not of much help.
Here's the problem. when exporting ID documents to ePub, and you're selecting your options in the "Image" export dialog box, you are offered two choices: "Fixed" and "Relative to Page." In theory, "Relative to Page" is the best choice because this means your images will be automatically scaled for the different viewing devices (i.e. iPad, Kindle, mobile phone, laptop). If you select "Relative to Page," however, your images will export with pixilation.
This may not happen to everyone, but it happened to me, as well as the last tech I spoke in India. I'm using a MacBook Pro running 10.6.7. Don't know what he was using, but he got the same results on his end when exporting an image to ePub using "Relative to Page." For me, the fonts look especially horrible in Adobe Editions. If you select "Fixed," they'll export just fine, (looked great in Adobe Editions and Kindle Previewer), but don't know how fixed size renders in the different devices.
This particular exchange was last Friday. The tech verified that we had a problem he couldn't solve and told me he had to speak with his "senior," who had already gone home for the weekend. I received an email today informing me that all I had to do was select the high quality performance settings in ID, and the image would look "pretty" while the file was open in the program. Really? I mean, duh. What does that have to do with the EXPORT problem?
And yes, I know to select the maximum quality setting in export. I'm a photographer who has used Photoshop since the 1990s. Used InDesign, QuarkXpress, and Pagemaker, in reverse order for that long as well, so I know how to prepare a file for print and the web. The techs I've spoken with have assured me I'm selecting the correct settings. Program has not only been uninstalled and reinstalled, but I went the extra drastic step of wiping my harddrive and starting over. No third-party plug-ins installed that didn't come with the original Adobe software. Have the latest ID update. The problem simply doesn't have a solution in my case.
Oh, well. As I say, nice guys, but this is my third time speaking with tech support about a problem with Adobe software. Not going to try again. IMHO, the customer service system/process could use some work.

As I said, it may not happen to everyone. Perhaps with a different operating platform or system version it may not happen. I was only reporting it because it happened to not just myself, but to the tech half a world away who shared my screen, saw the problem, and recreated it on his own machine/system.
Here are the selections in the ePub Export dialog box that caused the problem. I can't imagine that what is selected for TOC settings or other non-image settings would have to do with it, but here they are.
1. File > Export > Choose ePub as Format
2. In ePub dialog box: General Settings
Include Document Metadata checked
ePub Cover, you can select Rasterize first page or Use Existing Image File, makes no difference
Ordering, Based on Articles Panel
Formatting Options: Leave as Default
3. In ePub dialog box: Image
Preserve Appearance from Layout checked
Resolution, doesn't matter what you select, all produces the same result
Everything in the first section below this is as default
Image Conversion: JPEG (I've been using JPEG, but also tried it with a TIFF, and even a Photoshop file, no difference)
JPEG Options: Maximum, Progressive
Ignore Object Export Settings: I usually have this checked, but have tried it unchecked, and it made no difference
4. In the ePub dialog box: Contents
Format ePub Content: XHTML
Use InDesign TOC Style checked (I've tried the default, and my own TOC style, no difference)
CSS Options: I've tried Generate CSS and Use existing CSS template, never used Styles only. Made no difference
5. Click OK.
If you need what I do from the beginning...
1. New file: Print (not web, which tends to not honor the HTML tags on export). I typically chose 1024 x 768 because that's the screen resolution for an iPad.
2. Command-D, place file. I've tried JPG, TIFF, even Photoshop files of varying resolutions from 72 to 300. Files sizes from 800x600 to 1024x768 to sizes approximately double this. No difference.
3. Drag cover to Articles Panel and name.
4. Layout rest of eBook, etc.
5. Display performance settings while in ID are set to High Quality.
6. Triple check for errors (always a green light before exporting).
These are ePub files that have validated, after fiddling with the CSS and XHTML file, as necessary, of course. I don't mess with any image coding.
That's the steps!

Similar Messages

Hi there! So I am using Lightroom 3 on a pc and I have ran into an issue when exporting images. The DPI and image size (in inches) that I am selecting during the export process. For example I just exported a collection and set the dpi to 180 and the size

Hi there! So I am using Lightroom 3 on a pc and I have ran into an issue when exporting images. The DPI and image size (in inches) that I am selecting during the export process. For example I just exported a collection and set the dpi to 180 and the size to 7 inches on the long edge. My exported result is 457 dpi and sized at 3200x2134 pixels.. Any ideas on why this is happening and what I can do to correct it?

The DPI setting in a digital image has no meaning at all. You need to learn how to calculate what you need in your exported image. The only measurement in a digital image that has any meaning is the number of pixels in each direction. It doesn't matter what you set that DPI to (actually it's PPI or pixels per inch). The image will have the same number of pixels regardless of the setting. If you need an image that is 5 x 7" (for example) at 200 PPI then you would want an image that measured:
5 x 200 = 1000 pixels
7 x 200 = 1400 pixels
So you would need an image that is 1000 x 1400 pixels to have a 5 x 7" image at 200 PPI. The reason your exported image had such a high PPI setting is because you specified the number of inches you wanted the image to be. And there were enough pixels in the image that it calculated out to be that high PPI setting.
I apologize, I don't explain this very well. But you need to learn to do the math to determine how large you really want your exported images to be.

GPU acceleration not working when exporting images on Lightroom CC

I was monitoring CPU & GPU while exporting a timelapse sequence:
As you can see, GPU is idle when exporting images - CPU does all the work. So GPU is used only when moving the sliders in the Develop module for a fast preview of an image you are working on, but for export it isn't used.
What's your opinion? I'd like to have exports accelerated too. I was hoping for it. Exporting timelapses is really time consuming.
Adobe pls?

I couldn't find the Cuda-Supported-Cards.txt file at first, didn't know about right-click .app file "show package contents", but then found it. I also searched for the hack and some people said delete the file, others said add your Graphics cards to the file, others said add your graphics card to the the Opencl_supported_cards.txt file. I added my card to the Cuda-Supported-Cards.txt first, and it didn't work. I left the graphics card in that file, but also added it to the Opencl_supported_cards.txt file and now it works. Thanks so much.

Progress gauge or bar when exporting images

Hi,
am I missing a viewing option? When exporting images within Aperture the sprocket is spinning indicating that the images selected are being exported.
However,
I would like to see some type of a specific status during exporting, such as"
+"Exporting image 1 of 500, 2 of 500, etc.+
Is this available?
Thanks,
Michael

"Window→Show Activity" will provide some more information. You can bring up this window by clicking the spinning sprocket.

What resolution does Pages export Images to EPUB?

I was wondering what resolution Pages09 Exports images to EPUB (which are then readable in iBooks2?)
In other programs from Adobe and others you can control the Image conversion Resolution before you Click "Export" to EPUB?

I agree it isn't very helpful...but that is all I have been told. Still trying to fiond out what the projector resolution is.
I am using a fit within...but everything I am reading about projectors tells me I should be able to use higher resolution for a projector. This is more of a Foto Magico question as it pertains to images coming from Aperture.
It is less the image resolution and more the slideshow settings I am trying to figure out. Maybe this is not the right place to post... Thanks Frank.

Aperture 1.5 Extremely slow when exporting images

Has anyone else found Aperture 1.5 very slow when exporting versions. It took about 25 minutes to export 9 images (12mp Eos 5D files) as full resolution Jpegs. They had various afjustments applied to them, but the length of time to expot seemed rediculously long. I don't recall this task taking as long in previous versions.
Does anyone know of anything that might be slowing this down? Would turning previews off help - although they had finished processing before I started. Help in this matter wouyld be appreciated
Thanks

I'm experiencing this same behavior. Exporting is ridiculously slow. Actually editing the image doesn't seem so bad, but I guess it's just doing a preview at this point and not committing the change? Seems odd as I browse back to an image I've changed and the preview is instantly up with all changes applied...
I'm playing with the trial version now, I'd really like to buy it, but the speed is completely unaccaptable on export, or large file operations.
iMac g5 1.8 ghz, ALS, ATI 9600 card. 2 Gig of ram. Nothing else running.
Photoshop is much, much faster, even batching. I realize aperture uses GPU heavily, and my GPU is not up to snuff, but when making changes to an image ... it's not bad! It's a little sluggish at times, but most changes are near real time. It's just exporting and importing that takes far far far too long.
Any possibility of a preference to offload more work to the CPU? Lightroom, Photoshop, etc do just fine, but Apertures library management is something I'd really like to purchase and keep!

Errors when using "Limit file size to" when exporting images

When I try to use the "limit file size to" option in Export, I often get at least one image that doesn't export, and I get a dialogie box like the image attached here:
As I am exporting in batches, it geats really messy and risky too!I have tried various file size options but that doesn't seem to be a factor.
Any ideas on solving this, or is it an unfixed Lr bug?!
thanks in advance

I can't reproduce it here, so you could try trashing the preferences file http://members.lightroomqueen.com/index.php?/Knowledgebase/Article/View/1148/198/how-do-i- delete-the-lightroom-preferences-file
If that doesn't do the trick, post it on the Official Feature Request/Bug Report Forum

Photoshop CC crashes when exporting image to PDF file

Hello all,
I have recently started using PS, and when I attempt to save an image as a PDF, it makes it to about 97% and leaves a temp file, but crashes before it can complete. I have provided a copy of the crash log below:
Faulting application name: Photoshop.exe, version: 15.2.2.310, time stamp: 0x5480338c
Faulting module name: Photoshop.exe, version: 15.2.2.310, time stamp: 0x5480338c
Exception code: 0xc0000005
Fault offset: 0x0000000001c3f519
Faulting process id: 0x3a30
Faulting application start time: 0x01d05949d5314c48
Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
Faulting module path: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
Report Id: 30aba519-c53d-11e4-beb2-d43d7e97baf1
Faulting package full name:
Faulting package-relative application ID:
I have already updated, re-installed, rebooted, and run both a disk check and memory check (as c0000005 can indicate possibly failing hardware), but to no avail. All my video drivers are up to date, as I have seen that recommended in several other places. I am running an 8.1 system 64-bit. Any assistance would be greatly appreciated.

What PDF preset are you using? If high quality print, try flattening the image, and saving again. If that works, then it might point to something fonts. Obviously a flattened JPG is entirely useless as a PDF file, so it needs fixing.
When Chris Cox (Senior Adobe Computer Scientist — apparently several steps up from a rocket scientist) finds this thread, he is probably going to tel you that your truncated crash report doesn't tell him anything.
Fonts — Troubleshoot
Troubleshooting Steps to Fix Most Issues

Problems with image names when exporting - images that have come back into lightroom from photoshop

Can anyone help ? When I need to take an image from lightroom into photoshop then back into lightroom and then I export that image, the original file number disappears and is replaced by dashes. Does anyone know how to solve this ?
Thanks !

The appearance of dashes usually suggests some kind of pre-set e.g.
Wedding-20150106-0001.jpg
The only suggestion I can make is that you check to ensure you are using the correct parameters in the templates manager.
Photoshop Lightroom Reference Guide | Create Your Own Custom Filename Presets | Peachpit

Possible "pitch/synchronization" problems when exporting

I have a video that I edited in Adobe Premiere Pro, with a Sequence setting of 23.976fps... in the editor, when I render it and play it back... it plays back beautifully. Just the way I want it to.
I exported it as an MP4 file (with NATIVE fps, 23.976) and uploaded it to Vimeo, and played it there - and I SEE that it's off.
The way my video is edited is very fast, and relies heavily on Audio/Video synchronization, it's the WHOLE point of my video.
In Vimeo - I can SEE that it's off. The video is just a few milliseconds lagging. It's not catastrophical, but spending a month editing and playing it back over and over again in Premiere Pro, I pretty much know how it should play out... and the moment I saw it playback on Vimeo, I spotted this slight un-synchronization. The audio is slightly faster than the image that is supposed to be in synchronization with that audio effect
Is this a frame rate problem or am I exporting it wrong?
My Adobe Premiere Sequence settings are
[quote]Sequence 01
1920 x 1080
00;20;26;11, 23.976 fps
48000 Hz - Stereo[/quote]
when I right click on the actual audio IN the timeline the settings are
[quote]Source Audio Format: 44100 Hz - compressed - Stereo
Project Audio Format: 44100 Hz - 32 bit floating point - Stereo
Total Duration: 00:04:39:37476
Average Data Rate: 39 KB / second[/quote]
Can anyone tell me if there's something I'm doing wrong?
the 44hz, and the Sequence 48Hz are different, yes... but why is it when I play it back rendered in Premiere that it syncs perfectly then? or does the problem lie in something else?
Again for reference, my video is very experimental, the cuts are very fast that sync with the sound.

Hate to bring up an old thread, but this is EXACTLY the same type of issue I am always having, and rather than be accused of not doing a search, I thought that I'd reply to this and see if any can give some insight.
I'm in the exact same situation where the type of edits that I do are critical in syncing audio and sfx to visual cues in the video. As the OP mentioned, I spend countless hours getting things just right on the Premiere timeline, only to have things be not quite right on export...regardless of format it seems.
The bigges then I'm thinking is the root cause is the fact that many audio sources are different. Most music from CDs or online are in 44kHz whereas default sequences in Premiere are in 48kHz, as well as audio from video cameras.
It's really difficult to understand what is the "proper" workflow when working with 48kHz and 44kHz to ensure that WYHIWYG (what you hear is what you get), on export.
Is there anyone that can explain or point in the right direction to solve this issue?

Transparency Issue when exporting Image Sequence

Hi,
I'm creating short anims which have transparency and exporting them as png image sequences. I'm finding two issues with the export though:
1) The first frame is always solid black (when it should be totally transparent)
2) The R,G,B channels of each image are multiplied by the transparancy. So for example if I want a shape that's 50% transparent and coloured red the png should be 255,0,0,127 (R,G,B,A). In fact what After Effects is creating is a shape that's 127,0,0,127 (R,G,B,A)
Does anyone know what this issue is and how to solve it?
thanks
Paul

You should not have any problem with PNG as you have no choice but to have the alpha to straight (it's on of the only codecs that doesn't support premultiplied). Do you have the same problem is you select tiff sequences (LZW compression if you don't have much free space).

Doubts when exporting images

I've been working in a project to release the books of the company I work for to tablet, but we're facing some doubts and I'd like to know if someone can help me.
For example, we have a course that has 9 levels, which one with 12 books. Each book has different images in general, but 2 of them are repeatdly showed in each lesson. So, regarding this 2 last ones, we're going to have to export 2 x 12 = 24 / 9 x 24 = 216 images, when I think that the best practice will be export only 24. Can I do that? I mean export the images when it's is going to be in a different folder from the original one, not the same folder of the lesson that it belongs?
Another question is: what is the benefits or the problems when we export the book in one single package or doing this lesson by lesson?
Thanks in advance and sorry for my english.
Herminio

You have "Highlight Hot and Cold Areas" turned on.
Toggle this on/off from the View menu.
Thresholds are set at "Aperture➞Preferences➞Advanced". (I have mine set to 100% ~ it's not clear what the scale is.)
Message was edited by: Kirby Krieger

Possible bug in ccfe when using Apache STL

Environment details:
Solaris 10 @ patch version 148888-03
Sun Studio 12.3 (5.12, 2011/11/16)
I'm attempting to get boost 1.54 to build with this version of Sun Studio. I ran into a number of issues when trying to get it to build with stlport4 (let alone the default STL implementation) and decided to try the apache STL.
At one point when trying to build boost I ran into an error and as I delved into the problem I've discovered something extremely weird. I've been unable to reduce this to a simplified example, so I'll apologize ahead of time when I say you'll need to get the boost source code to see this happen. Here's the steps:
~ cd /tmp
~ gtar xf ~/Downloads/boost_1_54_0.tar.gz
~ cd boost_1_54_0/
~ BUILD_COMMAND=CC -library=stdcxx4 -I. libs/log/src/process_id.cpp
~ ${BUILD_COMMAND} -c
"/usr/include/stdcxx4/loc/_num_put.cc", line 67: Error: The prior declaration for std::num_put<std::_CharT, std::_Iter>::~num_put() has no exception specification.
1 Error(s) detected.
That build command is clearly simplified from what it would've been during a normal boost build, but since it reliably reproduces the error I've omitted the rest of the flags.
My environment is pretty clean; I'll quote variables that could be considered relevant:
~ env | ggrep -P 'PATH|SHELL|LANG|HOSTTYPE|OSTYPE|VENDOR|MACHTYPE|LC_TIME|LC_CTYPE
PATH=/opt/csw/bin:.:/usr/bin:/bin:/usr/local/bin:/bin:/sbin:/opt/sfw/bin
LANG=C
OSTYPE=solaris
VENDOR=sun
MACHTYPE=sparc
LC_CTYPE=C
LC_TIME=C
I'll demonstrate what I consider odd below; it'll probably be more clear through shell examples than from me describing it. Wherever you see ${BUILD_COMMAND}, it's the same as above:
~ ggrep -lRIP '_num_put.cc' /usr/include $(gfind ${SUNPRO_INSTALL_PATH}/ -type d -name include)
/usr/include/stdcxx4/loc/_num_put.c
/usr/include/stdcxx4/loc/_num_put.cc
/usr/include/stdcxx4/loc/_num_put.h
${SUNPRO_INSTALL_PATH}/prod/include/CC/stlport4/stl/_num_put.h
~ truss -eaf ${BUILD_COMMAND} -c 2>&1 | ggrep -P 'open.*_num_put\.c'
1729: open("/usr/include/stdcxx4/loc/_num_put.cc", O_RDONLY) = 8
... so clearly it's not going through _num_put.c, so it can't be going through the stlport4 header to do it; that means it must be going through _num_put.h (none of the boost headers or code files use this _num_put thing directly)
~ ${BUILD_COMMAND} -c -H 2>&1 | ggrep -P '^\s.*_num_put\.c'
The fact this last one didn't print anything seemed really odd. This next one is the weirdest though:
~ ${BUILD_COMMAND} -P
~ gsed -e '/^#/d' libs/log/src/process_id.i
~ CC -library=stdcxx4 libs/log/src/process_id.i -c
... produces no errors. It builds just fine. Furthermore, if you look at the output in the .i file (or if you use -E instead of -P) you won't see any of the code from _num_put.cc because the pre-processor doesn't spit it out.
Another way to see that:
~ ${BUILD_COMMAND} -c -Qoption ccfe ++boolflag:prepoutstd=true 2>&1 | ggrep -P '~\s*_num_put'
You won't see the destructor it's complaining about from the above. However, as I demonstrated above (and as the error message clearly demonstrates), it is in fact using the contents of _num_put.cc.
To put the final nail in the coffin, I looked at the output of using -xdumpmacros=%all (after examining how _num_put.h works) and this big of code sort of seals it for me:
~ ${BUILD_COMMAND} -c -xdumpmacros=%all 2>71 | ggrep -P '#define _RWSTD_DEFINE_TEMPLATE_(FIRST|LAST)'
/usr/include/stdcxx4/rw/_defs.h, line 1498: #define _RWSTD_DEFINE_TEMPLATE_FIRST(ignore) 0
/usr/include/stdcxx4/rw/_defs.h, line 1499: #define _RWSTD_DEFINE_TEMPLATE_LAST(ignore) 0
~ gtail -n 28 /usr/include/stdcxx4/loc/_num_put.h
#if _RWSTD_DEFINE_TEMPLATE_FIRST (_NUM_PUT)
# include <loc/_num_put.cc>
#endif /* ... more stuff ... */
There's another #if for _TEMPLATE_LAST later on with another #include line for _num_put.cc, but as demonstrated from the -xdumpmacros thing, both #if lines should not allow it to include _num_put.cc
I believe this is a bug in ccfe. If there's a straightforward way to force the compiler driver to do the preprocessing and compiling in two steps I believe I could work around this issue, but I don't see a way to do that.
As an aside, could someone point out a way to get some information on undocumented commands and flags? I found a way to get a listing, but figuring out what they actually do and when they're valid to use is another matter:
~ ${SUNPRO_INSTALL_PATH}/prod/bin/ccfe ++dumpswitches
~ ${SUNPRO_INSTALL_PATH}/prod/bin/ccfe ++dumpflags
-Brian

Based on your response to my question about forcing the use of a 3rd party pre-processor, I found I can make this build error go away with the -template=no%extdef option. I was under the assumption that the compiler wouldn't take it upon itself to automatically 'discover' the .cc file and attempt to use it; I assumed once the pre-processing stage was complete it would only attempt to compile the output from the pre-processor stage. Clearly that assumption was faulty.
Thank you for the response Steve. I've put in for the IT team to get/install the updates for us.
-Brian

When exporting images from iPhoto library to Aperture 3 library the highlights go red and the shadow area goes blue. This happen to all images in the Aperture 3 library, why?

For some reason all the images in Aperture 3 library have had their highlights go red and the shadow area goes blue. I can correct them one at a time with contrast control. This just happen on its on after I uploaded MOuntain Lion. Now when I go to transfer images from iPhoto this happens. The images are all right in iPhoto but this is not the case with Apeerture. I have 15,000 images in Aperture 3 and I can't afford the time to correct them one at a time. What is it that I did to cause this problem?

You have "Highlight Hot and Cold Areas" turned on.
Toggle this on/off from the View menu.
Thresholds are set at "Aperture➞Preferences➞Advanced". (I have mine set to 100% ~ it's not clear what the scale is.)
Message was edited by: Kirby Krieger

Maintaining collection organisation when exporting images.

I've read many times on this forum and elsewhere that photos should be organised into collections and by metadata rather than by putting them into folders and I've started doing this to some extent.
At some point however I have to export photos from Lightroom to deliver them to clients. How do I maintain the organisation afforded by the collections on export?
With folders it's relatively easy, I export photos as jpegs into a copy of the folders they're organised into, usually using LR2/TreeExporter.
That plugin doesn;t work with collections howoever, so what do I do?

johnbeardy wrote:
Folders for storage, keywords and collections for organisation - that's the hard line position
John
But you have to have organised storage, otherwise it's a messy heap of folders/images and it will look like Apple did the organising!
Not to mention I also use Bridge for times where it is better than LR and as collections are not interchangeable between the two apps.....
Besides I will not rely on collections for organising long term until that info is able to be stored independent of catalogues in the XMP file.
I've had to restart catalogues over too many times to solve LR issues or because of corrupted catalogues to trust any info trapped in there.
But organised storage and organised keywords and organised collections is only a good thing. Belts, braces and masking tape!
The big and rarely mentioned problem with keywords and collections is the huge amount of time and effort that is needed to do a thorough job of it.
Organising folders is dead easy in comparison, so is in reality far more likely to be done and therefore be of actual use.
I used to teach martial arts and would often get asked which one is best and my reply is 'the one you enjoy the most'. The reason being is that is the one you are likely to stick with and therefore learn the most from.

Possible Bug in ID5.5 When Exporting Images to ePub

Similar Messages

Maybe you are looking for