Lightroom color accent

My computer had crashed and I couldn't find my lightroom 1.1 program so I downloaded a free trial and it was of 1.3. I was working on a portrait and I had converted it to a black and white and did a color accent with a wand in the 1.3 version. Later I found my program, uninstalled the free trial and put my program 1.1 back on there. Now I can't find the wand that I used to do that with. I had this program for a while and never really used it because I did everything that I needed to in photoshop. I have downloaded the update to 1.3 but I still can't figure out HOW I did the black and white with the color accent. I have searched for 2 days trying to figure it out... can anyone help me?????

Aaah...
In that case, you absolutely have to check out Photoshop Elements. Get the free trial first and, if you like it, shop around for a good price. Several years ago, I was paid a penny to get it! At the time, the list price was $69.99 but the retailer had a $30 rebate and Adobe had a $40 rebate for those with a previous version. I paid the $69.99 but got $70 back in rebates!
The full Photoshop is horrendously expensive but, if you have a teacher in the family, the educational discount is phenomenal.
By the way, PS and PSE support layers, which makes a lot of photo work real easy. Here's some of my shots.

Similar Messages

Camera Raw 5.5 VS Adobe Lightroom (color correction)

Hi, does somebody know if discarding the advantage of making layers of Photoshop, is the Adobe Lightroom color correction controls superiors to the CameraRaw PS Interface correction controls ??? I mean for color correction purposes is Adobe Lightroom better tan PS's camera raw interface ???? because for me both controls seem to be pretty much the same thing, does anyone know something about it ??
Thank you in advance !

RicardoAngelo wrote:
I mean for color correction purposes is Adobe Lightroom better tan PS's camera raw interface ???? because for me both controls seem to be pretty much the same thing, does anyone know something about it ??
Both Camera Raw (most recent version) and Lightroom (most recent version) share the EXACT same processing pipeline...however, there are subtle differences in usability. For example, ACR 5.6 has a Point Curves Editor...Lightroom doesn't. Lightroom has a powerful capability to control output size and resolution which Camera Raw doesn't have...
Bottom line is they are two horses of a different color but each is capable of performing the same tricks...so use whichever app allows you o accomplish what you need to do in the shortest and easiest process...

Adobe Camera Raw and Adobe Lightroom color profiles ....

Adobe Camera Raw and Adobe Lightroom color profiles .... for sony cameras

Adobe Camera Raw and Adobe Lightroom color profiles .... for sony cameras

Lightroom color cast question of JPEG image

Lightroom color cast question of JPEG image
Camera Canon MKII Color Matrix Adobe RGB
Photoshop CS Color Setting Adobe RGB (1998)
Lightroom 1.2 as new lightroom user I did not think that I needed to choose a color setting or color profile until I am ready to print my photos. I have not done any preset camera calibration.
Link to my website with example photo http://www.basecampphotos.com/color.jpg
My question is why is Lightroom displaying the images with a yellow color cast ? The image is a print screen from Lightroom on the left and Photoshop on the right The color cast problem can be seen in the white walls of the stairway. Also when viewing the image with Windows Picture and Fax viewer the walls are white as expected.
Any ideas or suggestions as to why Lightroom is displaying the images with the yellow color cast or what I need to do to correct the issue ?
Thanks
Jim

Almost definitely a corrupt monitor profile. Time and again this turns out to be the cause of such differences between PS and LR. You need to recalibrate the monitor or if you do not have a hardware calibrator, delete the profile from windows' monitor properties pane to test and then get a hardware calibrator.
P.S since you are using adobeRGB jpegs, Windows picture and Fax viewers cannot give you the correct colors even on a calibrated monitor. Those are not color managed programs (I believe picture viewer finally is in Vista but definitely not in XP which you appear to be using). Also, PS has to be correctly set up to always preserve embedded profiles and to ask when you have profile mismatches, otherwise even PS will give incorrect color. Make sure to set this up in Edit>Color settings.
P.S.2: Make sure you are not applying defaults in Lightroom to your images either on import or elsewhere. Sometimes people by accident define develop defaults that in this case might contain a white balance shift. Go to LR preferences and open the Presets tab. Here click on "Reset all default Develop settings" and make sure that only the auto grayscale checkbox is ticked. For images that it might have already happened to, make sure to hit the reset button.

Can't get Lightroom Color Management to select custom profiles

I can't get Lightroom Color Management to select custom profiles.
- I select "other" in Profile,
- a pop-up box shows me numerous profiles to choose from
- I select a profile and the selection is highlighted
- I press "OK" and the pop-up box disappears
- but if I go back to the "Profile" selection line, only "Managed by Printer" is available.
What's wrong here?
Is the inability to select a profile the reason that prints from Lightroom look way to dark when I print them?
Vick

Oh, I'm on Windows, XP with SP2.
The profiles are in C:\WINDOWS\system32\spool\drivers\color
I used the .exe that was provided by Epson for installing the drivers.
Nothing fancy, nothing different.
For Lightroom, I installed it off CD, and got the 1.3.1 update off their Adobe site.
Any clues there, to solve the puzzle?
Vick

Logic of Lightroom Color Management

There are, I know, endless posts about Lightroom color management issues. This question, I hope, will be somewhat different, as I don't have a specific problem, yet, but am trying to understand the logic of the software in the hope of avoiding problems down the road (as when I add file types, e.g.) I am also reading a book on color management, but it is on general theory with specific references to Photoshop CS3 (or 2), not to Lightroom. So here are my two questions and I'm hoping that the answers, should I be fortunate enough to receive any, will help not only me but other neophytes.
First, the Adobe online manual says this: "For rendered files such as TIFF, JPEG, and PSD files, Lightroom uses the images embedded color profile to display the image, histogram, and color values. If the image doesnt have a profile, Lightroom assumes the sRGB profile, and the image may not look as expected on your monitor." Clear enough, but what does CS3 do when it is launched from Lightroom to do pixel editing on an image primarily managed in Lightroom? That is, if CS3 is used essentially as a Lightroom plugin does CS3 adopt the Lightroom color management or does CS3 independently have to be set appropriately for the image to appear the same in CS3?
Second, the online manual says this: "Raw photo files generally dont have embedded color profiles. For raw files, the Develop module assumes a wide color space based on the color values of the ProPhoto RGB color space. ProPhoto RGB encompasses most colors that cameras can record." This is confusing, at least to me. Consider the paragraph above in this post, where the manual explains (or at least intimates) that if you create a file with values of a broad gamut such as Adobe RGB but don't embed that profile Lightroom will think it has a narrower gamut, sRGB file and the display will be off (unsaturated and washed out, I presume). That makes perfect sense. But why, then, does Lightroom assume for RAW files the wide Prophoto RGB color space when a camera might not record across this gamut? Wouldn't a camera that records in a narrower gamut cause the same problems for the display as does an Adobe RGB file read as if it were an sRGB file?
Thanks in advance.

>For rendered files such as TIFF, JPEG, and PSD files, Lightroom uses the images embedded color profile to display the image, histogram, and color values. If the image doesnt have a profile, Lightroom assumes the sRGB profile, and the image may not look as expected on your monitor.
Funny but if this came from the manual it is actually incorrect. For tiff, jpeg and psd files, the image is rendered into the linear lightroom color space using the embedded profile or assuming sRGB if there is no color tag on the image. The histogram Lightroom shows is always based on the Lightroom color space with a gamma 2.2 toning curve applied no matter what the source of the file. To answer your question, if you do an "edit in CS3" from Lightroom a copy of the file is rendered in the color space that you requested in the dialog and CS3 uses that space if your Photoshop is correctly set up to respect embedded profiles.
>Raw photo files generally dont have embedded color profiles. For raw files, the Develop module assumes a wide color space based on the color values of the ProPhoto RGB color space. ProPhoto RGB encompasses most colors that cameras can record.
The manual is again not correct here! Embarrassing. I have never seen a RAW file with an embedded profile so generally is incorrect. Also, for RAW files, the module DOES NOT assume prophotoRGB color space. The actual primaries are actually stored in a internal database that is based on calibrations that Thomas Knoll and other ACR engineers did of the specific type of camera. They ARE not the prophotoRGB primaries. The RAW files are rendered into MelissaRGB using those primaries. MelissaRGB has ppRGB primaries but a linear gamma instead of 1.8.
>hat makes perfect sense. But why, then, does Lightroom assume for RAW files the wide Prophoto RGB color space when a camera might not record across this gamut? Wouldn't a camera that records in a narrower gamut cause the same problems for the display as does an Adobe RGB file read as if it were an sRGB file?
See above, the manual is wrong. Lightroom knows the actual gamut of your camera and uses that, not prophoto.

Color accent application for N8

Hi guys
I love the color accent option in shooting pictures and wondered whether there is an application for my nokia which will enable this feature on my phone
An example of what I mean: http://farm2.static.flickr.com/1017/627354251_f656f4f54b.jpg
Thanks for any help in advance

You can find them on the Nokia (or ovi) store app on your phone or here:
http://store.ovi.com/search?q=prayer+time

Lightroom Colors do not Match Windows

I have spent hours and hours trying to figure this out to no avail.
Dell u2410 monitor
Colormunki
Lightroom 4.3
Windows 7
I have gone through and calibrated the monitor according to Colormunki directions. It says it's saving a profile that windows and all of my programs will use. If I process a photo exactly as I want then export it srgb profile to my desktop and open with any other windows program it's significantly more pink.
I've looked through all of the advanced tab settings in color managment in control panel, but it's super confusing. How do I make what I'm editing to in lightroom match what I see in windows?
BTW...I had this problem before I calibrated the monitor as well, which is why I calibrated it. Actually it looks like windows views changed, but lightroom colors don't look any different than before profiling.
I'm so frustrated, this shouldn't be this difficult. I need to output some photo's to print in the next day or two and I now they are going to be messed up because I can't see the correct color.
Thoughts?

The effect produced by ColorMunki and similar tools consists of two independent parts: calibration and profiling.
Calibration is the process of adjusting your monitor/video card hardware to make it "as perfect as possible", i.e. to make your monitor and video card to display sRGB colors as accurately as possible by using their respective hardware adjustment capabilities. For monitor that involves adjusting brightness, contrast and independent RGB channel gains. For video card that involves loading so-called "color lookup table" (LUT) with more-or-less finely tuned values. Since calibration is a hardware adjustment, everything you do during calibration will affect all software running on your system, regardless of whether it is color-management-aware in any way or not. As long as the software sends sRGB data to the monitor, that data will be displayed more accurately after more accurate calibration.
However, with a typical monitor and/or video card calibration can only produce a roughly accurate results. It cannot make your monitor to work as a perfect sRGB device. There's simply not enough precision and/or flexibility in monitor controls.
So, this is where profiling comes into play. Profiling is perfomed after calibration. Profiling records all deviations from "perfect sRGB" your calibrated monitor still has, and stores these deviations in a color profile. Later, any color-managed software will pick up that profile. By using the data stored there, color-managed software will be able to dial-out any color imperfections your monitor still has after calibration. For example, if your calibrated monitor is still greenish, the profile will say that it is greenish, and the software will automatically dial-out some green from the image data before displayng it. The combined effect of the image data being "de-greened" by software and then "over-greened" (by the same amount) by the monitor will produce ideal (non-greenish) display.
However, only color-profile-aware software will use profiles and perform such adjustments to counterbalance calibration imperfections. All other (non-color-managed) software relies on calibration and calibration alone. So, in the above example, non-color-managed software will display greenish pictures while color-managed software will display the pictures perfectly.
Apparently, this is something that happens in your case. When you used your ColorMunki, did it ask you to use your monitor's RGB controls to adjust the channel gains independently in order to arrive at some white point? Does white look white your monitor or does white also look pinkish?
What your can also do is forget for a second about profiling software. Open your monitor's control panel and adjust it manually to your liking. Dial out any pinkness by using RGB controls (or use some standard preset). Adjust brighness and or contrast to the point where they "look good" to you. You may use some test picture and adjust the monitor manually to the point where the picture looks good to you.
Now, once you finished that, you can start the ColorMunki software and use it to profile your monitor only. Profile only. No calibration. Do not adjust anything, regradless of what ColorMunki tells you to do. Keep the current settings on your monitor and make ColorMunki to generate a profile for it. That way you will get the look you like in non-color-managed software while at the same time getting accurate display from color-managed software.

LIghtRoom color problem vs PhotoShop CS2 on Nikon RAW

I recently bought Adobe Lightroom and I was surprised to notice some huge color differences compared to PhotoShop CS2.
Im using Nikon D80 and shooting RAW. I have calibrated semi-pro monitor.
The same RAW file opens in LightRoom pretty well until you get the rendering preview. Once the preview is done, the picture becomes desaturated in red and blue and has a green cast especially in the shadows with much lower contrast. If I use Edit in PhotoShop option, the picture becomes even worse (even more desaturated and greenish) when opens in PhotoShop. If I open the same RAW in PhotoShop directly (using the NEF plug-in, not CameraRaw!) everything is just fine. The picture looks as opened in Nikon Picture Project or as I saw it when I took the picture.
After doing some research, I think that my problem relates to the way that Adobe Camera RAW, Bridge and LightRoom open a Nikon sRGB 4.0.0.3001 (D80) raw file. However, all the things being equal, PhotoShop CS2 (using the NEF plug-in) renders the same colors as Picture Project does (and what I saw on my camera and in reality). I also noticed that choosing sRGB in Camera Raw bring the things closer to the Picture Project colors but far from identical. Anyways, there is no way to change anything in LightRoom, outer than manually twicking all colors until I think it looks good. Which, I think Is very subjective and is different for every picture.
Right now, my Creative Suite Color Settings is North America General Purpose 2 (synchronized for all CS applications) and no application asks me anything about changing the color profile when opening the file. I shoot (with D80) in raw, Normal camera mode (no saturation / contrast, color profile change). I opened the same file in all mentionned applications (LightRoom, CameraRaw from Bridge, PhotoShop and Picture Project) and save them as .jpeg (same size, dpi, etc.) without changing anything (no camera calibration in ACR or LR; no printer profile in PhotoShop). I sent the .jpegs to my local Costco and printed them on glossy paper. All of them printed the same way that they look on the screen. LR, ACR - desaturated on red&blue, color cast on green and low contrast, while great vivid colors and contrast from PhotoShop and Picture Project. For me it looks pretty much as Adobe applications convert Nikon sRGB into a very unappealing Adobe sRGB (and way different from what I saw in reality). I know this is very subjective; some people may argue that Nikon profile is too reddish and oversaturated. But I find the whole story rather unusual. They all work in the sRGB space and there shouldn't be any differences. I've done lot of testing with color profiles and replacing the Camera Raw plugin file format (common files) with Nicon plugins and vice-versa. But still the same result.
I create a User Profile in LightRoom and I get pretty decent colors now, but when I want to edit the file in PhotoShop (from LightRoom) I get the same green and desaturated version.
What do you think?

>Regarding LR, what I'm looking here is a "factory made" solution; something that can give consistent results in the initial conversion (like Nikon plugin for PhotoShop, for e.g.)
The problem with that conversion is that you cannot change it. In lightroom you change the actual conversion parameters, which gives you far more leeway and allows for far better conversions in the end. Currently (this will change with Lightroom 2.0 apparently) the only recourse you have if you prefer Nikon's colors is to shoot jpeg, or run your NEFs through capture and create 16-bit tiffs. This is just the way it is. A hammer gives a different result than a screwdriver.
>It's hard for me to believe that Adobe has invested so much energy and resources in color profiling but it's unable to get nearly close to the Nikon raw colors.
Nikon's colors are far from colorimetrically correct which you can see in many tests. Here is an example for the D300: http://www.imaging-resource.com/PRODS/D300/D300IMATEST.HTM It is off in the deep reds, the saturated blues, and the Olive-like colors. Profiling the camera does not help you get close to Nikon's colors, but it will get you closer to the ideal colors. I doubt it has been Adobe's goal to get close to the in-camera rendering with Lightroom upto 1.4. They profile all the cameras and make some value judgments on what is more important. Skin tones vs saturated colors etc just like Nikon does.
Regarding getting close to camera colors, there is a trick that you can do to get close to the camera jpeg that involves the ACR calibration scripts. You do need PS CS3 though.
>I find rather strange that apparently there is no way to get professional conversion. This is defying the main purpose of Color Profiling, I think.
Why is Nikon's conversion professional and Adobe's not? They are both just interpretations of the sensor data. Adobe's is actually colorimetrically more correct in many cases. Colorimetrically correct often means boring unfortunately. This has to do with the fact that our eyes are not color measurement devices but that we have brains interpreting the data. To get pleasing results, Color Profiling does not help as much as you'd like. My issue with the in-camera or Nikon software approach is that it locks you down creatively to the
creative choices the Nikon folks made. Now, be aware that in the Lightroom 2.0 forum the Adobe folks have hinted at major changes to the rendering engine that will bring colors closer to the vendor rendering. How they will do this is unknown right now.

Camera Raw vs Lightroom Color Spaces

I photographed RAW image of a Gregtag color target with my Nikon D300 and opened it in camera raw in the ProPhoto Color space and adjusted the develop sliders so that the tone squares on the bottom row matched the ProPhoto values, (e.g approx 238,189,144,103,66,37) and ran the Robert Fors calibration script.
So far so good. I have read that all one needs to do is use the same settings in Lightroom. But when I opened the exact same RAW file in Lightroom and use the exact same develop and calibration settings that I used in ACR, it gives different values for the tone squares. And in fact the values are almost exactly the values for Adobe RGB (e.g. approx 242,200,159,121,84,53). And when I open that file in Photoshop from Lightroom using the ProPhoto color space option the value stay at the same Adobe RGB levels within the ProPhoto color space.
What am I missing/doing wrong?

the values in lightroom are not based on prophotoRGB, but on a prophotoRGB-derived space with the same primaries but with a sRGB tone curve. Since adobeRGB has almost the same tonecurve as sRGB, your values came out close. Bottomline is that the values do not correspond to the ppRGB values in ACR.

Why does Lightroom color not match when editing in Photoshop CS3

I just started Using Lightroom 4, the only version of lightroom that I have used. Short version, saves me heaps of time. But I went to edit more in photoshop and noticed that the color is dramatically different. I have Photoshop CS3 (10.0.1)and the color space is ProPhoto to match lightroom. If I make edits in lightroom, say removing dust spots, it shows in the photoshop version. It seems that on the shadow side is where it really shows. My workflow would be to import as original RAW in lightroom 4 (canon 1d mark II) and go about editing. Right click to edit in Photoshop CS3, and this is where colors go crazy. Then if I save the file with no edits done in Photoshop and compare side by side in lightroom, they are completely different. What is causing the drastic difference?
These are screenshots where in the left screenshot the original image is the dark image and the lighter is what it looks like when opened in Photoshop. The compare in lightroom on the right screenshot is what it looks like when I saved the file from Photoshop. So how does opening in Photoshop, then hitting save change the image? If i make the edit in lightroom then export the jpeg and open in photoshop, I get the appropriate color, exactly the same as my original lightroom raw.
My external editor settings in lightroom are tiff, prophoto colorspace.
photoshop preferences are to preserve embedded profiles.

Just to make sure we're talking about the same thing, when you "Edit in" Photoshop CS3, it should give a warning dialog that says the version of ACR in Photoshop isn't compability, with the option "Open anyway" (won't work well) or "Render in Lightroom" (which should be fine). Or, if you've created your own "Edit in" preset, you should get the option "Edit a copy with Lightroom Adjustments".
So long as you've chosen "Render in Lightroom" or "Edit a copy with Lightroom Adjustments" (depending on how you've edit up "Edit in...") then colour should be OK.
Colour options in PS should be something like:
Check all the "Ask when..." options, just to make sure you get warned of mis-matches. And I suggest the RGB policy should be "preserve...".
And the final thing: to be sure of no colour mis-match, you need a calibrated/profiled monitor (with a hardware tool like Spyder, ColorMunki, Eye-One etc). When there isn't a monitor profile containing a colour space (which needs a hardware tool, generally) then different programs can make different assumptions and display the same image differently.

Lightroom color labels lost on transition from one pc to another

I started using a mac laptop in the field and always used windows pc at home. A portable hard drive holds the lightroom catalog. It's fat32 formatted so it can be used by both mac and windows.
A catalog made by the mac lightroom opens fine in windows. However, all the color labels are lost. The flags and stars are retained.
If a color label is changed on a photo by the windows version of lightroom, then when that catalog is opened on the mac, that photo has no color label. (even though the mac originally gave it a color label)
And all the original color labels that were made by the mac magically return as they were assigned.
To trouble shoot this, I installed the Lightroom 3.6 trial on 2 other pcs - one runs windows 7 32 bit and the other windows 7 64 bit. These installs see the mac created catalog properly.
All the color labels are there and changing one on a windows box is properly reflected on the mac when that catalog is opened.
This is so annoying.
My main pc must have an allergy to my mac.
I removed and reinstalled lightroom on my pc-same problem.
Now i have to figure out what is interfering with my main pc lightroom install.
It cant be lightroom cause i removed it and reinstalled it. but it might be one of the plug ins i use. these magically reappearred even after i reinstalled lightroom after removing it.
Anyone have suggestions?

The color labels are preserved between different programs (for instance between Bridge and Lightroom) and I imagine between different LRs on two different computers only when the texts entered as description for the color labels in >Metadata >Color Label Set >Edit is absolutely identical on both computers down to upper / lower case, spaces, numbers, hyphens, etc. If one dexcription for - lets say the red label - deviates from the other by only a semicolon the label will not display properly.
WW

Why when I open my raw files into lightroom, colors are different from my camera's preview?

Ciao,
I have a problem... maybe this can be a stupid question but anyway.. I would like to know the reason why when I open a raw image in lightroom, for a second I see the right colors/tone/contrast that i see when i look at the same images on my camera and soon after the word "Loading" I see the raw files with different colors.
Why this happens???
Before "Loading" and --> after
Thank you so much

Hey Giuseppe
I have a similar problem but the cause may be different from yours. I shoot a Canon 6D and as far as I know no one with the 5D MKIII has my issue, but maybe you could look into it.
Canon's Adobe Camera Raw in Photoshop CC, as well as Lightroom CC, is automatically down converting my CR2 RAW files from 14 bit color depth to 8 bit color depth. This is screwing up my colors, contrast, gradients, etc quite a bit when trying to process RAW files in Photoshop CC and Lightroom CC.
You can read my thread here:
Banding due to automatic downconverting of RAW files to 8 bit
You might want to check and see if your RAW files are actually being processed in 16 bit color depth. There is a possibility that they are being down converted automatically for some reason.
The bit depth in Lightroom for RAW files is supposed to be 16 bit but when opening my files it just converts it down.
Try downloading Canon's Digital Photo Professional 4
Canon U.S.A. : Consumer & Home Office : EOS 5D Mark III
Use that software to process a RAW photo and convert to a 16 bit TIFF. I know this software truly gives you a 16 bit depth image. Then compare the result side to side with what you're seeing in Lightroom.
If you are having this issue, I have not yet found a way to process RAW CR2 files in ACR or Lightroom and maintain 16 bit depth.
If you are batch processing to JPEGs it probably doesn't matter, but my issue is that it is down converting BEFORE exporting and thus any edits I do become much more destructive on my 8 bit image than they would if I was editing a 16 bit image. I have to be able to keep things in 16 bit up until the point they go to the printer.
Sorry, this may not help you at all, it looks like there could just be a difference in White Balance, but I figured I'd throw my two cents out there and maybe you could see if this is actually what is happening for you, and hopefully eventually Adobe could potentially fix this bug.

Lightroom, Color Temperature, Kelvin

Is there any way to have Lightroom how the color temperature in Kelvin
instead of what it is using? Or does someone has a chart that equates the LR
numbers to the degrees Kelvin?
I wish Adobe would stick with standards with such things. It is bad enough
when you use the white balance eye dropper that the grid enlargement you see
when it is over the image shows the RGB values as a percentage instead of
what Photoshop shows you. It is very hard to get close to 128 128 128 when
your using a percentage. Again, Adobe started the use of certain methods in
Photoshop so I don't know why they can't be consistent.
Robert

Jim,
My understanding is that an absolute K whitepoint does not strictly make any sense for relative-colour JPEGs. This has been hashed out, ad nauseam, on other threads.
That is, the controls provided are intended to be /correct/, and not just convenient.
I don't have a dog in this fight, but I prefer correct interfaces myself.
I'm actually having trouble coming up with a case where an absolute Kelvin setting is of much use, anyway. I suppose if you know that 5300K was likely the temperature of the colour on a particular shoot it might be useful. But, if you already know that why not set the camera to the same value? If one needed absolute K (say, for legal or scientific reasons) I suspect one might be shooting raw, and using a pre-set whitepoint.
At any rate, my advice is to post this as a feature, which (I understand) will probably be interpreted to mean, "provide access to absolute K values for whitepoint for file formats that can only represent relative temperature, quantizing and approximating in some cases to get as close as we can, within some arbitrary limits."
I'd have to go look at the other thread and do some more research, but this, I think, is the crux of the matter. Misunderstandings and errors on this matter are, of course, all mine.

Photoshop Edits Import into Lightroom, Color/Noise Problems

Hello! When I edit photos in Photoshop (CS5), it looks completely different when I save it/re-import it into Lightroom. The color is usually way off, and there tends to be a significant amount of noise in the imported version. Tiffs v. Jpegs makes no difference. I read in another forum that someone else said he only has this problem with his Canon 7D files. My files are all Canon 7D. Would that be a Canon problem to solve, or Adobe? I'm attaching a screenshot of an image I had just saved in Photoshop, and then how it appears when it automatically re-imported back to Lightroom. Thank you for any help you can provide. It's killing me to work so hard on my images, just to have them look completely different afterwards.
Thanks, Heather

Looks like you are applying a preset, have set camera defaults, or have enabled auto-tone. In Develop, all sliders should be at zero for tif files. You probably have a large amount of shadow fill dialed in. Go into your preferences and make sure to uncheck "apply auto tone adjustments" Also reset all default camera adjustments in the same dialog. Then hit reset on the file in develop.

Lightroom color accent

Similar Messages

Maybe you are looking for