Saturation Loss When Exporting from Lightroom.

This happens to me when exporting from Lightroom 2 or 3. It happens regardless of the color profile, file format, bit depth, image size, compression, or the method of export. I regularly profile my one-year-old iMac monitor with an Eye One Display 2. My working color space for Photoshop CS4 is ProPhoto. After exporting, I am viewing the images in Photoshop, Safari, Firefox and Apple Preview, with the same result. I have used pretty much all the available export methods in Lightroom, including exporting with Lighroom ad-ons such as SlideshowPro. And, conversely, if I edit an image to my liking ourside of Lightroom, there is a saturation increase when I import it into Lightroom.  The effect tends to be most obvious and bothersome with shots taken outside on sunny days, with lots of blues and greens.  I am shooting raw files with a Canon 5d II and I use the Adobe Standard profile in Lightroom.
There is a section at the back of Martin Evening's Lightroom book where he talks about the Lightroom color space and Lightroom versus Photoshop curves, which seems to relate to what I am seeing, but I have the feeling that what I seeing is more pronounced than what he is talking about there.  It is a real dullng of the look, not merely a slight difference in how the colors are rendered.

Looks like Lightroom doesn't like your display profile.
Try removing the profile (don't know how to do it on a Mac) to leave your display uncalibrated. Are the colors still different in Lightroom and Photoshop?

Similar Messages

  • Pictures all grey toned when exported from Lightroom 4.

    They look great in Lightroom and then look/print grey toned when exported, even photos that have not been edited.  Fix?

    Can't think of any ICC profile LR would allow that would produce a grayscale appearing document. Wondering if it's another of those 'corrupted' display profile issues where a grayscale treatment is being applied to the images but in LR it isn't showing? This IS a strange one.
    What if in the Print Module you Save as JPEG, Gray?

  • Receiving an error report when exporting from Lightroom - Why?

    I use Lightroom, always have. Started editing on a new computer (given to me by an associate as my computer has crashed) - the specs are sufficient to run Lightroom, and 9/10 times it gives me an error message that says it can't export photos. Every once in a while it will actually export the photo, but there's no rhyme or reason to it - Please help.
    The error message only says "Not enough memory" - no other details, no nothing.

    Hi,
    minimum requirements are from sales people, optimal ones form the working people...
    Try to close all other (backgroud) programs.
    Which camera you are using? Try to export with diffent settings. (Why only @60 when you want to print?, Why sharpen for Mate if you want to e-mail?) If you want to print, I would use TIFF.  Try to export images in smaler packages (2x 50 pictures, instead of one 100 pictures job).
    Try to disable the wateramarking.

  • Pixelated images when exporting from Lightroom

    I recently switched from A Windows PC to the MBP Retina 15". I imported photos to lightroom from my external hard drive in RAW format to lightroom, edited then exported firstly as jpeg resized to 630 x 420 at 150 dpi. The images came out pixelated so I tried exporting at 300dpi even though the images are for web use. They still came out pixelated. So I tried exporting as .tif files at 300 dpi and still they are coming out pixelated... does anyone know why this would be? The raw files don't look pixelated at all.

    [email protected] wrote:
    I resized this image to 1200 x 800 and have just cropped a section to show you.
    PART I
    Viewed at 100%, I see no "pixelation" or any other distortion of any kind whatsoever.
    Only a 100% view (1:1) shows you your true image.  At smaller percentage views, pixels have to be discarded; at greater percentages pixels have to be made up (invented) by the software.
    With the Retina screen you're bound to see very strange things, unless you're using the latest and greatest versions of Photoshop and of your video card, and utilizing the Retina features of the software.
    PART II
    JPEG is a lousy, lossy format for maintaining image quality.  Every single time you open or create and save a JPEG, the image quality deteriorates, no exceptions.  Even at the highest quality of compression.
    To take a very low resolution JPEG, like you did, and subject it to such a massive enlargement is to ask for demand trouble.  Not only are you also magnifying all the JPEG compression artifacts, but you are "inventing" an inordinate amount of pixels.
    If you have to enlarge your images often, start with an image file that has NEVER been a JPEG.
    PART III
    Photoshop performed superbly in your case.  That is a remarkably fine enlargement, especially considering the miserly JPEG you started from.  Rejoice!

  • Get too small pictures when exporting from Lightroom

    I shoot in both cr2 (23 MB) and Small-jpeg. Afterwards I upload the pictures to Lightroom and have the appear in the catalog as one picture. Here I make all the editing and when I export the picture back to my harddrive as a jpeg I can only get a file of 3-500 kb. I know I have made some croping - but not that much. It is like Lightroom is working on the jpeg picture and not my cr2 picture. Do anyone have a clue to what I am doing wrong? It may be a setting?

    Lisbeth Bech wrote:
    Hi
    Here is a screendump of the export dialog box
    https://www.dropbox.com/s/ht380sf9irk6gmt/Screenshot%202013-11-26%2019 .22.40.png
    The size of the cr2 file i 21 MB (and it has a jpeg sister of 930 kb) - and the picture is cropped - but how do I read the cropped dimension? As I am shooting bird picture I normally crop a lot - but my picture are still of an ok size
    I can see your screenshot, and looking at the actual pictures that were exported (thumbnails in the filmstrip at the bottom) helps understand why the jpg files are small: your pictures are mostly a smooth blue background (sky) with a tiny bird in the picture. These files are highly compressible in the jpg format, as there isn't a lot of detail in them. I would expect that the resulting file size would be rather small, even if the original files were large.

  • Colour shift when exporting from lightroom 5 into Photoshop CS6

    Hi there,
    Having a really weird problem in Lightroom/Photoshop that no amount of Googling can seem to fix.
    When I grade an image for colour in lightroom, and then use the "edit in" function to send the file to Photoshop, the file is a completely different colour.
    Here's an example:
    I'm using SRGB for both Lightroom and Photoshop, and the "preserve embedded profiles" is selected for RGB, CMYK, and gray.
    If anyone can shed some light on this, it would be great. I don't want to have to use ProPhotoRGB, because most of my work is delivered online.
    Thanks in advance
    John

    I am also having this issue with the "Merge to HDR Pro" function in both LR5.2 and PSCC. When the image is viewed at 50% image size in the HDR app everything appears fine. However, once you start to zoom in the image begins to crop out segements starting on the right hand side. See the screen shots below:
    Image at 50%
    Image at 66%
    Image at 100%
    MacBook Pro 2.7 GHz Intel Core i7 16GB RAM 512GB SSD (early 2013) NVidia GT650M Mac OS X 10.9

  • I'm losing date photo was taken when exporting from Lightroom.

    The photo taken date is being replaced with the date that I'm processing the photo with Lightroom.  The photos I'm currently working with were taken over 10 years ago with an early generation Olympus digital camera.  Does this have anything to do with my problem?  I must be doing something incorrectly, can anyone give me advice.  T

    Rob - I am working with old images from an early generation digital camera but yes the image capture date does show correctly in Lightroom for most of these images.  However, I just realized thinking about your question that some of the photos could be scanned from a film image and do not how a capture date in Lightroom.  The exif data is entirely different for these.  The photo processors I used in those days were providing a CD along with the negatives / prints so I may have just answered my own question.  Thanks for the questions and help to both.

  • Optimal photos size for Ipad when exporting from lightroom.

    anyone using lightroom. what are you setting your photos at for the ipad. what is the optimal photo resolution for the ipad?

    Looks like Lightroom doesn't like your display profile.
    Try removing the profile (don't know how to do it on a Mac) to leave your display uncalibrated. Are the colors still different in Lightroom and Photoshop?

  • 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.

  • IDVD Stops Responding when Exporting from iMovie

    I'm using iDVD and iMovie (from iLife 06 and fully up to date) on a MacPro (also up to date on all software, MacOSX, Quicktime etc).
    This proceedure has worked before several times but now results in a non-responding iDVD every time I try it, including an archive and re-install and a complete new install of OSX and all software on a new partition.
    What I'm doing.....
    [1] Recording a TV programme on EyeTV (410) and exporting it to iMovie - sucessful every time
    [2] Edit the iMove project and add chapter markers and save project - no problem.
    [3] Export to iDVD - iDVD shows exporting in progress and whilst this is still showing iDVD launches
    [4] iDVD starts playing the music from a std theme for a few seconds and then stops. Then resumes the music after resizing the window and then after a couple of more seconds freezes. From the Dock I can see that iMove and iDVD are "not responding"
    [5] Eventually iMovie completes it's "export" and then starts responding normally. iDVD continues to show as non responding although I can move the window around the screen. I have to force quit iDVD to get it to close down.
    I have tried:
    Re-exporting the project from EyeTV
    Deleting the preferences files for iMove and iDVD
    Deleting the iLife suite and re-installing
    Doing an OSX archive and re-install
    Installing a fresh OSX (10.4.8) on a different drive and installing fresh software
    Running Disk Utility - clean bill of health on both drives
    Repaired permissions
    The Console reports the following errors when exporting from iMove to iDVD:
    ===== Tuesday, 24 October 2006 22:56:45 Europe/London =====
    [KN,10:57:08:852]/SourceCache/iDVD/iDVD-791/./PBProjects/iDVD/RemoteControlContr oller.m:348 : switchTheme: mIsPlaying = 0
    [KN,10:57:08:852]/SourceCache/iDVD/iDVD-791/./PBProjects/iDVD/RemoteControlContr oller.m:348 : switchTheme: mIsPlaying = 1
    [KN,10:57:11:968]/SourceCache/iDVD/iDVD-791/./PBProjects/iDVD/RemoteControlContr oller.m:348 : switchTheme: mIsPlaying = 1
    2006-10-24 22:57:53.394 iDVD[424] NSExceptionHandler has recorded the following exception:
    NSInvalidArgumentException -- * -[NSCFArray addObject:]: attempt to insert nil
    Stack trace: 0x954ee243 0x9264f2cb 0x9264f110 0x925dd399 0x000df708 0x000df806 0x00215e6d 0x002167ef 0x0021470b 0x001a0b4f 0x00184105 0x92627d78 0x92627222 0x92626fa9 0x92626811 0x92621ae0 0x00166dc7 0x9261e861 0x925f2ef1 0x925f2d1b 0x9151d6c5 0x9151d5f6 0x9151d4c2 0x92dda340 0x9325c63d 0x9325c056 0x93255ddb 0x93249d2f 0x0000ad5d 0x0000ab36 0x0000aa51 0x00000002
    Result - problem persists. I'm at a loss as what to do next. Any suggestions greatfully received.

    Yes, tried that when I deleted the preferences. Disk Utility did not report any permissions needed repairing.
    What really mystifies me is that this export to iDVD did work once and I expected it to resume once I'd created a fresh OSX install along with all the iLife apps on a new partition, but it remained the same!
    Perhaps there is some sort of other software conflict going on? I have Adobe CS2, MS Office, Toast and FMP installed all are latest editions. On the utilities front I have installed Stuffit Deluxe, Internet Cleanup, Contour USB controller for video editing and a LogicTech wireless trackball. Again all the drivers are the latest releases.
    Does anyone know if there are any preferences associated with the other not responding applications listed in my other post that I could try the delete-reboot trick on?

  • Large PDF file sizes when exporting from InDesign

    Hi,
    I was wondering if anyone knew why some PDF file sizes are so large when exporting from ID.
    I create black and white user manuals with ID CS3. We post these online, so I try to get the file size down as much as possible.
    There is only one .psd image in each manual. The content does not have any photographs, just Illustrator .eps diagrams and line drawings. I am trying to figure out why some PDF file sizes are so large.
    Also, why the file sizes are so different.
    For example, I have one ID document that is 3MB.
    Exporting it at the smallest file size, the PDF file comes out at 2MB.
    Then I have another ID document that is 10MB.
    Exporting to PDF is 2MB (the same size as the smaller ID document)... this one has many more .eps's in it and a lot more pages.
    Then I have another one that the ID size is 8MB and the PDF is 6MBwhy is this one so much larger than the 10MB ID document?
    Any ideas on why this is happening and/or how I can reduce the file size.
    I've tried adjusting the export compression and other settings but that didn't work.
    I also tried to reduce them after the fact in Acrobat to see what would happen, but it doesn't reduce it all that much.
    Thanks for any help,
    Cathy

    > Though, the sizes of the .eps's are only about 100K to 200K in size and they are linked, not embedded.
    But they're embedded in the PDF.
    > It's just strange though because our marketing department as an 80 page full color catalog that, when exported it is only 5MB. Their ID document uses many very large .tif files. So, I am leaning toward it being an .eps/.ai issue??
    Issue implies there's something wrong, but I think this is just the way
    it's supposed to work.
    Line drawings, while usually fairly compact, cannot be lossy compressed.
    The marketing department, though, may compress their very large TIFF
    files as much as they like (with a corresponding loss of quality). It's
    entirely possible to compress bitmaps to a smaller size than the
    drawings those bitmaps were made from. You could test this yourself.
    Just open a few of your EPS drawings in Photoshop, save as TIFF, place
    in ID, and try various downsampling schemes. If you downsample enough,
    you'll get the size of the PDF below a PDF that uses the same graphics
    as line drawing EPS files. But you may have to downsample them beyond
    recognition...
    Kenneth Benson
    Pegasus Type, Inc.
    www.pegtype.com

  • 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.

  • 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 ...

  • Exporting from Lightroom to Photoshop.

    I have set the necessary preferences so as to export from Lightroom to PS CC. However when i try to export a file then PS CC fails to open. However PSE 11 opens but with no file! Any help would be appreciated. thanks GM

    Ask in the LR/ PS forums and provide details about your system, your files, your develop settings, other stuff. You need to be much more specific.
    Mylenium

  • 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.

Maybe you are looking for