![]() |
![]() |
![]() |
|
|
|
||||||
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
#1 (permalink) |
|
Alpaca
|
Hi All
Can anyone explain why the image I see in the Lightroom Develop window doesn't quite match when I open it in Photoshop after export from Lightroom? It's pretty close, and easy to correct, but I would prefer the Lightroom file to look identical when opened in Photoshop. My Lightroom Export setting is set to AbobeRGB and the Photoshop Color Setting is set to a Working Space: AdobeRGB. As I understand it, Lightroom doesn't assign a working space to the raw file until export, where you can then choose to export it as sRGB, ProPhotoRGB or AdobeRGB. So does that mean that what I see in the Lightroom Develop window is the profiled Monitor color space? If so, is Lightroom converting from Monitor color Space to AdobeRGB color space on Exporting?. And if that is the case, why is there a small disparity in the conversion? Thanks Peter __________________
__________________
Members don't see this ad. Register your free account today and become a member on PhotoCamel - Your Friendly Photo Community, gaining access to posting privileges, contests, free plug-ins and other downloads, unlimited online storage for your photographs, reviews, free marketplace listings, and much more. |
|
|
|
|
|
#2 (permalink) |
|
F1 Camel
|
I never actually see differences in colour spaces until I print or post to the web.
|
|
__________________
-mcbit 'Twelve significant photographs in any one year is a good crop.' Ansell Adams www.pbase.com/mcbit |
|
|
|
|
|
|
#4 (permalink) |
|
F1 Camel
|
Are you using the "Edit in Photoshop with Lightroom adjustments" option in Lightroom?
|
|
__________________
-mcbit 'Twelve significant photographs in any one year is a good crop.' Ansell Adams www.pbase.com/mcbit |
|
|
|
|
|
|
#5 (permalink) | |
|
Alpaca
|
Quote:
![]() |
|
|
__________________
SureFire __________________________________________________ __________________________________________________ (2) 40D w/ Grips | (3) 580EX II's and CP-E4's | (4) PocketWizards | 10-22/3.5-4.5 | 17-55/2.8 IS | 24-105/4 L IS | 60/2.8 | 70-200/2.8L IS | 85/1.8 | 100-400L IS |
||
|
|
|
|
|
#6 (permalink) |
|
F1 Camel
|
When you edit in PS, LR will convert the RAW to a TIFF or JPG as you have set and embed a color profile. Depending on the way you have things set up, your color profiles may not match. The move from LR to CS3 edit is not an export, so that setting doesn't apply. I'm thinking that the LR conversion to TIFF when you select Edit in CS3 embeds the color space of ProPhotoRGB (at least mine does, but I prefer to work in ProPhotoRGB in CS3). In CS3, check to make sure that you have the box checked to alert you when the color profiles are mismatched or to convert to the working profile. I believe this will clear up your problem.
|
|
__________________
'A government big enough to give you everything you want, is big enough to take away everything you have. - Thomas Jefferson |
|
|
|
|
|
|
#9 (permalink) |
|
F1 Camel
|
With PS default settings if you change the colour profile of an image in PS you will see no difference in that image on screen in PS.
If you change the external editing profile in LR the document you see on screen in PS remains the same as the image is displayed in the PS current workspace profile whatever its embedded profile. If you print these documents or display on the web you will see a difference. If you make adjustments in LR then open directly in PS or through Bridge you will see the original unadjusted image. LR is non-destructive and the adjustments are only visible from within LR unless the image is exported to another file. The OP was not clear about how he opened the files in PS. ![]() |
|
__________________
-mcbit 'Twelve significant photographs in any one year is a good crop.' Ansell Adams www.pbase.com/mcbit |
|
|
|
|
|
|
#10 (permalink) | |
|
F1 Camel
|
Quote:
In Color Settings, you have the option to preserve embedded color, ignore mismatches, or convert to your working space. I prefer to preserve the embedded color and have it warn me of mismatches so that I can control how I want to edit that particular file. If you set it up to convert any mismatch to your working space, the engine will remap the colors prior to opening the photo and you won't see any differences. If you choose to ignore the color mismatches, you're on your own You will have color issues in most instances. |
|
|
__________________
'A government big enough to give you everything you want, is big enough to take away everything you have. - Thomas Jefferson |
||
|
|
|
|
|
#11 (permalink) |
|
F1 Camel
|
But the DEFAULT setup in CS3 is to display the images in the workspace profile. I've tried it in both my copies of LR and PSCS3 and the images on-screen in PS do not change. If I mismatch the profile it will only show up when I print or post on the web.
That's what happens to me anyway. |
|
__________________
-mcbit 'Twelve significant photographs in any one year is a good crop.' Ansell Adams www.pbase.com/mcbit |
|
|
|
|
|
|
#12 (permalink) |
|
F1 Camel
|
The default is converting it to your workspace, which is fine. That's why you don't see a color mismatch. I really don't remember if that setting is default or not, but I'll take your word that it is. The point is that mismatched profiles need to be addressed, either automatically or by the end user.
The problem with posting pictures on the web or any program that isn't color managed occurs when you're using a profile wider than sRGB. The web browsers (except Safari and now Firefox 3.0) and many image viewing programs don't understand color management. sRGB color space was originally developed so that it most closely resembled what one sees on a monitor for a PC (Joint venture by Microsoft and HP, I think). It's not that the web reads sRGB, but rather that the gamut of sRGB falls within the parameters. AdobeRGB falls outside that gamut and will result in colors that appear muted and flat when viewed in such programs. The print issue is another issue in itself. Printers don't actually use a color space, at all. They use a printer profile or an engine that deals with the colors. Depending on how you are set up, sRGB is often the safest choice. When using proper color management and printing from a color space aware program, the color space and the printer profile work together to produce the correct colors in output. In non-color managed workflows, color spaces outside of sRGB will likely give you problems. Personally, I use ProPhoto RGB as my working space throughout my workflow, from RAW conversion right through printing, but my workflow is based on color management practices, calibrated and profiled monitor, and a custom profile for my printer and each paper I use. If I were to send my images to an outside source for printing, I'd either use their profile or convert it to sRGB, depending on their needs. __________________
__________________
Members don't see this ad. Register your free account today and become a member on PhotoCamel - Your Friendly Photo Community, gaining access to posting privileges, contests, free plug-ins and other downloads, unlimited online storage for your photographs, reviews, free marketplace listings, and much more. |
|
__________________
'A government big enough to give you everything you want, is big enough to take away everything you have. - Thomas Jefferson |
|
|
|
|
![]() |
| « » |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Photoshop Bridge or Photoshop Lightroom | freddiebear | Computers and Software | 21 | 03-21-2008 09:04 AM |
| Some Produce | d2creative | Commercial Photography | 5 | 02-28-2008 08:36 AM |
| 60 photoshop actions & 24 FREE lightroom presets $10.99 | Jimmyz | Marketplace | 0 | 11-14-2007 01:30 PM |
| Photoshop Lightroom | Jose | Image Editing and Color Management | 6 | 03-24-2007 02:09 PM |
| Complimentary copy of Photoshop Lightroom is now available. | Rense | Image Editing and Color Management | 15 | 02-25-2007 02:53 AM |