Colors change after exporting from 5.2 upgrade

I did not have this problem prior to upgrading to Lightroom 5.2
I import .jpg photos into lightroom, adjust brighness and colors, export photos. All of the exported photos have odd colors. Blue skies are too purple. Warm woods are shifted greenish. The new photos are unusable because the colors are so distorted. It looks like the hue is shifted but I cannot be sure.

Here:

Similar Messages

Color change after exporting from Lightroom

I noticed a drastic color change after exporting a file from Lightroom to a JPEG file today. I have been using Lightroom for a while, and it never happened before. I am assuming that I changed the setting somehow and I cannot find how to fix it.
Here is the original.
After exporting to a JPEG. The color is so drastically different. I tried both sRGB and AdobeRGB and they turn out to have the same problem.
It is not as clear as JPEG files, but edited files with Photoshop CS5 also looks slightly different viewed on Lightroom.
I would appreciate it if anyone could help me. Thank you so much for your help!

Thanks everyone for looking into my problem!
>Can you upload a sample of each
>* Raw File
>* XMP Sidecar
>* Exported JPEG
I somehow can't find XMP sidecar files in my folders.... So instead, I exported the JPEG file to the 2nd JPEG file, hoping you can compare those two JPEG files.
The colors get lighter and lighter every time I export the files. I uploaded those files (RAW, 1st JPEG, 2nd JPEG) on line. I also changed the file samples from the original post because I can't add watermarks.
I checked my flles, but there is no preset applied to the JPEGs.
I am thinking of unistallng Lightroom and reinstalling it and see what happens.
Thanks!
1. The data of the RAW file: http://yuko-hirao-photo.hechtmail.com/others/DSC00530.ARW
2. Data of the GPEG exported from the RAW: http://yuko-hirao-photo.hechtmail.com/others/DSC00530test_upload_01.jpg
3. Data of the JPEG exported from above JPEG: http://yuko-hirao-photo.hechtmail.com/others/DSC00530test_upload_01test_upload_01.jpg

Why is the color changed after export?

Hi
The colors of my movie change after i export them.
I tried to find the anser on all kind of forums but i believe i'm the only one with this problem.
My settup:
Mac 24GB 1333MHz DDR3
Eizo CG221

Here are some screenshots.
I've made no color correction.
If you look at the preview, you see it's saturated and the colors are off. And after the export it's back to the origanal colors.
Here are some more specs:
Footage: Proress 422
Sequence settings:

Color change on exporting from lightroom and saving in Photoshop CS5

I have been having issues with my pictures with color management.    I have Lightroom 4 and Photoshop CS5. I thought over the last 2 years that it was just me.   I have bought a Eizo monitor with a hood, calibrate with a i1display pro, painted my walls gray, updated my strobes from alien bees to elinchrome bxri's.   Updated my sekonic meter to a L 758.   Have done custom white balance with gray card, expodisc, xrite kits.   The problem has been over the years when I work on a picture in lightroom and export it as jpeg or adobe rgb it gets saved to my external hardrive and the colors are really bad !!   You can go back and compare the picture in lightroom to the picture on my iomega external drive and there is a significant difference.   I do some animal photography and I had a dog that had brown fur and when I export it out of lightroom the dogs fur is actually a bright very orange color. Same thing happens with skin tones.     When I import the photos into lightroom the pictures look ok.       The same thing is happening when I go from lightroom to photoshop the picture color looks good but when I go to File-save as - tiff or jpeg the colors are changing.   It does not matter what color space I am in I have tried them all it is still happening.    If anyone has any insight that would be great.
Teresa

         Thanks everyone for the help.   I have only been doing photography for about 2 years and the color managment part has been my hardest thing to get right.   My monitor ColorEdge CG243W LCD.   Wide color gamut of 98%. Has a sensor on front of monitor that detects ambient brightness but this will only work if you are in a custom color mode. Modes are: custom, sRGB,DCI,EBU, Cal1.   I use the Cal 1 to be able to use the Colornavigator software that came with the monitor. You also have to be in custom color mode to be able to manually adjust brightness, contrast, temperature on the monitr itself which I do not use because I use the Cal 1 mode.   I was not sure about the digital input signals.   I am on the DVI-I in which this allows digital signal input and analog signal input.    There is a DVI-D mode that allows only digital input only.    Also did not know if I needed to be concerned about setting the frequency that corresponds to the grahic board in the monitor ?    My bandwith was set to normal and now is on wide.   My digital input is for 1920x1200 resolution.   Appicable signal is Vesa CVT RB. Frequency is 60 Hz.   Yes I did call Eizo twice last year when I got my monitor and did not get very far.     I have also called and spoke to a color specialist at my lab and told him the problems I have been having and he just told me to leave everything in sRGB.   Well I would like to get the most from my monitor's color gamut and when working on my pictures so that is why I am still determined to get this figured out.
I use the i1 Dislpay Pro hardware to calibrate with and the ColorNavigator software.     When calibrating.   I go to create a new target---select enter manually--Gamut ( monitor native--states recommended)--Brightness 100cd---White point (6500k)--set black level (recommemded states mininum 0.2)---gamma 2.20---priority (set automatically to standard, this adjusts gray balance while maintaining the contrast)---then I hit calibrate and it goes through the process.   The results I get are:                                            Target                                               Result
                      Brightness                                        100cd                                              99.9cd
                       Black Level                                    minimum                                       0.15cd
                      contrast ratio                                                                                            647:1
                      White Point                                    6500k                                              6501k
                       Gamma                                           2.20                                             R   0.6774,0.3136
                                                                                                                                        G   0.2031,0.6992
                                                                                                                                        B    0.1498,0.0499
Thanks again for your help I know this is alot of information but I thought it might help ?
Teresa

Cannot Open Excel File after exporting from Disco Plus

Hi there,
I got a question from one user having issue with opening Excel file after exporting from Disco Plus.
The report has been using for a while and he is using Excel 2003 version and Discoverer 10g(10.1.2.2), he never got this kind of error before, just recently got error.
After exporting from Disco Plus he saved file on his desktop and when he tries to open the excel it says "Cannot be Accessed, can be corrupted...." but this is not from network drive since he saved file on local desktop or C drive.
Also not for all reports, only this particular report and only specific parameter, for example for parameter 2008 Feb opened successfully, but for2009 Feb he gets this error when trying to open excel.
i tried in excel 2007 also , i dont think this is Excel version error, am not sure.
Also after go live last week (we upgraded database from 9i to 10g) but i am not sure this causes ,since for one parameter working, for other parameter not working.
Actually we should get one window for Macro when we try to open excel, but he is not getting it seems.
Any ideas/thoughts on this would be greatly appreciated.
Thanks for your help
--skat

Rod,
Thanks for your quick response on this.
Yes, we can export to other formats as well, but actually exporting is working, after saving the file on our local desktop/drive and when we try to open we get this kind messages or we cannot open the file, we should get message window for Macro to enable/disable but for this report we are not getting this either,
Also this happens only for specific parameters,like i mentioned above it works I mean excel file opens for one set of parameters but for some other set of parameters cannot open.
For example :- when we enter FEB 2008 it works, if we enter FEB 2009 it won't open the file.
This is weird
I am still working on this issue, may be better to recreate the report again might be helpful,
Any ideas/comments/thoughts would be great
Thanks
Skat

PDFs dull in Acrobat after exporting from Indesign - again

Hi folks,
I am aware of a previous post which discussed this issue which was apparently resolved, but it appears to have reared its ugly head again. The problem - since updrading to Mavericks and the Creative Cloud, pdfs in Acrobat are very dull after export from Indesign and it is not a transparency blend or Indesign issue. I understand Adobe blamed Apple for not updating their colour management software and the reply from Adobe was:
"We have found the root cause of this issue and are in process of providing a fix. Once this is done, we will test it to make sure that it works as expected and will release an update patch for all our users."
I am running the latest version or everything but it appears to still be a problem. I have also uninstalled Acobat XI and tried earlier versions without success. I have a print job to send off tomorrow and I am very nervous about how this will print.

Sorry about that, I apparently forgot to attach the file; have done so now.
The method I'm using for creating outlines is simply to use the "Create Outlines" command under the Type menu within InDesign. Then I create my PDF files by using the Export command under the File menu and choosing the PDF/X1a option. 99% of the time I get perfect results, it's only when I try to make outline type that I encounter this problem. You'll clearly see the artifacts in question in the example attached.
I don't know whether or not the press would have printed these artifacts, as you suggest, since no printer has been willing to execute a file that shows any anomaly in the proof process. I can't say that I blame them.
Hopefully you will see what I'm talking about and can recommend a solution, though I like your idea of simply giving them a properly executed file and then telling them to get a life. It hasn't worked so far, as I unfortunately deal with a lot of Neanderthals around here, but I suppose it's worth putting forth again the next time this issue arises. It will.
By the way, no print house of my choosing is this far behind the curve, if at all. These cavemen are always printers who have long-standing relationships with my clients, and for whatever reason (generally lowest cost I'm sure), the clients think they hung the moon. We, of course, no otherwise, but it does it profit a designer to tell his client he or she is crazy for using a printer who is a decade behind the technology curve.
We cowboy up and seek solutions, eh?

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.

Color change when exported

Using Lr4.1 on PC w/ win7pro laptop with external NEC multisync mmonitor-calibrated, I've taken Raws made LR adjustments, then imported 3-10 images into photoshop layers for masking, merges, few if any color changes. Then save as all layers as a psd, then flatten the psd and save as a tiff. When I open in LR for any other minor tweaks, sharpening, dust spots, and do an export into SRGB or Adobe rgb, the colors are terrible. Look nothing like what I see in LR. I've heard people have minimal issues, but I am having major changes, many times the collors will become dull and flat or very saturated when viewed. As an architectural photographer I need these colors close to what I took. If I edit in CR into PS I don't have this problem. I assume its related to the prophoto RGB color changing, but I really don't know what's going on with the color space. The color will appear different from my laptop monitor to the NEC by a lot which I understand a pro monitor will show more colors, but the color space shift is making a lot of work done in LR useless if I have to redo it all in CR. How can I get LR to export the colors I see in LR into a srgb jpg and Adobe tiff?
Thanks

Lots of steps here:
"Using Lr4.1 on PC w/ win7pro laptop with external NEC multisync mmonitor-calibrated, I've taken Raws made LR adjustments, then imported 3-10 images into photoshop layers for masking, merges, few if any color changes."
How do you get them into PS? What do you mean by "imported 3-10 images into photoshop"? Do you mean you use "Edit in.." from LR, and choose "Open as layers in Photoshop..."?
"Then save as all layers as a psd, then flatten the psd and save as a tiff."
How does it look in PS?
"When I open in LR for any other minor tweaks, sharpening, dust spots"
How do you open in LR? The normal process, after "Edit in..." is that you save in PS, and the image is automatically stacked in LR against the original (or one of the originals, if you open several by "Open as layers in Photoshop..."). How does it look now?
"and do an export into SRGB or Adobe rgb, the colors are terrible. Look nothing like what I see in LR."
Only now they look terrible? They looked OK in LR originally, OK in PS, OK when back in LR, but when you export they look bad - is that right? And as Victoria says, how are you viewing the exported images?
"I assume its related to the prophoto RGB color changing, but I really don't know what's going on with the color space."
It certainly shouldn't be due to colour space changing. The whole point of colour management is that it deals with this.
Final points: you say your monitor is calibrated. You do mean calibrated and profiled with a hardware instrument (Spyder, Colormunki etc)?
And, color settings in Photoshop, they should look something like this:
Choice of working space should be ProPhoto RGB, Adobe RGB or sRGB, but not a monitor or printer profile. Policies should all be "Preserve" and I recommend all the "Ask When" boxed be checked (so you are warned of mismatches).

Red color clips after export to H.264

Dear friends,
I am very new to try use Color. I sent seq. from FCP to Color, changed some clips use Color FX, and than back to FCP.
After export seq. from FCP to H.264 for web, some of the clips appeared red.
Thanks for any answer.
Libor

Do you mean red render bars or the clips are actually Red? With Color you should avoid H.264 until after any rendering. ProRes or Uncompressed are the best codecs to bounce between Color and FCP.
-Noah
Creator of Call Box training series for FCP and Color.

Color space when exporting from RAW

Hello,
I am a new user of Lightroom and I find color spaces topic a bit confusing so far. My main question is: when exporting a photo, does Lightroom convert to a profile or assign a profile? Because there is no way to choose. I tried to export a photo with 3 different color spaces (sRGB, AdobeRGB and ICC profile from laboratory where I print my photos). After exporting them to JPEG it turned out that all of them look differently on my monitor - does it mean that Lightroom assigns a profile? If it was converting, shouldn't they have the same colours? What is more, after printing them in laboratory, results were completely different than I expected - the photo which had closest colours to what I saw in Lightroom was that in sRGB, but that with ICC of Lab was very different (much colder colours).
Where is the problem, or what aspect do I seem to misunderstand? Do I have wrong settings, should I use DNG to work with photos, should I export to TIFF, or I just have too weak monitor or wrongly calibrated one? Should I calibrate when viewing a picture in Lightroom or with the use of a photo exported to the ICC profile of Lab?
I would like to have a little bit of control over what I'm working on, depending on whether I want to publish it on a website or print. I know that my monitor can be a problem (I have an iiyama with IPS), but surely there has to be any way to make results of my work a bit closer to my expectations.
Just for information, my workflow doesn't require Photoshop, as I rather prefer to use only tools from Lightroom. I hope that my problem doesn't require the use of Photoshop.
I will be really greateful for your help - the general knowledge about colour spaces seems to be unsufficient when it comes to the usage of applications such as Lightroom.
Many thanks,
Marcin

Marcin S wrote:
Thank you for you helpful replies. Now I know a little bit more about it. But still, this is not completely clear to me.
My main question is: when exporting a photo, does Lightroom convert to a profile or assign a profile?
Both.
What you mean by both? How should I interpret it? I cannot choose "convert" or "assign", so how they both work together? What does it mean for me wanting to process photo and print in Lab?
I can only add, that those 3 photos which I exported to JPEG with 3 different colour spaces, they look different when viewing outside of Lightroom, ie. IrfanView. But when importing those JPEGs into Lightroom, differences are extremly slight. Is that because Lightroom operates in ProPhoto, which covers all colour spaces which I used, and other programs work in sRGB and those photos differently?
And the last question for now: will the hardware calibrator help in monitor which is, let's say, medium cost and medium quality? I mainly use it for preparing photos to put them on the website gallery, but would be nice if I could print better ones with a bit of certainty about what I will get from Lab.
Many thanks!!
Marcin
When you export a photo from LR, it converts to the colour space you select (e.g. sRGB) and embeds the appropriate profile in the exported file.
If your monitor were calibrated and profiled, and you view with a colour-managed viewer then images should look pretty much identical no matter which colour space you export in. (W7 Photo viewer is colour managed, the XP equivalent isn't, Mac s/w generally is. IE and Chrome aren't properly colour managed, Firefox is for all images, Safari is for images with embedded profiles. Other viewers vary.) With colour-managed viewers, the only difference should be with very highly saturated colours outside sRGB colour space (and then only if your monitor can display those colours).
LR is colour managed. If the monitor isn't calibrated/profiled then I think LR assumes the monitor has a colour space equivalent to sRGB (which is generally roughly right but won't be accurate). Internally LR uses ProPhoto RGB colour space in develop module, but uses Adobe RGB in Library, and previews are stored in Adobe RGB. However, the colour space LR uses won't explain why other viewers show things differently. It's simply that LR is colour managed (which means it converts to/from the image colour space), and I guess the other viewers you're using aren't; they just throw RGB data at the screen without converting.
Is it worth calibrating and profiling your monitor? Quite possibly. Does the colour and brightness vary with viewing angle as you move your head from side to side? If so, it may be TN technology, and perhaps not worth profiling. If it looks reasonably stable with different viewing angle then probably yes.

Color change after 10.4.8 update

After the update, my eyes are picking up a universally light, bluish tinge (not as in light-blue, but as in a small amount of blue in the white) on my display (which is just the Macbook's LCD display, not an external one). Has anyone encountered this? Does anyone know a solution? I have tried to calibrate, but that didn't change anything. Maybe my eyes have something wrong with them, but the whites don't seem as "white" and the silver displayed on Safari's top toolbar doesn't seem as crisp.

I was able to return the previous color profile by copying a file called Color LCD-4271780.icc from another 10.4.7 system.

Color change after merging to HDR Pro, going back into Lightroom

I recently updated Lightroom and now when I "merge to HDR Pro in PS" the photo then comes back into lightroom with highly elevated contrast. I have set the color options to ProPhotoRGB in Lightroom and Photoshop. and the image looks fine when going from LR to PS, and it looks fine in "preview" after saving the image as a TIFF. But once that TIFF gets imported back into LR it has all those weird color changes. I'm not sure what to do, and I never had this problem until I recently updated photoshop and lightroom. Any help you would be appreciated. thanks!

The image will look different in PS than in LR. PS uses the embedded preview and LR uses the actual 32 bit image data. You need to apply the LR Develop module Basic panel Tone settings to the 32 bit HDR TIFF.

File number is changed on export from lightroom

using lightroom 4.3... when I edit a group of photos in lightroom, most of the files will only be edited in lightroom but a few will also be opend into PS6 (by right clicking > edit in>...) Once the PS edits are complete the image is saved & I return to Lightroom. When I export the entire group of images - I set the file name to 'custom name - original file number'. The images I edited in lightroom only - all are renamed as expected (ie wedding photo-1234, wedding photo-1235...). The images I edited in both lightroom & photoshop receive the custom name but lose their file name (ie wedding photo-, wedding photo-1, wedding photo-2, etc.) When viewing these PS edited images in lightroom - they do show the file #, it is only after export that the file # is lost..
Previous versions of lightroom / PS did not have this problem for me.
I wish to maintain the file names for all of the images, help?!?

Thanks Brett, yes - when I open the photo in PS, the file name has changed from i.e. _MG_5720.CR2 to _MG_5720-2. I save the image & go back to lightroom, the image is now called _MG_5720-edit.tiff. When I export, (and in the export settings I rename to custom name - file name) the file now becomes wedding photo--. In previous versions of the software - the file name would have exported as wedding photo-5720-edit.
Can you please explain how I can check how the file names are being changed and see if I can make it so any changes to the name occur before numbers.
Many thanks, Anne

Color different after export

OK image looks great in LR...RAW shot with 5D and edited in LR. Export to desktop,flickr,for email, ANYWHERE I export as jpeg...the color changes. Skin is orangy and yellowie and not pretty.
Here is a link to the example.
http://www.flickr.com/photos/tagp/2227514380/
WHAT IT GOING ON???

First, make absolutely sure you are exporting to sRGB jpeg. If you are exporting to other color spaces and you are not using color managed apps to watch the files (e.g. Firefox 2.0 is not color managed), you will see a color shift. If you are already doing that, Lee is probably right. Vert likely a bad profile. Even if it works in Aperture and other apps. This can happen because Lightroom uses the perceptual rendering intent, while most apps use the relative colorimetric intent. The difference should be almost inperceptible (pun intented), but some canned profiles and profiles generated by certain calibrators have a bad perceptual intent embedded. Also, if you are using dual monitors, make sure that they are the same or that you know what you are doing. Lightroom will usually pick up the profile from the main monitor. But when you then drag the window to another it often does not pick up on the change.

Photoshop 7.0 - Problem Retaining Original Color Space After Export

I just registered for this forum & would appreciate your input.
I convert Canon RAW files to jpgs & always embed the sRGB color profile & color space in the converted files.. Once I open & edit one of these files in Photoshop 7.0 & save it, the color space is changed to Abobe RGB. I have tried many changes via Edit > Color Settings, but still the same results. I thought that the settings preset "Web Graphics sRGB Color Space" would do the trick - but it doesn't.
If I go to Image > Mode > Convert to Profile & select sRGB for both source space and destination space for an opened jpg file, the sRGB color space is embedded in the saved file - even after reopening in PS, editing, and re-saving. Must I do this for each jpg I edit?
Please educate me how to set PS so all exported files either retain the sRGB color space or have PS embed the sRGB color space upon export.
Thank you.

This is of course, an issue of permissions so there may be no solution.
Absolutely not. Don't jump to false premature conclusions. As Noel said, it solely depends on detecting a previous install/ verifying the install media. Since the latter is out of the question, the first would be way to go, the point being that it merely looks for the respective registry keys in HKEY_Local_Machine\Software\Adobe. Lucky for you, back then nobody cared to encrypt such stuff so it could be hacked in manually. Off hand I'm just not aware of the specific structure for the keys, though, but a little digging might turn up that info. In fact it would be almost identical to the ones for PS 7, which might already linger there just lacking the proper vlaues...
Mylenium

Colors change after exporting from 5.2 upgrade

Similar Messages

Maybe you are looking for