Why are my JPEG exports from Lightroom 4 are not displaying on other computers?

When I export JPEGs from Lightroom, they display fine on my computer but when I send them to the client, they are not displaying at all. There is a message saying that the software on the clients computer may not be up to date so I tried updating their software but to no avail.

I know, it's strange. I've never encountered it before. They are definitely JPEGs, although I don't know if the difference between JPGs and JPEGs is anything to consider.
On my computer, 2008 MacBook Pro, OS 10.8.3, they display through Preview. Also, when I upload them to Dropbox, the thumbnails display correctly. I have transferred them to a USB key as my client was not tech savvy enough to grasp Dropbox. When I brought the USB Key to the client and transferred to her MacBook Air, neither the thumbnails nor the photos themselves displayed. I also tried transferring to her PC and the same result.
I was trying to contact Adobe support to see if this was a problem other people had experienced.

Similar Messages

Background images are not displayed (CSS, other images ok

I tried clearing cache, looked at about:config for weird configurations, did a private browser window and disabled all extensions. None of these had any effect.
Test pages: Amazon.com and https://developer.mozilla.org/samples/cssref/background-image.html - both of these pages have background images loaded by CSS. For example, Amazon's logo at the top left is a background loaded from a CSS page. The image itself can be viewed raw:
http://g-ecx.images-amazon.com/images/G/01/gno/sprites/global-sprite-v1._V339353059_.png
So can this image:
https://developer.mozilla.org/samples/cssref/images/starsolid.gif
But why, why why do these images display on their relevant webpage? I see Amazon, eBay, and many other websites without a full complement of images. Especially the ones used for menus and other important navigation buttons.
Here is what I see on the Mozilla page mentioned above: I see the text, but no repeating star image. This works in other browsers and on other computers in Firefox.
The page I am typing on right now has no blue background, the entry windows are not correct (like the search window is not a rounded gray box) and the search magnifying glass is missing. So this experience makes even simple pages impossible to use.
Firefox 32, Vista

You did make sure that there isn't a high contrast theme selected in Windows like I posted above?
*http://windows.microsoft.com/en-us/windows-vista/make-the-computer-easier-to-see-optimize-visual-display

Apple Preview does not recognize jpeg export from lightroom 4.1

When i open the pictures in DPP I can see them fine?
Here is the message I get:
"The file “Edit-739820120223Canon EOS 7D.jpg” could not be opened.
It may be damaged or use a file format that Preview doesn’t recognize."

I was having the same problem! I downloaded a free file converter called Graphic Converter through CNET. It worked perfectly and you can convert one JPG file or a batch. I'm not sure what the issue is but this is definitely the easiest solution. I recently upgraded to Mountain Lion. I think it has something to do with the upgrade and reading JPG files that may be formatted differently. What I don't understand is why Mountain Lion cant read the files. Nonetheless, this worked perfectly for me.
Good Luck!!!

Pdfs exported from InDesign CS4 & 5 not displaying or wrongly displaying satin effect

When I apply satin effect to a text block, it often doesn't display once the file is exported to pdf (using CS4 and Acrobat 8). Satin effect applied to text or strokes in CS5 don't display fill or stroke color, just the black part of the satin effect. In the first instance I was exporting to PDFx1a for a commercial printer. From CS5 I was doing "high quality print". Anyone else have this problem?

When I apply satin effect to a text block, it often doesn't display once the file is exported to pdf (using CS4 and Acrobat 8). Satin effect applied to text or strokes in CS5 don't display fill or stroke color, just the black part of the satin effect. In the first instance I was exporting to PDFx1a for a commercial printer. From CS5 I was doing "high quality print". Anyone else have this problem?

Why do my pictures become blurry after exporting from lightroom 5?

My pictures become somewhat blurry or not as sharp after I export them from lightroom 5. PLEASE HELP!!!

If you are looking at your exported pictures in preview.app than that is the culprit. It uses an extremely poor downscaling algorithm for displaying large images and will make every large image, no matter how sharp originally, display blurry. In preview you can hit command-0 (that's a zero) to make the image display 1:1 to see the actual detail. Make sure you have it's preferences in the images panel set to "Define 100% scale as 1 image pixel equals 1 screen pixel". I think in older Mac OS X versions, it was called something like ignore image dpi for display or so but I don't remember. You can also make sure to downscale (with correct output sharpening in the export panel) upon export from Lightroom. If the exported image is smaller than the display, Preview should display 1:1 by default upon opening.

Why won't .MOV files export from Lightroom?

Why won't .MOV files export from Lightroom?

The will.
Or at least they can, and do, sometimes, if you have good MOV karma..
Why not supply a little more info, like:
* Which OS
* Which version of Lightroom
* History of MOV files.
* Export format.
* Do other video types export OK
* How many different MOV files have you tried - all with the same history?
and of course:
* What, exactly, happens, when you try?
Rob.

Exporting from Lightroom 4 to Photoshop CS5

I have a workflow I have followed for a long time now. Things changed and I can't figure out what I did:
I make adjustments to images in Lightroom 4 then send the image to Photoshop via EDIT-IN method [ctrl-E] on my PC. I make my changes in Photoshop and then SAVE-AS a TIFF followed by a JPEG. Normally both files return to Lightroom where I can see them in the filmstrip. However, I cannot see the JPEG's anymore. They are not displaying in the filmstrip anymore. I have made some changes recently in my color settings and I checked my Preferences but I can't see anything that would prohibit the RETURN of the JPEGS. Any thoughts?
Thank you!!!

It is important to understand how Lr works.
Lr displays photos only when they are imported into Lr. A (seeming) exception is for a Raw image that is edited in Photoshop and <Saved> to the default settings that you selected in external editing of Preferences in Lr. So if the default setting is for PSD and you just hit <Save> in Photoshop, a PSD will be created and automatically imported back into Lr so that it will be displayed there. So, this is not really an exception from the rule that an image has to be imported into Lr - it is an automatic import. This automatic import works only for the <Save> to the default settings;it does not work when you do a <Save As> and select a different file format than the default setting. In your case you did a <Save as> to create a JPG. This JPG will not be automatically imported into Lr, you have to import it manually - either through the Import Dialog or by <Synchronize Folder>.
Apart from that, and as JimHess said, why do you create a JPG in Photoshop from the same file? If you need a JPG, in Lr just export your PSD as a JPG when you need it.
I often need JPGs from my file, but I create them only when needed by exporting them to a folder of my choice. Usually I delete them after a while. I don't see a reason why I should have JPGs sitting around on my hard drive(s). They can be created again (from the Raw files or from PSD's/Tiffs) if the need arises.

Prints exported from Lightroom consistantly 1 stop dark!

I calibrate my monitors regularly and currently have my two monitors set to the absolute lowest brightness point they'll go.
Everything's calibrated and my histograms look good yet, every time I try to send something out for printing, it comes out at least a full stop dark.
Conversely, if I print on my own Canon Pixma printer and allow the "printer to manage colors" - things are spot on.
I don't want to always have to print every little thing at home. I'd like to send things out sometimes.
I do not have this problem with files exported from Photoshop. Only files exported from Lightroom. Yes, I know I can fool around with making a brightness preset but why do I have too?? What is going wrong here?
This is making me crazy. Help Please!

IF you're working with an outside lab that doesn't supply an ICC profile for soft proofing, you can pretty much forget about getting a match. Further, the lab has to be using that profile (or let you use it) or again, you're dealing with a lab that has a half baked color management workflow. No wonder you are having good luck printing yourself, you're probably doing everything correctly.
That's absolutely right. The only consumer oriented big box local lab I have found that does this correctly is costcos and then I understand you need one where the operators have a clue and not every location is good and keeps their machines consistent. The other labs I mentioned all do a great job color managing and I have never had "too dark" prints. The fact that your own printer works fine makes me think that this is indeed very likely a lab problem (not at all uncommon). I would recommend that you print to your own printer while having Lightroom color manage as you should get better quality in subtle color gradients but only do this if you understand the weird codes Canon uses for their profiles and you understand how to turn off color management in the driver.
That said, you can do a quick sanity check of your calibration by using a printer test file. Andrew has one on his site here that will work fine: http://www.digitaldog.net/tips/ and a nice one from inkjetart can be found here: http://www.kenleegallery.com/images/tech/4800test.jpg
Load these into Lightroom. Do not touch any develop settings and see if the images make sense on screen. Skin color should look great (not too bright), you should see nice saturated colors and no plugged up shadows. Export these files to sRGB jpegs (they are in a different color space as downloaded so you need to convert for most labs) from Lightroom and send those to your lab. If your prints from these testfiles come back dark, stop using them as they don't calibrate their machines correctly. Well-calibrated machines should give very good prints with tone and color very close to what you see in Lightroom. You can get somewhat better results if the lab provides icc profiles but in my experience, if the machines are tuned correctly you will have a hard time distinguishing profiled images from sRGB images if you don't use a good viewing station.

Export from Lightroom: folder not found.

New Problem with export from Lightroom. I always have to select the folder where to save to, even if it was selected before. This means I have to click on an already activated folder at every export. Why? This problem wasn't there before.
I always use the option "choose folder later on" at the export dialog box.
Error message: "Es wurde kein Zielordner für diesen Vorgang angegeben."
Thanks for help folks!
Best
Bernd

Normally when Lightroom says "not enough memory", that's exactly what the problem is, you don't have enough memory.
A partial solution would be to make sure no other applications are running when you do this export.
The real solution is to make sure your computer has both 8GB RAM (or more) and a 64 bit operating system. One of these by itself without the other will not improve the situation.

Saving PSD files after exporting from Lightroom saves incorrectly

I've only recently moved to Lightroom from using Photoshop/Bridge together, so I'm not 100% sure how saving files exported from Lightroom should go. But here's what I experience:
Base edit of file within Lightroom
In library view, right click on image -> Edit in -> Open as Smart Object in Photoshop
Perform all my necessary edits and such
File -> Save As, and save it to another location as a PSD file (totally different HDD)
Perform more edits....
Shortcut CTRL+S to save, and it saves it as the TIFF file under the location it was originally in within Lightroom
Eh...? Am I missing something. It should just save as the original PSD I created when I went "Save As". I have seen on a few occasions, immediately after "Save As", the file name resorts back to TIFF and not as PSD.
My settings for External Editing in Lightroom are as follows:
File Format: TIFF
Color Space: ProPhoto RGB
Bit Depth: 16 bits/component
Resolution: 300
Compression: None
Does anyone have any ideas what I'm doing wrong? Also, to note, that sometimes I double click on the Smart Object within Photoshop to load Camera Raw and perform some edits, but not often.

Modesto Vega wrote:
Replying to your last 3 posts.
Re Camera Raw being used to pass an image to Photoshop
a) I am assuming this is independent of the Compatibility level in Preferences\File Handling DNG creation.
b) Does the same apply to other photo editing software made by Adobe like Elements?.
Reply: Yes, the principle is the same. Photoshop Elements cannot read raw data either. That's why it has to be converted before it's opened.
c) Assume that I have LR 5.7.1 and CS5. Is Camera Raw is still used to pass an image to Photoshop? If so, why is there a need to get LR to behave differently?
Reply: Camera Raw is used IF you choose the option to open anyway. Then Camera Raw will be used to convert the image that's opened in Photoshop. But since it is older than Lightroom some of the new adjustments might not be transferred to Photoshop. That's why there is a need to let the user make the choice.
d) Sometimes it does seem as if Adobe might be using Camera Raw updates and process version updates to get consumers to change their habits, this includes having to buy subscriptions or having to change workflow to some ideal that somebody at Adobe or working with Adobe might have in mind.
Reply: The fact is that in the past, when a new version of Photoshop is released then all support and updates cease for the previous version. Since the introduction of the creative cloud, at least users of Photoshop CS6 get support for new cameras. They just don't get the new features. Yes, there's motivation to upgrade. Adobe is a business. What do you really expect?
Re stacks
I find impossible to see collapsed stacks on the film strip. Stacks are only visible on the Library module and using a grid view; I don't say clearly visible because they are only recognisable by the label at the top left corner with the image count; I don't even think it is possible to change the colour of that label or the grey colour surrounding an image. Also I cannot name stacks. If I could name stacks, see them as virtual folders underneath a library folder and make them glaringly visible I would use them extensively.
Reply: The only reason I can think of that you are unable to see collapsed stacks on the filmstrip is if you have the filmstrip reduced in size to the point that Lightroom can't display all the icons. I'm able to see the collapsed stacks in the library grid view and on my filmstrip
Re storing your Raw files and processed files in separate locations
Assuming Raw files are negatives and Photoshop files are transparencies or prints, would you want negatives being handled/read on a regular basis? If anything happens to your negatives, you would never be able to produce another print or another transparency again.
Reply: The raw files or the negatives, as you put it, are never modified by Lightroom. They always remain in their pristine state they were in when they were imported. If I have a backup of that raw file then I can do whatever I want to the one in my working folder. Resetting that raw file so that it looks unaltered is just a click away.
I have worked extensively with databases and database systems, it is a standard feature of database systems to be able to choose where to store different database objects. I don't see why LR cannot do the same, it is a database after all. I do agree with both the OP and photo.
Reply: Well, I won't argue that point. If that's what you really want than lobby for it. It just won't get my vote because I don't see any real advantage.
If you read back through this quoted message you'll find that my replies are included. I don't know how to separate them out so they are highlighted properly. Read through it and think about it. But personally, I don't want to waste anymore time on this discussion because it isn't accomplishing anything in my opinion.

HELP- Exporting from Lightroom 5.0 to iPhoto 9.4

What is my problem?
After exporting from Lightroom via export menu I am only seeing certain metadata in iPhoto.   My keywords appear in iPhoto but my ratings are not showing up.
Current Process
In lightroom save all metada data. Select photos in lightroom (DNG format). Export ensuring all metadata is sent. Exporting in JPEG to desktop.   Drop folder into iPhoto.   Keyword are there but no ratings.
What should I do?
I prefer iPhoto for apple tv, iOS devices, links with email, and using in Final Cut.   And general viewing.
Adobe please help make this easier for me.
Otherwise love lighroom
Thanks anyone who can help,
J

attached as 8.2, which you can open
Attachments:
BOP488.vi ‏19 KB
BOP488-w.vi ‏18 KB
Keithleytest.vi ‏8 KB

Corrupted EXIF data in photos exported from Lightroom CC

After upgrading to Lightroom CC EXIF can't be read by some apps. "Re-saving" a file in Photoshop fixes the problem. I'm using Mac OSX 10.9.5. Are there any plans to update and fix the EXIF data generated when exported from Lightroom CC?
Also, this command fixes the issue with Create Date part of EXIF.
#!/bin/sh
exiftool -AllDates="$(exiftool ${1} | grep 'Create Date' | awk '{print $(NF-1), $NF }')" -overwrite_original ${1}
The reason I'm asking is because we run a site where "Create Date" read from JPG's EXIF is crucial and it's a matter of letting users upload the pic or deny uploading.
So again, any plans on the fix?
Regards,
Pawel Kadysz

I confirmed that the Exiftool command line:
exiftool -m -all= -tagsfromfile @ -all:all -unsafe file.jpg
removes the ICC Profile, which could account for significant color differences, considering that the profile is Adobe RGB. I think this may be a bug in Exiftool, so I filed a bug report. (But it might be that Exiftool just can't handle the non-standard layout of LR's JPEGs.) The author is typically very responsive.
I tried some alternate Exiftool command lines that touch as little metadata as possible, and this one seems to address both of LR 6's JPEG problems:
exiftool -m '-exif:datetimeoriginal<exif:datetimeoriginal' -xmp-crs:all= file.jpg
The -m option ignores minor errors and issues, in particular, when there are more than 1000 entries in the XMP metadata.
The '-exif:datetimeoriginal<exif:datetimeoriginal' option sets the EXIF Date Time Original Field with its current value; this tricks Exiftool into rewriting just the EXIF metadata without touching the other metadata segments (e.g. the ICC profile), addressing the first JPEG problem. (You could use any EXIF field that's present -- I picked DateTimeOriginal since every camera adds that.)
The -xmp-crs:all= option option deletes all of LR's develop settings from the XMP metadata, addressing the second JPEG problem.That metadata is not ready by any programs other than LR, as far as I know.
I've tested this new command line on a couple of pics, including the example you provided above, and it appears to work correctly. But given that we're dealing with buggy output from LR that doesn't conform to the de facto and de jure standards, it's hard to have high confidence without testing on dozens if not hundreds of pics.

JPGs exported from Lightroom 5.6 will not open in other applications

Recently I have noticed that jpgs exported from Lightroom 5.6 can not be opened in Canon DPP 3.14 and can not be resized using Image Resizer plugin. Both of these I use frequently.
I have seen mention of this issue re other applications also. Does anyone know if there is a solution?
I am using Windows 8.1 64bit. 5D Mark ii

This was an issue with 5.5 (the placement of some of the internal headers of the jpgs was changed and some other applications, including DPP, could not open them), but was corrected in 5.6. I just checked on it by exporting a jpg and opening it with no problem in DPP 3.14.15, Windows 7 x64. Are your jpgs old ones from LR 5.5?

Trouble exporting from Lightroom 4

While trying to export from Lightroom 4, I was getting the error message "An internal error has occurred:WIN32 API error 2, etc. Others have asked about this and the solution offered was to check "Do Nothing" in the post processing box, which I have done. Now I can export, but the image is severely downsized from being a full sized jpeg. How do I get it to export at full size? All was working fine with exporting until today

Thanks...the quality slider was at 60 - moved to 100 and it solved the problem. Simple - Thank you for suggesting - I was getting a headache trying to solve my issues today!

Book Module: exporting from Lightroom as a 2 page spread

Hello Lightroom people,
I have begun to create my albums in the lightroom book module, and I am about 85% happy with it. I have one major complaint, and I'm wondering if it can be corrected:
My album company wants me to submit my album pages as two page jepg spreads. For example, if I am making a 10" x 10" book, rather then submitting pages 1 and 2 as two 10" x 10" jpegs, they require a single, 10" x 20" jpeg that is then printed as pages 1 and 2.
When I export from lightroom, it exports instead as single pages (to use the example from about, two 10" x 10" jpegs for pages 1 and 2). I've noticed that if I design a 2 page spread--then it will export that the way I want it, but obviously no album can have all 2 page spreads.
My work around for this is to import the jpegs in photoshop and lay the pages together the way my album company likes, but this is somewhat time consuming.
Is there a setting in the book module I am missing that could correct this?
Thanks,
Ellen

JimHess wrote:
The book module is designed specifically to work with Blurb.
Which was the biggest error in decision making Adobe made in going forward with the book module ... it should have never been tied to ANY single vendor ...
JimHess wrote:
I just export copies of my images and use the software provided by the book company to create my books.
Yes, there is always a workaround, though Lr was supposed to simplify the process, not create more work ... though if we were discussing having to export images ... THEN ... send them to a printer instead of printing them directly in Lr ... there would be much more discussion about the problems the Book module poses for many users ...
If I must export images and use outside software to finish the job (InDesign or otherwise) I may as well give up Lightroom as a "workflow solution" ... I could get the same job done working with Bridge/ACR/Ps workflow ... however ... I bought into the paradigm of Lr being the answer for RAW processing to output workflow ... though Adobe seems to pick and choose which features they really care about ... If Adobe is going to include a Book module, and expect me to financially support the effort ... they could at least offer a module that is functional without being tied to a single vendor ...

Why are my JPEG exports from Lightroom 4 are not displaying on other computers?

Similar Messages

Maybe you are looking for