Color Management, (Again!)

I know this has been discussed before, but I still haven't found anything that can help me solve the issue. It's starting to become a serious barrier to professional work, so any thoughts woudl be appreciated.
I have both the eye1Display2 and a Gretag-Macbeth color checker and regularly calibrate my monitor and camera profiles. I'm working with CS5.  The colors in Photoshop are consistently far off from every other applicaiton outside of it. Even Flickr. I assume this is because of the color management, but I've even turned that off, (which gives me a warning message now every time I bring in an image), and the issue still occurs. Worse, the colors displayed working with RAW images are now different to those in the main interface, and even then, they are NOT the same outside of Photoshop, whereas all the other packages are consistent.  My workaround right now is to save regularly and check in other packages but this is simply not good enough for adjusting curves, HSL, etc.  I do a lot of work with skintones, which are particularly color-critical.
So my quesions are - how can I turn Photoshop's color management completely off so it's not applying any lookup at all to the color in any module?
If I WANT it to apply the color profile from the i1Display and the X-Rite Color Checker Passport sofware, how can I know this is being done and carried through from the RAW processing to the rest of the package?
Many thanks
Albert Hastings

ahast42696 wrote:
I have both the eye1Display2 and a Gretag-Macbeth color checker and regularly calibrate my monitor and camera profiles. I'm working with CS5.  The colors in Photoshop are consistently far off from every other applicaiton outside of it.
If what you're saying here is that a fully color-managed application, like Photoshop, is delivering color that's different from non-color-managed applications, this is just what you should expect.
There is no such thing as system-wide color management.  It just doesn't work that way.  Individual applications do (or don't do, or even partially do) color-management.
This is key:
Color-managed applications perform transforms on the colors being displayed in pursuit of absolute color accuracy at the expense of consistency with non-color-managed applications.
Corrollary:
Some color-managed applications misinterpret some color profiles.  It happens.
Expanding on what Dag has said in post #1 above, no transform takes place if the document profile matches the display profile.
So... IF you're working with documents in the sRGB IEC61966-2.1 color space (aka just "sRGB" for the purpose of this discussion) and IF you want the display of these images to match as often as possible between color-managed applciations and non-color-managed applications, this is one possible direction you can take:
1.  Set your system to associate the system-provided sRGB profile with your monitor(s). This is done via OS configuration dialogs.
2.  Set your monitor(s) to as closely match the sRGB color space as possible.  Some monitors were manufactured to be close, and others have the ability to be set that way.  Still others can't be directly set that way, but the system response can be tweaked with the basic controls (brightness, contrast, saturation, etc., as well as the curves adjustments in the video card drivers).
When the above conditions are met, you will see the following results:
A.  sRGB image documents, which are the majority of those published online and are usually the default output from digital cameras, will appear consistently the same in color-managed (Photoshop) and non-color-managed applications.  Depending on your needs you can configure Photoshop to work in the sRGB color space for creating your own images (this is actually Photoshop's default).
B.  In Photoshop and other color-managed apps you will get good overall color-management of image documents in other color spaces, though you'll see just the out-of-gamut colors (i.e., those colors from a larger color space that just can't be displayed in the sRGB color space) as fully-saturated and thus somewhat inaccurate.  In practice, most colors in most images fall within the sRGB gamut.
C. You'll see accurate color management by the partially* color-managed Internet Explorer 9, within the constraints of item B above.
D.  Since the sRGB color profile that comes with every Windows system is well formed, and is the default, there is a near zero chance that a color-managed application will misinterpret it and produce screwy color.  Such misinterpretation DOES happen with other profiles, a surprising number of times, even sometimes with profiles generated by good quality color measurement and profiling devices.  Color profiles are not trivial, and some software simply can't use some profiles.
The real (non-trivial) trick in this strategy is actually getting your monitor to closely match the sRGB color space without using a monitor profile.  However, it IS possible to get it close, and for many people "close enough" + "consistent across more apps" is better than "perfectly accurate in Photoshop but mismatching other apps".  It can even be checked with a profiling device to help with the fine tuning.
-Noel
*IE9 interprets your document color profile and always transforms it into the sRGB color space, regardless of your monitor profile.  Thus the only way to make the colors come out right is to have the monitor actually BE sRGB.  So far, unfortunately, it appears IE10 in Windows 8 is following this same "half baked" strategy.

Similar Messages

  • Color managment again

    I am working with PE5, a new Canon Pro 9000, a PC, and LCD monitor.
    Problem is that the pictures, originally shot in raw,then edited in PE and saved as Tiff, look very different from the print preview, and from the final print. Since the print preview and final print are very close, I assume that PE is the culprit. The prints always turns out rather cool. When I use the printer controls, the color looks unreal. Any thoughts?

    Pat....
    I think you've added a layer of complication in trying to find where the problem is by printing B&W gradients because many inkjet printers have trouble producing good B&W without a colour cast. I don't know the Canon 9000 and it may or may not have this problem.
    The first thing you must do is Calibrate and Profile your monitor. Adobe Gamma may or may not calibrate it but wont profile it. Your best bet - funds allowing - is to purchase a Colourimeter which accurately measures the display and creates a profile.
    Secondly it helps immensely if your source image has a colour profile associated with it and you have Colour Management enabled in Elements. If your source has a profile then pick any setting but the one called No Colour Management.
    Thirdly when you go to print you must choose a Print Space profile that matches the paper/printer you are using and you must disable Colour Management in the Printer Driver.
    One thing to keep in mind about your display profile. It only effects what you see on the screen and not what you print. However if its wrong then it may lead you to make adjustments that are not required. Also one of the most common errors in printing is to have both Elements and the Printer Driver manage the colours - you must decide on one or the other but not both.
    Colin

  • Preview panel loses Color Management after Minimize Bridge CS5

    Whenever I minimize the Bridge CS5 application window to the Windows taskbar, upon restoring or maximizing the Bridge application window the image(s) currently showing in the Preview panel no longer appear color managed (they look exactly as they would appear from a non-color-managed app.)  In order to see them as color managed again, I have to either de/re-select their thumbnails or double click the Preview panel twice (once to minimize it, and once again to restore it.)  Otherwise resizing the Preview panel has no impact on the color.  The thumbnails in the Content panel are fine.  This did NOT occur in CS4 or earlier versions of Bridge - otherwise the same environment.
    I have a wide-gamut monitor, which causes many non-color-managed images to look super saturated, especially reds & greens, so it is probably much easier to notice this behavior in this environment than from a typical-gamut monitor.
    Windows 7, x64, ATI Radeon HD 4850 graphics card, Bridge v4.0.3.9
    Anyone else notice this annoyance?

    Thanks Curt,
    I doubt this is a video issue as no other versions of Bridge behave this way on this system.  I have the same preference settings in Bridge CS5 as for Bridge CS4 - which works fine.  Nor does Photoshop exhibit this behavior post-minimizing, & Photoshop behaves perfectly for all the OpenGL Drawing settings (which I have set to Advanced in PS.)  Bridge just seems to poorly manage the Preview panel color post-minimizing the application window, but otherwise everything displays fine during operation.  I'd be surprised if it was just me but if it is, it's an easy enough annoyance to work around.  I'd imagine that this isn't too observable on a normal-gamut monitor.
    I tried your suggestion of  "use software rendering", just in case, but it made no difference.  Appreciate the idea though...
    One more observation:
    While thumbnails are being generated for the first time on large images, they also have the non-color-managed appearance until they complete their generating, at which time they take the managed appearance - but I just consider that a processing-timing final step & it hasn't changed behavior from previous versions of Bridge.

  • Color management........again   SORRY!

    OK, I know this topic is like fingernails on a chalkboard, however I have not been able to understand or solve my issues after months of trying.... I have a very simple setup (and also very simple needs...):
    PE 5.0
    Epson RX-700 printer
    Colorvision Spyder2
    Nikon D70
    I can NOT get prints from any image that I modify in PE. In fact, the only time I can get a reasonably matched print is if I utilize the PhotoEnhance setting within my Epson configuration and no modification has been done within PE. All of my prints come out with an apparent 2-3 stop underexposure when I print a PE modified image. Modifications range from unsharp mask to a few layers, but nothing very fancy or involved.
    My question:
    1. There are many options for printer color space; sRGB, EPSON sRGB, NIKON sRGB, etc. Which would be optimal? My camera is set to sRGB, though I've tried Adobe RGB with the same results.
    I would rather have PE color manage, but when I set the printer to do no color management, I get the above results.
    Any suggestions on things to try, things I've overlooked, or anything in general?
    Any help is very much appreciated...
    Dave

    OK, I know this topic is like fingernails on a chalkboard, however I have not been able to understand or solve my issues after months of trying.... I have a very simple setup (and also very simple needs...):
    PE 5.0
    Epson RX-700 printer
    Colorvision Spyder2
    Nikon D70
    I can NOT get prints from any image that I modify in PE. In fact, the only time I can get a reasonably matched print is if I utilize the PhotoEnhance setting within my Epson configuration and no modification has been done within PE. All of my prints come out with an apparent 2-3 stop underexposure when I print a PE modified image. Modifications range from unsharp mask to a few layers, but nothing very fancy or involved.
    My question:
    1. There are many options for printer color space; sRGB, EPSON sRGB, NIKON sRGB, etc. Which would be optimal? My camera is set to sRGB, though I've tried Adobe RGB with the same results.
    I would rather have PE color manage, but when I set the printer to do no color management, I get the above results.
    Any suggestions on things to try, things I've overlooked, or anything in general?
    Any help is very much appreciated...
    Dave

  • Vista color management & CS3

    Two weeks ago I wrongly faulted my new Dell 2707WFP monitor for its high contrast and saturation after many failed profiling attempts using the Spyder2Pro with the updated Vista software. I'm still at a loss as to why images are dark and overly saturated in Photoshop, Bridge and Lightroom. They were all fine on an older Dell system running XP home and CS2. I've gone so far as to purposely inflict various gamma curve settings in Spyder to bump up the low end luminance but resulting profiles still show images clipped in the low end and overall saturated even as the desktop and the PS interface turn a sickly pale.
    I'm new to CS3 and Lightroom and so I'm not sure if the following is normal. When I view a NEW batch of images that were not previously viewed in Bridge, they are normal looking, however when I click on a thumbnail, it then reverts to the same garish contrasty version that I see full size in the above adobe software when opened. The same thing happens in the WINDOWS PHOTO GALLERY viewer but NOT in WINDOWS EXPLORER. In Explorer the thumbs are as they should be...normal, and if I open them in Microsoft OFFICE PICTURE MANAGER or in Quicktime PICTUREVIEWER, they open as normal images.
    All this sounds like a profile issue of some kind, but as far as I know, everything appears to be set correctly in both PS and the profiling software. However, Im not sure about the system settings regarding profiles. In the Windows COLOR folder all the profiles are where they should be and I can select which one to load using the Spyder Profile Chooser. And again, I do restart PS when I change a profile. Could this be some kind of Vista bug??
    Other notes:
    If I do a screen shot and paste it back into PS, it turns DARKER than the original file.
    When I do additional calibrations I restart PS to load the latest profile.
    All files tagged sRGB and in sRGB workspace. PS shows this correct space and likewise the correct monitor profile in COLOR SETTINGS
    ATI CATALYST CONTROL CENTER fails to run on bootup so windows shuts it down. No fix that I can find for this.
    Running Vista Home Premium on a Dell Inspiron 530 E6550, 4GB memory, Radeon HD2600XT
    Thanks again for your help!

    Found this on the DATACOLOR site in their SUPPORT CENTER:
    Incorrect Color outside Photoshop on Wide Gamut Display
    Solution >>I just purchased a Dell 2407 HC display, considered wide gamut and the spyder 3 elite. I've used the spyder 3 to calibrate the monitor. In photoshop whenever I "Save for Web" or "Save as" in the sRGB color space, I wind up with over saturated oranges and reds. I'm needing to save in the sRGB for web work. My working color space is set to sRGB which looks fine when editting in photoshop, but as soon as I save it out of photoshop the reds and oranges are over saturated. I purchased the spyder 3 because of the wide gamut support, is there something I'm missing in calibration?
    The display profile is not at fault here. The ICC profile for the display tells any application that uses color management what the color values for the display are. Thus Photoshop, which is using the profile, corrects for the colors on screen, giving correct results. A non-color managed application (such as Internet Explorer for Windows) would not use the profile and thus the colors would be oversaturated on your wide gamut screen. This is not the fault of the profile (that would make the color look wrong in Photoshop, where the profile is being used), but the lack of a profile (which makes the color look wrong in non-color managed applications).
    This is the problem with using a Wide Gamut display for viewing in non-color managed applications. A typical gamut display is not color correct in such applications, but is at least approximately correct; a wide gamut display is noticably oversatured in some colors. On the Mac many applications, including web browsers and OS utilities, are color managed, so it is less of an issue than on Windows.
    Article Details
    Article ID: 723
    Created On: 10 Jan 2008 07:31 PM
    So if the color is off outside PS, then its not the fault of the profile. My problem is the image is off INSIDE PS, and by the same reasoning, then the profile is at fault. If the profile is to blame, is this a Spyder issue or Vista issue? So far noone seems to know anything including Adobe tech support and Dell. Been waiting 2 wks to hear from the Spyder people.
    Would really appreciate some input on this. thanks.

  • Confused about Color Management in CS5 (Photos appearing differently in all other programs)

    I recently noticed this and it's been driving me crazy; when I view photos in Photoshop CS5 they appear significantly lighter/more washed out than when viewed in other programs like Zoombrowser, Digital Photo Professional or just in a regular Windows folder using Filmstrip mode (Windows XP).  When opening the same photo in both CS5 and Zoombrowser and switching back and forth between the two windows the difference is very apparent...for example, one of the photos I compared was of a person in a black shirt -- in CS5 (lighter/washed out) the folds in the shirt were very obvious, but in Zoombrowser (darker, more contrast/saturation) the folds were nearly invisible and it looked like just solid black.  Now, after messing around with the settings in both Photoshop and in Zoombrowser I've found a few ways to get the photos to look the same in the two programs; one way gives them both the lighter/more washed out appearance and another way gives them both the darker appearance with more contrast and saturation.  My problem is that I'm not sure which view is accurate.
    I use a NEC MultiSync LCD1990SXi monitor with SpectraView II calibration software and calibrate it every 2 weeks using these calibration settings (screenshot): http://img52.imageshack.us/img52/8826/settingsx.jpg
    In the SpectraView II Software under Preferences there's an option that says "Set as Windows Color Management System Monitor Profile - Automatically selects and associates the generated ICC monitor profile with the Color Management System (CMS)."  This option is checked.  Also, when I open the Windows' Color Management window there's only one option displayed, which is "LCD1990SXi #######" (the ####### represents my monitor's serial number).
    I assume the above settings are all correct so far, but I'm not sure about the rest.
    Here are my current default Color Settings in CS5 (screenshot): http://img97.imageshack.us/img97/666/photoshopcolorsettings.jpg
    Changing these settings around doesn't seem to make the photo appear much different.  However, when I go to Edit -> Assign Profile, then click off of "Working RGB: sRGB IEC61966-2.1" and instead click Profile and select "LCD1990SXi ####### 2011-06-21 18-30 D65 2.20" from the drop-down menu, the picture becomes darker with more contrast and saturation and matches the picture in Zoombrowser.  Also, if I select "Adobe RGB (1998)" from the drop-down menu it's very similar in terms of increased darkness and contrast but the saturation is higher than with the LCD1990SXi setting.  Another way I've found to make the image equally dark with increased contrast and saturation is to go to View -> Proof Setup -> Custom and then click the drop-down menu next to "Device to Simulate" and select "LCD1990SXi ####### 2011-06-21 18-30 D65 2.20" again.
    Alternatively, to make both images equally light and washed out I can go to Zoombrowser -> Tools -> Preferences and check the box next to "Color Management: Adjust colors of images using monitor profile."  This makes the image in Zoombrowser appear just like it does in CS5 by default.
    Like I said, I'm confused as to which setting is the accurate one (I'm new to Color Management in general so I apologize for my ignorance on the subject).
    It would seem that assigning the LCD1990SXi profile in CS5 would be the correct choice in order to match the monitor calibration given the name of the profile but the "Adjust colors of images using monitor profile" option in Zoombrowser sounds like it would do the same thing as well.  Also, I've read that Photoshop is a color managed software whereas Zoombrowser and Windows Picture and Fax Viewer are not which makes me think that maybe the lighter/washed out version seen in Photoshop is correct.  So which version (light or dark) is the accurate one that I should use to view and edit my photos?  Thanks in advance for any help or info.

    Sorry for the late reply;
    But before we go there or make any assumptions, it's important for
    you to determine whether you're seeing consistent color in your
    color-managed applications and only inconsistent color in those that are
    not color-managed.  For that you'll need to do a little research to see
    if the applications in which you're seeing darker colors have
    color-management capability (and whether it is enabled).
    I opened the same picture in 7 different applications and found that the 6 of the 7 displayed the photo equally dark with equally high contrast when compared to the 7th application (CS5).  The other 6 applications were Zoombrowser EX, Digital Photo Professional, Windows Picture and Fax Viewer, Quicktime PictureViewer, Microsoft Office Picture Manager and Firefox.
    However, at least two of these programs offer color management preferences and, when used, display the photo (from what I can tell) exactly the same as Photoshop CS5's default settings.  The two programs are two Canon programs: Zoombrowser EX and Digital Photo Professional.  Here's the setting that needs to be selected in Zoombrowser in order to match up with CS5 (circled in red):
    And here's the setting in Digital Photo Professional that needs to be selected in order to match up with CS5 (again, circled in red):
    *Note: When the option above "Monitor Profile" is selected ("Use the OS settings") the image is displayed exactly the same as when the monitor profile is selected.  It's only when sRGB is selected that it goes back to the default darker, more contrasty version.
    So with the red-circled options selected, all three programs (CS5, ZB, DPP) display the images the same way; lighter and more washed out.  What I'm still having trouble understanding is if that ligher, more washed out display is the accurate one or not...I've read several tutorials for all three programs which only make things more confusing.  One of the tutorials says to always use sRGB if you want accurate results and *never* to use Monitor Profile and another says that, if you're using a calibrated monitor, you should always select Monitor Profile under the color management settings...so I'm still lost, unfortunately.
    What I also don't understand is why, when the monitor profile is selected in CS5, the image is displayed in the dark and contrasty way that the other programs display it as by default but when the monitor profile is selected in Digitial Photo Professional it displays it in the lighter, more washed out way that CS5 displays it using CS5's default settings (sRGB).  Why would selecting the monitor profile in DPP display the photo the same way as when sRGB is selected in Photoshop?  And vice versa...why would selecting the monitor profile in Photoshop display the photo the same way as when sRGB is selected in DPP?
    I feel like I'm missing something obvious here...which I probably am.  Again, I'm very new to this stuff so pardon my ignorance on the topic.
    By the way, I find that the way that the non-color managed programs (Windows Picture and Fax Viewer et al.) display the photos is more aesthetically pleasing to the eye than the duller, more washed out display that CS5 gives the photos, but ultimately what I want to see in these programs (especially PS5 where I'll be doing the editing) is the accurate representation of the actual photo itself...i.e. what it's supposed to look like and not a darker (or lighter) variant of it.
    So just to reiterate my questions:
    Why does selecting Monitor Profile under the color management settings in DPP give the same display results as the default sRGB profile in CS5 and vice versa?  (CS5 with monitor profile selected having the same display results as DPP with the sRGB profile selected)
    When using CS5 with it's default color management settings (sRGB), using DPP with the Monitor Profile selected, and using Zoombrowser EX with "Adjust color of images using monitor profile" selected this results in all three programs displaying the same lighter, washed-out images...is this lighter, more washed-out display of the images shown in these three programs the accurate one?
    I noticed when opening an image in Firefox it had the same darker, contrasty look as the other non-color managed applications had.  Assuming that the CS5 default settings are accurate, does this mean that if I edit a photo in CS5, save it, and upload it to the internet that other people who are viewing that image online will see it differently than how it's supposed to look (i.e. in a non-color-managed way?)  If so, this would seem to indicate that they'd see a less-than-flattering version of the photo since if their browser naturally displays images as darker and more contrasty and I added more darkness and contrast to the image in CS5, they'd be seeing a version of the photo that's far too dark and probably wouldn't look very good.  Is this something I have to worry about as well?
    I apologize for the lengthy post; I do tend to be a bit OCD about these things...it's a habit I picked up once I realized I'd been improperly editing photos on an  incorrectly calibrated monitor for years and all that time and effort had been spent editing photos in a certain way that looked good on my incorrectly calibrated monitor but looked like crap on everyone else's screen, so the length and detail of this post comes from a desire to not repeat similar mistakes by editing photos the wrong way all over again.  Again, thanks in advance for all the help, it's greatly appreciated!

  • Suspected Flaw in Firefox 35 Color Management Behavior

    I hope I can keep this concise, but bear with me if my confusion causes me to include some extraneous info. The info below is what I think is required for someone else to fully understand the issue.
    BACKGROUND:
    - NECPA271W wide gamut monitor in dual monitor setup with a standard gamut Samsung 245BW
    - Windows 8.1 Pro 64-bit
    - Nvidia Quadro K4000
    - Latest versions of FireFox (v35 32-bit), IE11 (11.0.9600.17498 updated to 11.0.15 32-bit) & Avant (Ultimate 2015 build 7, in use for testing because it incorporates the rendering engines of 3 major browsers, IE v 11.0.9600.17496, FireFox v 34.05.5464, & Chrome v39.0.2172.95)
    - i1Display Pro (not the NEC SVSensor version), SpectraView II, NEC Multiprofiler & i1 Profiler
    - Both monitors are calibrated and profiled. The NEC is calibrated using SVII, but since that software only supports NEC monitors, the 245BW has to be done using i1Profiler software that comes with the i1Display Pro. SVII is only capable of generating v2 ICC profiles, i1 Profiler is capable of v2 & v4, and recommends v4. Nevertheless, I think this entire bullet point is irrelevant to the effect I'm observing.
    - I've lately started selling some of my photography on a fine art website.  As a result I started digging deeper into how those images are viewed by others & subsequently printed. Images optimized in sRGB for the best possible display results across a widely varied viewer base are not going to give the same results as images that are soft-proofed and optimized for specific media/printer/ink combinations. This is especially true of my images which tend to lean in the direction of being more heavily saturated & wider gamut
    - I've been exhaustively over the info here COLOR MANAGEMENT PHOTOSHOP CC CS6 Basic ColorManagement Theory ICC Profiles Color Spaces Calibrated Monitor Professional… & here http://cameratico.com/tools/web-browser-color-management-test/  among many others.
    I had reached a point where I thought I understood things pretty well, but now I'm not so sure again Here's the problem:
    I followed the guidance and info on how to set FireFox for FULL color management  (value 1 with associated monitor profile) that allows the handling of non-tagged images and web page elements, http://cameratico.com/guides/firefox-color-management/. Upon restarting Firefox with the updated configuration, I return to the test at http://cameratico.com/tools/web-browser-color-management-test/  The last two tests there are designed to show a) how much wider your display gamut is than sRGB, and b) how the browser handles untagged images and elements.
    The behavior I observe is different from the behavior I expect! Specifically, setting FIrefox to color management value 1 and telling it my monitor profile causes Firefox to display the sRGB tagged images as if they were not tagged. With the default value 2/no monitor profile, I can see a difference between the display of sRGB tagged images and either the ProPhoto RGB tagged image or the untagged sRBG & untagged CSS elements. I would expect that the change to value 1 with monitor profile should have no impact on the display of tagged images and elements, and yet that switch ONLY causes a  change in the display behavior of the tagged images it shouldn't have affected, and I can no longer see a difference between the various images because everything is fully saturated
    A marked up screen capture showing the comparative behaviors between the various applications and browsers would probably be worth more than the proverbial 1000 words, I'm new here & haven't figured that part out yet, but will post this as is while I work on that.
    Can anybody replicate the behavior I observe? Is anybody spotting an error in my thinking?
    TIA
    Randy
    *EDIT - I have annotated a screen shot comparing the results across 4 browsers. The screenshot has an embedded Adobe RGB profile which best represents the effects & changes that I was/am seeing but may not be preserved if posted here. It may be best to download and view in CS6 so as to not introduce any additional confusion arising from which browser YOU may be using :-) If needed the full res 2560x1440 version is available, but scaling to meet the forum limits of 900x900 makes the text unreadable. Can anyone suggest a means of supplying the full res file with the embedded profile retained?

    twenty_one wrote:
    Firefox will use the profile for the main display. It does not support a dual monitor setup. If you move FF to the secondary display, it will still use the primary display's profile.
    There is a Firefox Add-On called Profile Switcher that allows using multiple monitor profiles. You will need to setup a Firefox user profile for each monitor:
    https://developer.mozilla.org/en-US/docs/Mozilla/Multiple_Firefox_Profiles
    After installing Profile Switcher Add-On you will find a new entry in the FF File menu 'Open Profile Manager,' which can be used to create and manage the new user profiles (see screenshots below).
    You can then setup a Firefox Sync account to keep the user profiles synchronized or do this manually using Copy & Paste. I was concerned that Firefox Sync would over-write the configuration data for the monitor profile, but it doesn't. I leave 'gfx.color_management.display_profile' blank on the user profile for the primary NEC 272W monitor, and add the path for the monitor profile on the user profile for my standard gamut secondary display. Here's what I see when launching FF:
    After installing the Profile Switcher Add-On you'll see two new entries in the FF File menu that allow you to manage and launch other FF user profiles as separate browser instances.
    It works fine on my Windows 7 system and should also work on Mac OS X systems and Windows 8.x.

  • CS6: Can't switch off color management in the printerdriver when photoshop manages colors

    So this is weird: I'm using CS6 Extended and Lightroom 5 on a Windows 7 Pro machine, printing to an old Canon Pixma Ip5200R. When i print from Lightroom, i am using a special printer profile for the pixma and my photopaper, so color management is switched off in the printer driver. The photos print fine.
    Now when i print the same photo from CS6, it has a magenta color cast, so clearly something is wrong with the color management. Even though i am using the same printer, the same paper, the same printer profile and  - of course! - had set photoshop to manage the colors, and switched color managent off in the printer driver. The magenta cast could be an indication that the photo is double colormanaged.
    It took my quite a while to find out what happens, and this is really weird: When i re-checked the printer driver settings, i noticed that the color management settings did not stick. The canon printer driver offers the options "driver matching" "windows ICM" "none", e.g. having color management done by the printer driver or windows, or switch color management  off. So when i go to the PS print settings and set it to "photoshop manages colors", add the correct printer profile, i have to check the settings in the printer driver and make sure that color management is set to "none". I set it to "none" and click OK. Now everything should be configured correctly. But it's not - because when i re-check the print driver settings, i see color management is set to "diver matching". I can go to the print driver settings again and agian, but whenever i check, color management is set to "driver matching". This setting simply does not stick. No wonder i get a mangenta cast on my prints, the colors are doublemanaged by photoshop AND my printer driver.
    Now, this is getting weirder: Only the color management settings don't stick. I can change other settings like print quality and the stick.
    But - how do i get rid of this? The culprit seems to be photoshop, not the printer driver. If i print from lightroom, i can change the color management settings in the (very same) printer driver and they stick. When i set the photoshop print dialogue to "printer manages colors" i can change the color management settings in the (very same) printer driver - and they stick! So this looks as if photoshop stops me intentionally from using the correct printer driver settings, that is from switching off the printer drivers color management if it is set to manage colors.
    I have already resetted my personal photoshop preferences, but this changed nothing. What am i missing? What is going wrong? Your help is very appreciated.
    Tobias

    Hi all, Just to let you know that I finally solved my problem myself.
    Essentially what had occurred was that I had updated my Epson driver for my printer , but it hadn't installed, despite informing me that it had! To cut a long story short when I checked in System preferences the older driver for Leopard O/S was still the current driver. I proceeded to ask Epson support for assistance, bu despite their efforts I could not immediately resolve the problem. They were directing me to my Utilities program to remove all traces of my current driver from Printer Utility which did not exist. When I queried this they stated it was not always visible and I should proceed to the next step then install the new driver. Problem was they required me to access this invisible utility in order to complete this process, and yes before you ask I had informed them I was using an Intel Mac with Snow Leopard 10.6.2 O/S. Finally I ignored their advice and took the following steps:
    1. I opened System Preferences and double clicked the Printer & Fax icon.
    2. I highlighted my Epson R2400 Pinter and removed it by clicking the minus sign at the bottom of the Printers window.
    3. Next I did a search and deleted any old drivers for my R2400 that were on my system with the exception of the new Driver.
    4. I restarted my Mac Pro.
    5. I reinstalled my new printer driver which I had previously downloaded from Epson Support.
    6. I restarted my Mac Pro and found that the new driver had installed correctly and full functionality had been returned to the Print Features Dialogue box i.e I could now turn of color management and access advanced features to set the quality of printing using the full spec of the R2400.
    Hope this post will be helpful to others if they have a similar problem
    Regards Denis
    Message was edited by: Denisimo
    Message was edited by: Denisimo

  • Color Management in Bridge CS6

    Hello,
    I'm having a strange color management issue in Bridge (64 bit). Essentially, Bridge is not displaying images in either the thumbnails or preview pane using the correct color profile.
    Background: I'm on Windows using a dual monitor setup (both independantly calibrated) but I have the issue even when I use only one monitor. Photoshop has no issues with color settings. I've tried resetting all settings (hitting Ctrl as Bridge starts). I've tried purging my cache and having Bridge generate monitor-size previews.
    The weirdest part is when I start Bridge, for a split second images appear to be in the correct profile, and then Bridge adjusts everything to the wrong color profile.
    Any thoughts?
    Thanks!

    Omke Oudeman wrote:
    about A:
    I don't get that, I have a custom made monitor profile based on D65 and with or without this profile the only difference one would spot would be in the total picture, this screenshot shows what I see and that is not as much difference between the Bridge thumb and preview (and in the metadata placard you can see they are 16 bit ProPhoto with on top of it the floating PS panel with the same image. It is one picture of one screen, without my monitor profile (and without knowing what happens during the adding process to the Adobe site) or with, the difference between both applications would not change, only the total picture. (or I really don't understand anything anymore about color management )
    The first threshold question is whether you're using a wide gamut monitor. I'm going to assume the answer is yes. The reason it's essential to embed your monitor profile in your screenshot is if you do not have a wide gamut monitor, someone looking at your image who does will be able to tell since the gamut will be smaller than it should be. If you are not using a wide gamut monitor, that would explain why you cannot see the difference. Additionally, whether you have a wide-gamut monitor or not, if you do not embed a profile, the untagged image will appear way oversaturated when brought into Photoshop (this is happening for me) unless I can guess the approximate color space of your monitor.
    Admittedly, if you are using a wide-gamut monitor, then although the image will be way oversatured without a profile (until I assign one), both the Photoshop portion and Bridge portion should be way oversatured by the same amount. However it's not particularly helpful to use guesswork and approximation when trying to narrow down a problem like this. You say "this screenshot shows what I see," but you have to keep in mind you are looking at it on your monitor. Even though your screenshot will obviously look right to you on your monitor, someone looking at it on a smaller gamut monitor won't see what you're talking about.
    about B:
    There you have a point but this was a current project at hand and at this moment there is a bit over saturation in the wood. In real life I also almost never have to deal with the bright colors of your example. I don't want to go again messing my workspaces to create a screenshot for the files you provided but I can assure you I have less to none difference between both files in both Bridge and PS, like I never have seen your problem on my current computer (Mac Pro, 2 x 2,4 6 core intel Xeon mid 2012 and a lot of RAM and SSD etc including ATI Radeon HD 5770 1024 MB VRAM running OSX 10.8.3) as well as my former MacPro with same graphic card - and two others - that I used since 2008 during OSX 10.5 to 10.7 with all used versions of CS.
    Yea, I understand why you don't want to mess with your workflow. I wouldn't either if I were in the middle of a project. But (assuming you have a wide-gamut monitor) if you finish a project and do get the chance, I encourage you to try the ProPhotoRGB color patch in Photoshop versus Bridge. When you really stray from sRGB, you, like me and Yammer, should see a major difference. I suppose there's the possibility that the Mac version of Bridge works differently, but that doesn't seem likely. It's possible you've never noticed the difference before because (again, assuming you have a wide-gamut monitor) you've never been looking for it, or you don't shoot many subjects with colors vastly outside sRGB - things like flowers, dyes, clothing, bright lights, etc.
    And as for the quote, I also never make my choices based on colors for DNG in Bridge, in fact, I always shoot with manual WB set to 5500 K, whether in daylight or artificial light, I just don't bother because I want my colors to be adjusted in ACR and refined the way I want them in PS. The plus side of manual WB is that all colors are off in the same way and can be adjusted in the correct direction in one go for a series
    That's an interesting idea and really illustrates the beauty of shooting RAW - tons on flexibility. And in fact, whether you use manual white balance, or don't, with RAW everything can be corrected or adjusted from a certain baseline by the same amount after the fact anyway.

  • Photoshop CS3 color management "Save for Web" problem

    This problem is getting the best of me.......
    After spending 3 full days researching this problem, I am no closer to finding an answer than when I started. I still cannot produce a usable image through the "Save for Web" feature of Photoshop CS3. I have read web page after web page of "Tips, Tricks and Recommendations" from dozens of experts, some from this forum, and still I have no solution... I am exhausted and frustrated to say the least. Here's the simple facts that I know at this point.
    I have a web design project that was started in PS CS1. All artwork was created in photoshop and exported to JPG format by using "Save for Web". Every image displays correctly in these browsers (Safari, Camino, FireFox and even Internet Explorer on a PC).
    I have recently upgraded to PS CS3 and now cannot get any newly JPG'd image to display correctly. My original settings in CS1 were of no concern to me at the time, because it always just worked, and so I do not know what they were. I have opened a few of my previous images in CS3 and found that sRGB-2.1 displays them more or less accurately. I am using sRGB 2.1 working space. Upon openning these previous image files, I get the "Missing Profile" message and of course I select "Leave as is. Do Not color manage". CS3 assumes sRGB-2.1 working space, opens the file, and all is well.
    The problem is when I go to "Save for Web", the saturation goes up, and the colors change. The opposite of what most people are reporting. Here's another important point... new artwork created in CS3 does exactly the same thing, so it's not because of the older CS1 files.
    I have tried every combination of "uncompensated color", "Convert to sRGB", "ICC Profile", etc. while saving. I have Converted to sRGB before saving, and my monitor is calibrated correctly.
    I have tried setting the "Save for Web" page on 2-up and the "original" on the left is already color shifted before I even hit the "Save" button. Of course, the "Optimized" image on the right looks perfect because I am cheating by selecting the "Use Document Color Profile" item. Why do they even have this feature if doesn't work, or misleads you?
    Does anyone have any ideas what could be happening here? Why is this all so screwed up?
    CS1 worked fine out of the box.
    Final note: I do have an image file I could send along that demonstrates how it is possible to display an image exactly the same in all 4 of the browsers I mentioned with no color differences. It is untagged RGB and somehow it just works.
    I am very frustrated with all of this and any suggestions will be appreciated
    Thanks,
    Pete

    >> First of all... I'm using an Adobe RGB image master... I open it and get the Profile Mismatch Screen... I choose Use Enbedded profile... all looks well. Next I go to Proof Setup > Monitor RGB... again all looks well, no change that I can tell.
    This has further confused the issue on several points, not the least of which version PS you are doing this with?
    >> AdobeRGB> Convert to Profile > Working Space sRGB-2.1... all still looks well... but now, when I go to Proof Setup > Monitor RGB... I see the insane oversaturated look that is driving me nuts.
    That is your strongest clue...it sounds like you have a bad system or bad monitor profile. To rule out the monitor profile: Set sRGB as your monitor profile in System Prefs> Displays> Color.
    >> Adobe RGB image master... I open it and get the Profile Mismatch Screen... I choose Use Enbedded profile... all looks well. Next I go to Proof Setup > Monitor RGB... again all looks well
    That doesn't make sense, stripping an embedded AdobeRGB profile should desaturate the color in Softproof MonitorRGB, especially the reds -- you have something wacky going on there.
    At this point I think you need to review the links and get a grip about how color management and profiles work...
    BTW, forget about setting ColorSync in PS COlor Settings, use Adobe ACE.
    MO,
    I think SFW is fixed under CS3 :) By default it Converts to sRGB and strips the profile.

  • Can't access Color Management options for HP 6700 under Mac OS 10.8.5 (Mountain Lion)

    Hello.
    I've got the HP Officejet 6700 Premium e-All-in-One and I can't find any way to access Color Management options.
    The printer is attached (Wi-Fi) to my iMac running Mac OS 10.8.5 (Mountain Lion).
    I want to correct a magenta cast to photographs that I've printed.  I've had the magenta-cast problem under Lightroom and using Preview to print the photographs, so now I want to work with color profiles in Photoshop Elements.
    Photoshop Elements recommends that I "disable color management in the printer preferences dialog".
    However, I'm not able to find color management preferences for the 6700 in any of the settings under Mountain Lion:
    Not under (Apple) > System Preferences > Print & Scan.
    Not under (HP Utility) > Open Embedded Web Server.
    Not under (HP Utility) > Printer Settings.
    Not under Preview's print dialog.
    Nor can I find any clear direction in the online help (at HP or elsewhere) that I've read so far.
    Any suggestions would be most appreciated.
    Thank you!
    Michael
    This question was solved.
    View Solution.

    Please note that in the Print dialog I get "Color Matching" not "Color Management."
    Still, I am (at this point) able to control color from Photoshop Elements, so that's good enough to proceed.
    Thanks again.

  • Photoshop CS5 Color Management

    My question has a complicated back story, but here is where I'm at.  I'm still a newby when it comes to color management.  I'm running Photoshop CS5, Lightroom 3.3, Windows 7 64-bit, Dell Studio XPS desktop, and a new Dell U2311H monitor.  I really struggled several months ago trying to learn color management and Photoshop printing work flow, and may have made an error during that process that created my situation.  When I attach a new monitor (or different monitor), all of my images in Bridge, Photoshop, and Lightroom display with a strong pink/magenta cast.  Images displayed by applications that are not color managed look normal.  Once I calibrate the new/different monitor (with Spyder2Express), and reboot, the color managed images display normally.  If I go to the Control Panel, and assign another profile (such as sRGB IEC61966-2.1) as the default profile for the monitor, all images continue to display normally.  If I go to the Control Panel, and disassociate ALL profiles from the monitor, the images displayed by Bridge, Photoshop and Lightroom again display with a strong pink/magenta cast.
    If no profile has been assigned to the monitor on which Photoshop is going to display an image, what does Photoshop do that might result in a pink/magenta image?  Might I have a corrupted profile somewhere, or might I have miscoded something in Color Management that is causing the condition?  If I need to provide some additiional info, please let me know what info is needed.
    Thanks for any assistance..

    Andrew, thanks so much for taking the time to respond.  I believe I found
    and corrected my problem last night.  When I attempted to do my own printing
    from Photoshop last summer, I experimented a lot as I tried to figure out
    the work flow.  I discovered last night that I had apparently introduced an
    error into the Monitor Color settings under Color Settings.  The RBG Work
    Space under Monitor Color was set to "Monitor RBG - xxxxx", where xxxxx was
    the profile for the Epson paper I was experimenting with last summer!  I
    suspect that Protoshop was using that profile when I didn't provide any
    other profile for the display.  I changed that setting to "Monitor RBG -
    sRBG", and my problem (the strong magenta casts when displaying images
    without profiling the monitor) is gone.
    I have been using the Spyder2Express for the past couple of years, and
    usually work with a monitor I have previously calibrated with the Spyder.
    This magenta problem only showed up when I switched to a new monitor, and
    displayed images before running the first calibration.  I wanted to resolve
    the magenta problem, however, to determine whether it might be connected to
    two other problems I have involving color management.  The first was my
    attempt last summer to print on a "hand me down" Epson 2200 printer.  I
    finally got the work flow figured out, but was never able to eliminate a
    slight magenta cast from some of my prints.  I tried printing from three
    computers, using two operating systems, downloaded the 2200 driver and paper
    profiles numerous times, printed on two different Epson papers, printed test
    prints of the same image on two other printers (without the slight magenta
    cast).  I've given up on the 2200 for now!
    My latest concern, which really prompted my renewed interest in color
    management, is my latest monitor calibration.  I just purchased a Dell
    U2311H, and calibrated it with the Spyder2Express.  At the end of the
    calibration/profiling process, the Spyder provides a before/after view.
    With other monitors, I've always felt that the calibration/profiling process
    improved the test image.  With the Dell U2311H, however, it appears to my
    eyes that the "before" image looks super, while the "after" image appears to
    have a yellowish, or yellowish-green, cast, and the after image is also
    "lighter", giving the image a bit of a "washed out" look.
    Any suggestions on what I might try next?
    Thanks again for your help, Andrew.  By the way, I read the two articles you
    sent links for.  I especially enjoyed the article on matching display and
    prints.  I'll keep rereading that one until it all soaks in!
    Mike
    www.mikelandwehr.smugmug.com

  • Color Management Discrepencies Between Bridge, ACR & Photoshop

    Hi - I've had a color management issue I can't wrap my head around which is similar to this infamous thread: http://forums.adobe.com/message/3235601#3235601
    I'm hoping with a little more information provided I can get this figured out. The basic problem is that Bridge displays images markedly differently than either ACR or Photoshop. The most common issue is as follows:
    With the external monitor as the primary display (and the laptop monitor as a secondary), I start Bridge. Photos will seem to be in the correct gamut for a moment, but it almost immediately desaturates them as if switching gamuts. Opening the image in ACR or Photoshop shows the correct color. See the below:
    (Note: on my wide-gamut monitor, there's no clipping on the ACR version - that's how it should look)
    There are various permuations to this problem depending on which monitor I have on when I start Bridge, but the above is my general workflow.
    Some background:
    Lenovo ThinkPad T430s w/ integrated Intel HD4000 graphics
    ASUS ProArt Series PA246Q (Wide Gamut)
    Photoshop CS6 (using 16-bit ProPhotoRGB as the standard workspace)
    Datacolor Spyder4 calibrating both monitors
    My settings:
    I know there are a bunch of variables, but does anybody see any glaring issues which might explain my problem?
    Thanks!

    No problem, thanks for the help! On my PC, screen capture using the Prnt Scrn button must be pasted into a program or taken/saved using the snipping tool. Either way the result appears to be untagged.
    Here are a few more examples if you get a chance to look in the future. I'm making sure the proper profiles are embedded correctly (you can confirm in both Photoshop [lower left] and Bridge [upper right]):
    Primary, wide-gamut monitor (sample includes embedded profile) - Viewing PSD w/ embedded ProPhoto RGB:
    Secondary, laptop monitor (sample includes embedded profile) - Viewing PSD w/ embedded ProPhoto RGB:
    Primary, wide-gamut monitor (sample includes embedded profile) - Viewing WhackedRGB Sample w/ embedded profile:
    Secondary, laptop monitor (sample includes embedded profile) - Viewing WhackedRGB Sample w/ embedded profile:
    Primary, wide-gamut monitor (sample includes embedded profile) - Viewing Sample Lowrez ProPhotoRGB w/ embedded profile:
    Secondary, laptop monitor (sample includes embedded profile) - Viewing Sample Lowrez ProPhotoRGB w/ embedded profile:
    So the WhackedRGB sample looks ok and the ProPhotoRGB samples look ok here, but it doesn't look like the WhackedRGB or ProPhoto samples have anything outside the sRGB range.
    Note what happens when I edit the WhackedRGB and ProPhoto samples simply by adding colors on the extremes of the gamut...
    Primary, wide-gamut monitor (sample includes embedded profile) - Viewing WhackedRGB Sample w/ embedded profile EDITED with gamut extremes:
    Primary, wide-gamut monitor (sample includes embedded profile) - Viewing Sample Lowrez ProPhotoRGB w/ embedded profile EDITED with gamut extremes:
    The issue is back - the colors are very different! At this point, it's probably a bug, right...?
    Thanks again!

  • Color management detective needed!

    I need help with some color management issues I'm having.
    I've noticed that RAW images imported into Aperture (both 1.0.1 and 1.1) look very different than those imported into PS2 via ACR. I've been told that this is simply a result of the different conversion algorithims each program uses.
    However, since I don't see a lot of discussion about that here I began to wonder if the differences I see between PS2 and Aperture are unusual. Also, I've noticed that when I export a RAW file from Aperture or PS2 as a JPEG, the colors of the resulting files look slightly different than they did before export (no adjustments were made in either program). Finally, when I upload the exported JPEGs to a website, the colors change once again!
    This is very frustrating, because I spend a lot of time adjusting the image and finessing the colors... only to see it significantly altered when I put it on the web. I'd like to better understand what's happening here and have more control over the process.
    So I've created a website with various examples of what I'm talking about. I imported the same RAW file into Aperture and PS2 without adjustments. Then I used OS X's Grab application to take a screen shot of how the image appears in each program. Then I exported the image as a JPEG from both PS2 and Aperture, using Adobe RGB as the embedded profile in both cases. (Note: my monitor profile is a custom profile created by EyeOne) Then I uploaded the JPEGs to a website I often display photos on, and then took a screen shot of how both the Aperture-exported and PS2-exported images appear on the web.
    Please look at http://web.mac.com/chriskresser/iWeb/Site/Last%20Roll.html
    So, my questions are:
    1. Why does the color vary so dramatically between Aperture and PS2? Is this normal, i.e. do you experience the same thing? Is there something I can do about it?
    2. Why do the exported JPEGs look different than their RAW master's? Again, is this normal and is there anything I can do about it?
    3. Why do the JPEGs uploaded to the web look different than the JPEGs opened in Preview or PS2?
    I've tried to standardize my color workspaces as much as possible, but I'm not sure I've done it correctly. In Aperture, onscreen proofing is off and I'm just using the default colorspace (which I understand is a wide-gamut RGB?). In PS2 I am using Adobe RGB as the working colorspace. My monitor profile is the custom calibrated Eye-One profile.
    I really appreciate any help you can offer. I'm pulling my hair out trying to get this straight.
    Thanks,
    Chris

    Thanks to everyone for helping me figure this out.
    Let me make sure I understand. In Aperture, when I go to export a JPEG for web use or printing from another application with my home inkjet I select sRGB as the color space.
    In PS2, I use Adobe RGB as my working color space, but when I save a JPEG for the web, I change the profile to sRGB before exporting. Do I use the "Edit>Convert to profile..." command for this? Or should I be using sRGB as my working color space in PS2 since most of my output is for the web and home inkjet? (There are occasionally times I send files to a printer for output, though).
    The Aperture RAW and PS2 RAW look significantly different on my monitor too, not just on the web. I'm using the default ACR settings - do you think they need to be customized for my camera? I see what you are saying... the ACR RAW does look much brighter than the Aperture version and kind of washed out. Not sure how to fix that though...

  • Color Management, Photoshop CS3 and Epson Inkjet Printer

    I have been down this road before but here goes again...
    Im using Photoshop CS3.
    Im printing on an Epson Stylus Photo RX680 using Photo quality inkjet paper.
    I know this printer is capable of very good quality prints.
    Thing is I can not figure out the correct combination of color management settings to get a decent print out of Photoshop or InDesign.
    I have read that you are supposed to turn off all printer color management and let Adobe manage the color. Doesnt seem to work.
    I just get overly magenta images that look awful.
    If I let the Epson color management control color I can get a lot closer but the print out is far from accurate or high quality.
    So what the heck IS the correct protocol for printing to an Epson inkjet printer from an Adobe app.
    BTW, I do seem to get a fairly decent print out of something like a PDF which I understand does its own postscript conversion before hitting the printer.
    Is this what my issue is?
    Does Photoshop or InDesign require postscript ripper software to get decent results out of an inkjet printer?

    Have spent hours with both Adobe and Epson support people. I've read several of these forums. Is there an insurmountable problem with CS3 and Epson (2200/2400 are mine)? I have the Leopard patches and upgrade 10.5.4.
    With Photoshop managing the color I get prints that are slightly underexposed and carry a pink cast. Color management is off. With the printer managing the color I get prints that are too green and dark. Epson advice here is to have color management off. There are two other choices for management but to adjust a perfectly balanced print to the printer's whim seem like cruel punishment.
    Have a calibrated monitor and my CS2 works beautifully. Perhaps the best idea is to just go back to CS2 until Adobe and Epson can decide what to do. According to Adobe people, the CS3 gives much of the management back to Epson. According to Epson -- with CS3, you should choose the printer to manage the color (since this seems to be the trend between the two companies) but we users are not happy with the results.
    What is the solution for right now?

Maybe you are looking for