Invalid Color Management in Lightroom? (RAW)

I've noticed the strange thing, how Adobe Camera RAW 4.1.1 displays the same image differently in Photoshop CS3 & Lightroom 1.4.1
Here are the screenshots from both programs:
What I've got in Lightroom/develop mode:
http://www.imagebam.com/image/956c3d6537871
What I've got in Photoshop:
http://www.imagebam.com/image/17a67c6537874
Notice the reds on the face and oranges on the trees on the background. 1) Face on second, photoshop variant is more reddish. 2) The contrast differs as well!
3) There is more orange on the leaves on the second image.
That's all happens in the preview in Lightroom - if I export image as a JPEG and open it in Photoshop - the images will be the same. But BEFORE the export they're DIFFERENT! What's wrong?
(Image is shot on Sony Alpha 350, white balance and all the settings in Camera RAW are the same in two programs).

>yes they are, but in practice PDF causes lot's of bugs.
My experience is opposite in that pdf is usually the only thing that actually works for multipage documents and things containing vector graphics. For single page photos of course tiff always works, but there are lots of clueless operators that do not know their behind from a color profile.
>In my experience colors will be different even for an eye of a consumer. On some printers red will be more reddish, on others green more greenish etc. The contrast will differ either. Maybe you and we use different printers. BTW I work on Windows, maybe that's the point.
I have always had basically perfect results. There was a time when Lightroom interacted wrong with printer drivers when you used profiles inside of the program instead of having the printer driver manage for you. This has long been fixed. Of course there are subtle differences between printers and it would be good if Lightroom had some sort of soft proofing to judge this in advance. The differences are usually pretty minor though nowadays.
>Well, Noritsu, as I know, for example, uses its own color management profile, which you cannot tune even in Photoshop. If you use sRGB, it will be ignored, and you'll get a very low contrast print with desaturated color and you have to be there when it's printed to tune it with the lab assistant. Usually they do it themselves ... well... good. I have SOME good experience with Costco. But for many cases I can't get my colors and contrast without being there when it's printed. And it depends on paper - is it metallic, for example, or matte. The picture will be different. The colors will be different. And you can't check it exactly on your monitor being at home, or in office.
I tested this extensively. If you do this right, it is very hard to see the difference between a sRGB print and a print converted to the profile. With well-tuned Noritsus, you get a small difference in oranges, and a tiny difference in greens - independent of the paper you use. This is the whole point of these machines. If you feed them sRGB, they should give you great results. Maybe my local costcos is very good, but I doubt they are very different from other labs. I tried both Matte and Glossy and they both showed the same result. This is borne out by softproofing in Photoshop that shows exactly the same effect. Note that I wrote about using lab profiles with Lightroom extensively and always tell people to use the profile, but in reality it really is not that important.
See for example: http://lagemaat.blogspot.com/2008/05/great-prints-from-labs.html
If you see large differences in contrast and saturation, there really is something wrong with your calibration workflow or your lab. FOr good prints, the only thing they need to do is to turn off their auto color correction, which with most labs you can do automatically in the online submission pages. I should tell you that you do have to judge prints under good lighting. Often these differences are simply caused by one day being sunny and the other overcast when you walk out on the parkinglot and take out your prints. This is not a real difference. Use a good high color rendering index lamp of high color temperature and you will see that they were the same. My local costcos is calibrated by drycreek photos every month and the profile hardly changes at all over time.
>I don't know, Jao, maybe your point in photography is different, and you don't pay so much attention on colors. These things are subjective! Maybe you pay more attention on other components of photo. In my experience it takes lots of time to prepare a 40"x30" photo for print and then it takes more time and money to colormatch it.
Actually my work is almost always about color. Perhaps I don't sweat it as much. I'd really like Lightroom to have some kind of soft proofing though showing how anal I am about color. I don't use costcos for prints larger than 12x18 as they don't do it locally, but I usually use smugmug's lab (EZprints) for the really large prints. They color manage for you and supply a profile that you can soft proof to if you want. They also appear to scale and sharpen the prints somehow. I've always had outstanding results from them and you can send back the images that you don't like at no cost, although I have never had to do that. I also use smugmug for galleries that clients can order from directly. They have always been very happy with the prints.
>And I work in Windows, maybe your Mac does it better, maybe that's the point of my sad story. But Windows is my karma for many reasons.
The point maybe, also, you print every time on the same printing hardware in Costco - that can explain it all.
I have been happy with my costcos and with EZprints, but I doubt that it is much of an issue. As said, I don't use inkjets very often as they are so darn expensive and annoying to operate but I have never had much issue with bad prints. There is no reason why you could not get windows to behave better. The only thing that you need is to calibrate regularly. I have seen on this forum that windows tends to corrupt monitor profiles over time. The issue is always fixed by recalibrating regularly. Once every month should be plenty.

Similar Messages

  • Color management through Lightroom

    I'm using Lightroom and getting poor results from my new iP8720 printer.  How do I turn off color management in the printer?
    Solved!
    Go to Solution.

      KISS
    EOS 1Ds Mk III, EOS 1D Mk IV EF 50mm f1.2 L, EF 24-70mm f2.8 L,
    EF 70-200mm f2.8 L IS II, Sigma 120-300mm f2.8 EX APO
    Photoshop CS6, ACR 9, Lightroom 6

  • Color Management in Lightroom 4

    By default, Lightroom uses the Pro Photo color space "with the same gamma curve as sRGB," according to something I read somewhere. Now Pro Photo is a very wide color space, wider than any monitor can display - even my wide-gamut (Adobe RGB) monitor. If I adjust the color in an image to very high saturation, then at some point in the adjustment I must reach a part of Pro Photo that cannot be displayed on my monitor so I would expect to stop seeing any changes after that point. Yet I continue to see changes all the way up to saturation 100. So this has something to do with the sRGB curve that is somehow mapping those out-of-gamut colors to something that can be displayed.
    I'd appreciate some explanation of this process, or any useful links.
    Thanks.

    Andrew Rodney wrote:
    Bill_Janes wrote:
    I think there is some misunderstanding here. I don't have Lightroom but have looked at Julieanne Kost's video on softproofing in LR4, and what you stated is not my understanding of how the softproofing overlays work. As I understand things, the overlay toggled by the icon on the left does not compare the gamut of Melissa to that of the monitor
    Yes it does, Eric Chan of Adobe had confirmed this in another thread on the beta4 forums and confirmed this behavior is a bug! It is supposed to compare the gamut of the display to the gamut selected in the soft proof mode. As for Kost’s video, the use of the gamut overlay appears to me (and at least a few others) in terms of editing to remove said overlay, a bad idea. See:http://digitaldog.net/files/LR4_softproof2.mov
    As Eric states in the same thread where he confirms the bug, this is more educational than a useful means of editing. Let the ICC profile clip the gamut.
    You didn't give a link to Eric's post, but I downloaded the Lightroom4 beta and checked out the softproofing for myself and compared the results to those obtained in with the gamut warning of Photoshop. I selected an image with out of gamut yellows for both my printer and monitor. I then edited the image so that no colors were clipping on my softproof of the Epson 3880, but there was still some clipping on my profiled monitor (NEC PA 241W) as shown the Lightroom monitor overlay and by Photoshop set to simulate the monitor.  The two proofs were essentially identical, showing that the monitor overlay in Lightroom shows colors in the image that are out of gamut for the monitor. The out of gamut colors are well within the gamut of Mellisa and ProPhotoRGB. The behavior that you suggest would be more useful, since it would show colors that are within the gamut of the printer but out of the gamut of the monitor.
    I agree that editing the image to remove clipping in the overlay is often a bad idea, since the resulting image may appear very unsaturated. It is better to let the colors clip as long as important textural deatil is not blown out.

  • CS3 color management won't match prints

    Okay, I know there are a lot of boneheds who can't figure out how to set up color in Bridge and CS3 but I am at my wits end on this so bear me out.
    Windows XP and CS3
    Bridge is set to; Enable color management in Bridge
    RAW conversion is SRGB
    CS3 color settings/working space set to SRGB
    Print color management is set to SRGB and Photoshop manages colors
    Printer is set to "application manages colors" (HP B9180)(btw, I have also tried it set to SRGB)
    Image looks the same on Bridge, RAW conversion, CS3 and print screen (dark)Image looks LIGHTER when viewed with any other program (including windows picture and fax viewer, HP print program, Paint Shop Pro and online) and prints to match the lighter image both on my HP and from my lab!
    The closest I have been able to get to a total sync is to set Photoshop's color settings to "Monitor color," and uncheck the box in Bridge that says "apply color management settings in Bridge." In that case, Bridge and CS3 produce a lighter image but RAW conversion is still darker. Plus, who the hell wants to use monitor color in Photoshop!?

    That's pretty much it David... I could get Photoshop to match my prints but then any other program would show the prints as being waaaay off-color.
    Today I bought a spider2express and color balanced my monitor. Now everything seems to look in sync and my prints match very close (a little warm for my tastes..). Tech support at Photoshop told me it was a calibration issue but I thought that was bull... i mean, how can calibration make an image that looks different in two different programs look the same? Well, it does. As far as I understand it now (layman's terms)when you look at an image in windows viewer ot explorer or any other non-color management program you are looking at the image based on your monitor profile. When you look at the same image in photoshop the program uses it's own color management which then gets filtered through your monitor program to your eyes (but not to the printer). If your monitor profile is bad, the image looks bad.
    Or something like that :)

  • Color management in hp 8500 officejet premier pro so I can use Lightroom or Photoshop?

    When I print what I see on the Monitor is not what I get on printout.   I don't seen to be able to use the icc profile in either application.  If I let the printer manage the color, they are blue-green overtone.   

    Hi ssprengel,
    Thanks for the reply. I didn't know how these things work but now realise that my profiles seem to have been sitting in windows/system32/spool/drivers/color  since I bought the computer in 2010.
    The guide you referred to suggested that at least one of the profiles on my computer, GL3, should be suitable (there was no mention of GL2) In fact I ended up trying most of my profiles but they all had a very distinct red tint which was completely unacceptable. I even tried specifying and downloading a new profile from Ilford (I can't see where to get these from Canon) but this had the same red tint. When using the profiles I did switch off Color Management in the Print Preferencies, or rather i set it to manual and left all the sliders at zero.
    When i used "managed by printer" there was no red tint and the print looked reasonably good although not quite matching the screen, particularly in brightness.
    It may be worth mentioning that, for the profiles, the red tint was obvious in the print preview. I did not have to wait until the actual print, although I obviously did print to check.
    I did try printing my RAW files to JPEG then printing via Explorer and this ended up around the same quality as "managed by printer" directly from Lightroom
    Any ideas  about what causes the red tint when using the profiles?

  • Lightroom's color management paper options don't match any paper i can buy from Canon

    Up to now I have been using "managed by printer" for printing on my new Canon MG8250. But i have seen several suggestions that i should let Lightroom manage the colors so i decided to give this a go by choosing "other" instead.
    This gave me a list of papers to choose from: Canon IJ Color printer profile 2005, fine art photo rag 2, GL2/SG2, GL3/SG3, MP2, Other fine art paper 2, PT1, PT2, PT3. All the names being preceded by MG8200 series apart from the first one
    However, when i looked up the papers available from Canon, these were all different:  Photo paper pro platinum (PT-101), photopaper pro luster (LU-101), photo paper plus glossy II (PP-201), photo paper plus semi-gloss (SG-201), glossy paper everyday use (GP-501), Matte photo paper (MP-101)
    There are some papers here which look as if they they might relate to the lightroom list eg PT-101 and PT1, SG-201 and SG2 but, at the moment, i am particularly interested in which option should be used to match the photo paper plus glossy II (PP-201) paper which I have bought - GL2 looks as if it might be a contender
    Any help would be most appreciated

    Hi ssprengel,
    Thanks for the reply. I didn't know how these things work but now realise that my profiles seem to have been sitting in windows/system32/spool/drivers/color  since I bought the computer in 2010.
    The guide you referred to suggested that at least one of the profiles on my computer, GL3, should be suitable (there was no mention of GL2) In fact I ended up trying most of my profiles but they all had a very distinct red tint which was completely unacceptable. I even tried specifying and downloading a new profile from Ilford (I can't see where to get these from Canon) but this had the same red tint. When using the profiles I did switch off Color Management in the Print Preferencies, or rather i set it to manual and left all the sliders at zero.
    When i used "managed by printer" there was no red tint and the print looked reasonably good although not quite matching the screen, particularly in brightness.
    It may be worth mentioning that, for the profiles, the red tint was obvious in the print preview. I did not have to wait until the actual print, although I obviously did print to check.
    I did try printing my RAW files to JPEG then printing via Explorer and this ended up around the same quality as "managed by printer" directly from Lightroom
    Any ideas  about what causes the red tint when using the profiles?

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

  • Lightroom (ACR 4) color management problems

    Lightroom (or ACR 4) has some color management problems. When I develop a DNG into Photoshop (sRGB) everything looks great. Then I proof colors for the web (monitor RGB) the reds become oversaturated. I don't see this problem when I develop the same DNG using Bridge (ACR 3).
    Any picture that I develop using LR that looks great in Photoshop, becomes way too red when published on the web.
    Whats going on here?

    I have confirmed this finding using Photoshop CS3 beta - same problem in converting to the web - too red!

  • All my prints using: Lightroom 5, printer color management turned off, and non-generic ICC profile (e.g. Epson Premium Glossy) have magenta tint or cast

    I'm using PC with: Windows 8.1, 64bit, Lightroom 5.4, Epson R3000, 6.75 (latest) driver, color management turned off in printer settings, Lightroom configured to manage color.  If I use a generic ICC profile such as Epson sRGB, the prints look OK.  But when I use any ICC profile dedicated to my paper and printer combination, such as Epson Premium Glossy, or one created using ColorMunki print profile, the prints all have a medium to heavy magenta tint or cast.  The effect can be seen before I even print in the Epson Print Preview.  Yet when I soft proof, I don't see this effect.  I suspect the problem lies somewhere in the CMM process, but I can't pin it down.  Any tips or suggestions are appreciated.

    Thank you kindly for your insightful response.  As it turns out, the answer is half correct.  I've found others who'll say the same thing, that double color management will lead to a very magenta result.  I believe this was certainly the case when I first started playing with the settings,  Where I went wrong, is that after I corrected my settings by turning off printer manages color and letting Lightroom do the color management, is that the Epson Print Preview was still showing magenta with certain profiles.  Not wanting to waste more money on paper and ink, I used the preview to gauge whether I was going to get a normal print or not.  Then one day I ignored the print preview's magenta cast as a 'warning' and I went ahead printed the photo anyways.  Because I used a profile that I created with ColorMunki Photo, the picture came out perfect (i.e. a very good match to what I was seeing in Lightoom on my monitor).  The lesson learned is that for judging the final color correctness, the Epson Print Preview can be way off target and your best bet is to ignore it.

  • - Lightroom Color Management Hints & Tips -

    Summary
    If you have a profiled monitor and you experience that Lightroom 2.1 renders the image
    very different from the way Photoshop renders it, or that the Library and Slideshow modules render the image
    very different from the way it is rendered by the Develop module, chances are that this can be solved by re-profiling your monitor and saving the new profile as a matrix-based profile rather than a LUT-based profile.
    The full article
    Read the full article at: http://photo.bragit.com/LightroomColorManagement.shtml, which describes the background, the problem, the solution and the results. There are also some hints on the use of test patterns, choice of gamma, color temperature and luminance.
    I am sure many people may have opinions on these issues, so please run any discussions about the article in this forum.

    To Richard Waters:
    For normal mid-tone images (excluding shadows) viewed at 1:1, there should be no (significant) differences between Development and Library modules (and Photoshop). If you do see significant differences, there is something wrong with the calibration.
    As for Photoshop vs Lightroom: Photoshop is better for printing because it has a proofing systems. What one can do is to open it in Photoshop (with Lightroom adjustments), then do the proofing, and perhaps some extra adjustments to compensate for the paper, and then print the result either from Photoshop or from Lightroom. Printing from Lightroom has the advantage that it does the resampling and sharpening automatically.
    Choice of gamma when profiling is not very critical. 2.2 is reasonably okay (and the most common), although the sRGB gamma (if you have the choice) may be more optimal, especially for deep shadows. Color management works so that, in principle, if the bit depth from the graphics card to the monitor was infinite, it would compensate for whatever gamma you choose. Thus, in principle, you could choose any arbitrary gamma, and the image would look and print exactly the same. The only reasons to choice a "suitable" gamma are: (1) the bit depth is limited to 8 bits which makes it necessary to use a "reasonable" gamma so as to avoid banding and posterizations; (2) when viewing images from the internet that are not tagged with a profile, or using a lousy browser that does not understand CM, then the choice of gamma is critical since it directly affects the contrast of that image.

  • Color managed workflow for web and camera raw

    I recently calibrated my monitor and was wondering what is the preferred workflow for the web? I shoot with my camera in sRGB and my working space in Photoshop is sRGB aswell. The problem that has arised now is that the color managed colors in Photoshop are way different than the non-color managed in my web browser. Is this normal? And what I don't quite get is how a photo that has an embed sRGB profile looks the same in Firefox (that understand embed profiles) and Photoshop, but in Google Chrome (that does not recognize embed color profiles) shows the colors very differently, although the browser should understand the photo is in sRGB by default and show the same colors that are in Photoshop, right? So what happens here, because the colors are not the same? What information does Photoshop assign to the embed color profile that makes the colors so different?
    Anyway, I assume the problem here seems to be my newly calibrated monitor profile. The only way I can get the same colors to my photo in Photoshop and to a photo in web is to use soft proofing set to my Monitor RGB AND save without a color profile. Is this the way to go? But here comes another problem. I shoot in RAW and use camera raw to edit my photos. Camera Raw doesn't allow soft proofing, so I'm stuck with these color managed colors that are so different from non-color managed colors I get in my browser that any color correction in Camera Raw is simply useless. Unless everyone was using color managed browsers and I could start to use fully color managed workflow, but that's not the case I suppose. So, what's the solution here?

    First off, you need to be working in sRGB, or converting to sRGB when you save out files that are destined for the web. You can change the color space that Camera Raw (ACR) send your raw files to by clicking the blue text in the bottom center of the ACR window. This is probably that safest workflow for you until you get a handle on color management. If the color of your images is very important, you might consider embedding a color profile in them, which will help color managed browsers render your color properly.
    If your display's color gamut is different than sRGB (many are), you'll find matching colors for non-color-managed browsers to be impossible. But consider the average display and take heart. The best you can do is correct to a standard and hope for the best.
    Both the convert to sRGB and embed color profile options are in the save for web dialogue box.
    More about the ACR workflow options here:
    http://help.adobe.com/en_US/Photoshop/11.0/WS739D7239-24A7-452b-92F9-80481C544F25.html
    More about matching colors for the web:
    http://help.adobe.com/en_US/Photoshop/11.0/WSB3484C68-ECD2-4fa4-B7CC-447A5FE86680.html
    http://help.adobe.com/en_US/Photoshop/11.0/WSD3F5E059-4F51-4b44-8566-13B854D3DF5F.html
    http://help.adobe.com/en_US/Photoshop/11.0/WS0B3CD652-4675-44be-9E10-445EB83C60BA.html

  • LightRoom Color Management

    Apart from the unique color space and behavior on certain export operations, Lightroom seems rather closed mouthed about color management. (This is a bit unsettling for someone used to all of the control offered by Photoshop) For instance, 1) is there any way to reveal the embedded profile of legacy PS files which have been imported? (all I can presently find for profile is "embedded") 2) what profile (and what gamma) is sent to a printer when printer color management is selected? 3) Is ColorSync enabled? and 4)Finally, is there any source which might make all of this clear?
    Bob Hesse

    Raw files have no color space, they are essentially Grayscale data.
    Existing rendered images have their own embedded profiles and thus color space but IF you apply ANY corrections using LR, you're converting into its internal color space to apply the edits. At that time, you're basically now in ProPhoto RGB (with a linear tone curve) so you might as well export back to 16-bit ProPhoto RGB.
    IF you don't apply an edit, the embedded profile will be honored if you open it in Photoshop.
    You might want to read this:
    http://www.ppmag.com/reviews/200701_rodneycm.pdf

  • Color discrepancy between Lightroom and Camera Raw

    I'm new to LR and came across a color issue when viewing the photos in LR.
    When view the RAW in LR, I see a color discrepancy compare with ACR. The color in LR is more like the JPEG view in Windows Photo Viewer (an non color-managed application). I suspect it's a color space config but can't find any in LR as in PS.
    When I changed my monitor's ICC profile to "SRGB IEC61966-2.1", all the applications, LR, ACR, WPV, look the same then. It's said that profile just for troubleshooting and should change back to monitor's profile. Can someone help to explain what's happen and what should I do to get consistent color? Thanks a lot!

    It sounds like the monitor profile from the monitor manufacturer is not compatible with LR.  This is a common problem, and you have confirmed it by temporarily switching to sRGB.
    If the only profiles you have available are sRGB (which is consistent but may be wrong) and the monitor profile (which doesn’t work) then for more accurate color you’ll need to buy a hardware calibrator. 
    I use the i1DisplayPro.  Others might use a Spyder or a ColorMunki, although the i1DisplayPro has some more detailed options for creating profiles (Matrix vs LUT or ICCv2 vs ICCv4) that can be necessary to make LR happy, or at least my preference is to have a more powerful program in case I do need to tweak things.  I haven’t ever used a ColorMunki or Spyder so perhaps they work fine, too.  I think the color-measuring hardware with the i1 is better, though.  I guess you get what you pay for.

  • 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

  • Lightroom 3: cannot access color management / print dialog

    Whenever I go to print anything in Lightroom 3 (or CS5 for that matter), I cannot access the print / color management settings in the print dialog box. The words are there with black lines through them, with the warning that the bundle doesn't match the architecture - or something like this. I have installed the newest print driver software (Epson 2200, work horse). Help! I have not been able to solve the problem with Adobe either.

    After trying to figure this out for weeks, I did find a related post on Lightroom's Facebook page. It is the 64 bit issue. To solve, highlight the application icon, go to "Get Info" dialog box, and click on "open in 32 bit mode". Same applies for CS5.  Good Lord, what a hassle.

Maybe you are looking for

  • How do you load Compiz before Gnome Session?

    I'd like for Compiz to load entirely before the Gnome 3 Desktop panels slide in. Is there a way to control in what order things load in Xorg or something?

  • Gzip problem on download files

    I've downloaded the files for Oracle 9i Database from http://otn.oracle.com/software/products/oracle9i/htdocs/linuxsoft.html When I try to gunzip the files, I get an error message gunzip: Linux9i_Disk1.cpio.gz: not in gzip format The files I have are

  • Safari not quitting

    Safari always gets the beach ball when I try to close it. Need to Force Quit.  It may or may not have something to do with 1Paaword extension which has NEVER worked  with Safari 5.  Cannot delete Safari, since it is part of OSX. cant copy another Saf

  • Ineteractive form application deployment error

    Dear All, We are creating a Adobe document application using Developer Studio.we have already done config , we are SP15 now. We are just keeping a simple static text in this form to test it. When we deploy and run it gives us error: Failed to process

  • Cannot access GNOME Keyring from Systemd Unit Service

    Hi ! I am using isync to download my IMAP mail to a directory in maildir format. I use the following line in ~/.mbsyncrc to fetch the mail password: PassCmd "gnome-keyring-query get mail_pw" My ~/.mbsyncrc is configured correctly, because I am able t