Skip navigation

Tired of color desat when opening in Bridge/Lightroom. HELP!

Oct 27, 2010 7:34 AM

  Latest reply: Gabor-CS, Feb 17, 2014 6:37 AM
Replies 1 2 3 Previous Next
  • Currently Being Moderated
    Jan 22, 2011 9:50 AM   in reply to Johnnysks76

    Alright, one last one using the same image as before for consistency.

     

     

    Spyder2 Pro (left unmanaged, right managed SRGB)

    test.jpg

     

     

    Spyder3 Express (Left managed sRGB, right unmanaged)

    Test3.jpg

    One last bit about Connie's dilemma.  I recall she was using the Spyder3 Elite.  I've read that the Elite needed an update to support wide gamut monitors, and the Express that I was using does not.  Her problem could be a bad profile using the Spyder3 Elite.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2011 9:49 AM   in reply to Chris_BC_1
    Gator soup appears to assume you don't know that turning off color management will change the colors

     

    The problem (and my point) is we can NOT "turn color management off".

    We can only force our app/device to assume its default profile that may or may not match the source color space.

     

    And I recall that point was made and reinforced early on this thread, as was building bad/defective/incompatible monitor profiles and using broken color settings...

     

    But anyone is certainly welcome to ignore my posts.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2011 9:55 AM   in reply to Johnnysks76
    Johnnysks76,

     

    Your original pics didn't show as big a difference as what Connie had.  It even looked like there may have only been mostly a brightness difference.  When you're optimizing photos of course you don't want even the small change, and since you've bought a wide gamut montior you're interested in quality.

     

    I would guess that the standardization on sRGB years ago is the main cause of the problem.  If you're properly calibrated and color managed things should look the same on wide gamut or limited gamut monitors.  Or if you set your wide gamut monitor to do the limited gamut of sRGB you may be okay with and without color management in software.

     

    I have my Dell set to Adobe RGB mode and I've calibrated using a Spyder 2 Pro but with the ColorEyes Display Pro software.  I do plan to upgrade to the Lacie software and X-Rite hardware kit, but I'm not sure that either my calibration method or using the Adobe RGB mode of these is causing the large shifts I see, or in the large differences between some of the thumbnails vs. the full previews in Bridge.  It looks to be a more substantial change to me, similar to what Connie showed.

     

    Are you using the sRGB mode on your Dell?

     

     

    Update:

     

    Your last post came in after the above text.  Those pics are interesting.

     

    Message was edited by: Chris_BC_1

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2011 9:53 AM   in reply to gator soup

    I agree.  I think techinical debates aside, some of us are just trying to ensure a reasonable amount of consistencies when our work are view by others on their own system, which may not be colour space aware nor profiled correctly.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2011 9:56 AM   in reply to Chris_BC_1

    Yes.  I am working in an all sRGB space, from RAW, to CS4 Bridge, PS, and the U2711.  My lab takes sRGB.  Web browsers will support sRGB at the most (if at that), and I am sure none of my clients can properly display aRGB.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2011 10:20 AM   in reply to Chris_BC_1

    lol yes.  See the green shift in the first?  Honestly, the 2nd set is close enough for me, and that was all chucked up to the spyder2 not able able to read the wide gamut display properly for calibration, resulting in a bad profile and causing all colour space aware applications to have the green shift.  The shipped Dell profile was pretty garbage as well.

     

    Lastly, Connie's shift may be more pronounce as she had the Spyder3 Elite, which didn't support wide gamut out of the box as well, thus it may have given her a bad profile (but a different shift than mine).  Would have been interesting if she updated her software and see if everything works as it should now.

     

    Edited:  I'm rethinking the Dell profile.  I've been doing more digging, and suppsenly the spyder3 clips the gree channel on the U2711?  Going to have to experiment some more.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2011 11:25 AM   in reply to Johnnysks76
    some of us are just trying to ensure a reasonable amount of consistencies when our work are view by others on their own system, which may not be colour space aware nor profiled correctly.

     

    the only simple answer to that question is:

     

    CONVERT to sRGB (if you are not already there) and Save As with an embedded sRGB profile, then hand off your file

     

    I am not sure how to approach an explanation without using a 'technical' discussion about how color spaces interact...

     

    but a clue to the problem is standard sRGB color is a lot different than wide-gamut RGB monitor color

     

    in Photoshop, open one of your tagged sRGB files (use the embedded profile),

    then View> Proof Setup: Monitor RGB

     

    seeing is believing...

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2011 5:07 PM   in reply to conniez68

    Connie,

     

    In Windows 7, could post screenshots of the 3 tabs of your Color Managment dialog box?

     

    1-22-2011 7-37-06 PM.jpg

     

    Perhaps with the drop down of all device profiles showing such as below?  I know you probaly can't get all of them showing at one time, but perhaps your monitor related profiles are grouped together.

     

    1-22-2011 7-34-47 PM.jpg

     

    Forgive me if you've already been through this exercise, but it's really not obvious how this is set up in Windows 7.  And it's apparently not at all obvious how Adobe is using whatever color profiles are available either.  I'm hoping I can learn a bit more from your ordeal so I don't repeat it.

     

    Johnny,

     

    Keep us posted on anything you find.  I suggest reading through the reviews at  http://www.tftcentral.co.uk/  (both the wide gamut monitors as well as the calibration tools) if you haven't already.  Their info is why I plan to go with the Lacie solution.

     

     

    "gator soup",

     

    How about giving the "convert to sRGB" mantra a rest?  Johnny is obviously already fully up to speed there and I'll bet money that Connie is as well.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2011 5:39 PM   in reply to Chris_BC_1

    Thank you for the input, folks.  I think Connie is right, and I suspect it has to do with Spyder's profiling and how Windows 7 is loading the profile.  I'm going to do more testing, and I'll post back if I find anything.

     

    What I am very confused about is this:  Using spyder3's profile and their loader, I get consistently greenish colour across both color space aware and unaware application (think the Matrix's green tinge).  Using the shipped Dell profile and Window 7's profile loader, I get greenish colour in application that supports sRGB, and "proper" (or what my expectations are) in anything that doesn't read sRGB.  I am incline to think it is not just the profile, but also how they're loaded by OS and the applicaitons.  I'm going to try to find other loaders to see if I can find consistencies using Dell's ship profile.

     

    Connie, if you are finding issues with Spyder profiles loading when they're not suppose to, have you consider deleting them completely?  Windows keep them in the following directory:

     

    c:/windows/system32/spool/drivers/color

     

    Colorvision's profile would probably be in a file name spyder3express.icm (or in your case spyder3elite.icm) or something along those line.  I imagine deleting the actual file would be a sure fire way of preventing Windows or another application from reloading an undesirable profile?  Or, if you're hesitant about deleting profiles, you can always rename them from spyder3express.icm to spyder3express.icm.old so that windows cannot load it (as in affect, they can't find the file).  It's an old technician's trick.

     

    Gator, I appreciate your input, but as stated I have been using sRGB profile from capture to Bridge to CS4 for a few years now, so in this case it is unrelated to not using sRGB.  If you have any other ideas, I would welcome them and hopefully help us to find a solution.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2011 6:37 PM   in reply to Chris_BC_1

    "gator soup",

     

    How about giving the "convert to sRGB" mantra a rest?

     

     

    Okay, Chris_BC_1, it appears you know how Windows interacts with profiles and color-managed apps, so I will sit back and maybe learn something about this problem myself...

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2011 6:44 PM   in reply to conniez68

    Connie,

     

    Indeed there was information earlier in the thread about your color management settings, including in your original post.  (At this point one problem is there's reams of info in this thread.)  One thing I quickly noted is that you've gone from "Relative Colorimetric" rendering to "Perceptual".  Do you know if this change made any substantial difference?

     

    I also note that on the Advanced tab you're using "WCS profile for sRGB viewing conditions" instead of "WCS profile for ICC viewing conditions".  This is one I'm in the dark on but my instinct was that with any custom calibration the ICC choice would be the way to go.  Now that you've thrown in another curve ball with turning off the Windows Color System service I'm not sure this even matters at all.     Have you received any knowledgeable help on this setting that panned out?

     

    Also, if you're sticking with sRGB why not have your Dell's mode set to sRGB instead of Adobe RGB?  Did I see that right in the picture above?  (I'm trying to go Adobe RGB all the way through except when I share images with others for use on other PCs, so I'm using the U3011's Adobe RGB mode.)

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2011 6:59 PM   in reply to gator soup

    "gator soup",

     

    You've got two sRGB users here (in the recent posts) already who appear to very technically savvy about using sRGB.  I don't see your posts contributing to the discussion at hand.

     

     

    P.S.  For myself I have zero interest in the "sRGB is the holy grail" mentality that guys like Greg Ballard are preaching because I know just how limited sRGB is versus what the human eye can see.  Regardless of the widespread use of sRGB, simply continually repeating that using sRGB is the answer just acts to help hold PC color technology back.  One goal should be a much wider gamut across the board for all users, and another should be sure fire ways to avoid the issues that people are describing in this thread.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 22, 2011 9:31 PM   in reply to Chris_BC_1

    Ok, I found a pretty good work around based on these two thread.

     

    http://photography-on-the.net/forum/showthread.php?t=861984&page=2

     

    The op claims that the Spyder3 are clipping the green and generating bad profiles that cause oversaturated green's, and he suggested using collected profiles that others generated using Lacie Blue Eye pro per the below link:

     

    http://www.tftcentral.co.uk/articles/icc_profiles.htm

     

    I tried their sRGB profile using Window 7's profile loader, with my U2711 set to sRGB, both Bridge and PS set to North American General purpose 2 (aka sRGB work space), both the raw and jpeg does have sRGB profile (screenshot included for jpeg) contrast 50, brightness 20 (around 130 measure brightness, I forgot what the unit was), and after Bridge loads the profile the "shift" is much more subtle, and not very much green shifted.  Here is another comparision, using Irfanview with colour management turned off and then on (and reloaded), and it seems pretty usable to me.

     

    test5.jpg

     

    For prosterity, here is the screenshot confirming sRGB profile was indeed embedded into jpeg.

    exif.png

     

    To me the problem is clear.  The profiles from Spyder3 of the U2711 causes greens to be oversaturated.  The shipped Dell profiles was not a good match (thus I saw a large discrepency between managed applications's display of image such as Bridge/PS/Irfanview vs IE8/Windows), and the LaCie's profile are a pretty close match, which is the solution I am include to stick with for now.

     

    Lastly, let me assure you what I saw in Irfanview with color management turned on did match what I saw in Bridge/PS using North America General 2 in case there are any doubts about Irfanview's validity.  If there are any differences, they're beyond what my human eyes can precieve, as well as any potential clients of mine.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 23, 2011 7:35 AM   in reply to Chris_BC_1

    chris bc 1

     

    again, I am all ears to see how you solve this post with your great knowledge of windows color management and wide gamut monitor spaces

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 23, 2011 8:35 AM   in reply to gator soup

    In the vast land of Windows colour management and wide gamut monitor spaces, are there no space for the high road?  If there is no space for the high road, then surely there is no space on a support forum for ethuggary either.

     

    Connie was right about narrowing it down to the spyder profiles, Chris was right about the Lacie Blue Eye, and I help to tied it together with other info in regards to Dell 2410/2711's wide gamut and the spyder's inability to calibrate it properly.  Problem solved.  I hope no one else has to be frustarted by this as Connie, countless others and I have.  You'd be surprise by how many others I have found in various forums with the same undiagnosed problem who was told by others to just live with it.  I hope they find this thread and can revolve their problem and get on with what they need to do.  I myself have 18 weddings to finish!

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 23, 2011 9:48 AM   in reply to Johnnysks76
    Dell 2410/2711's wide gamut and the spyder's inability to calibrate it properly.  Problem solved.

     

    Thank you for posting your information about the Dell U2711 & U2410 displays because I have an interest in learning what the problem was here.

     

    The monitor profile and Spyder Pro profiling packages were pointed out as the most likely culprit early on this thread, but I am glad you figured it out there and posted your examples.

     

    I remember there was a certain Hitachi monitor that would not display properly using any custom profile and it too caused similar grief for everyone who tried to profile it...

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 23, 2011 12:10 PM   in reply to conniez68

    Conny,

     

    well, even when it works for you (in other words: gets your colors back to what you expect or how you like them to appear), I'm pretty sure your current settings make not much sense. You work with sRGB profiles, but the monitor is in aRGB mode.

     

    You believe you disabled Windows Color Management, but what you disabled is something different:

     

    "The WcsPlugInService service hosts third-party Windows Color System color device model and gamut map model plug-in modules. These plug-in modules are vendor-specific extensions to the Windows Color System baseline color device and gamut map models. Stopping or disabling the WcsPlugInService service will disable this extensibility feature, and the Windows Color System will use its baseline model processing rather than the vendor's desired processing. This might result in inaccurate color rendering."

     

    This service normaly stands on "manuall", and is used/started by third party modules only, IMHO.

     

    I also wonder, if it makes sense, to fall back to the internal graphic card and sRGB when using a wide gamut monitor.

    Guess the internal card is not OpenGl capable?

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 28, 2011 10:16 AM   in reply to conniez68

    conniez68 sorry for your trouble with this issue.

     

    The only point you need to make to a troubleshooter is Photoshop is not displaying the Tagged PDI images correctly in Photoshop. Period.

     

    It should be routine for him to verify what profile Photoshop is using and for him to rule that profile out (about five minutes).

     

    Moreover, a person with a working knowledge of Windows Color Management should be able to easily (and quickly) pinpoint the part of your setup that is broken by tracing the workflow back to the point where what should be happening isn't.

     

    Another poster wrote of similar problems that involves your monitor and profiling package so maybe that's your most helpful post in solving your own issue, too.

     

    The monitor is easy to rule out by swapping it it out.

    However, the system is not so easy (because so many people have had their fingers on it).

     

    +++++++

     

    In your shoes, I would put in a different hard drive, Erase it, install ONLY the OS, Photoshop and updates.

     

    If it fails at that point (with no more fiddling around), I would send it back to where you bought it and ask them why it doesn't work correctly.

     

    If it does work at that point, either the profiling package or the monitor you swapped out is the problem, or something is amiss in your old system.

     

    +++++++

     

    I've seen my share of PC 'experts" at work, they always seem to fiddle around, uninstall, reinstall, fiddle around, uninstall, reinstall and come back to repeat the process...when they do solve a problem they never seem to understand why or what happened, it always seems to have magically fixed itself during their fiddling.

     

    People who understand the question generally get right to the issue (unless there are bugs or hardware issues to slow them down).

     

    I wish you the best luck in solving this.

     
    |
    Mark as:
  • Currently Being Moderated
    Jan 31, 2011 9:43 AM   in reply to gator soup

    Didn't read the entire thread, but connie mentioned she was using a Nikon D70.

     

    Back when that camera came out the embedded profile as chosen incamera often couldn't be read by Adobe and other color managed apps. This NikonGear thread:

     

    http://nikongear.com/smf/index.php?topic=26719.0

     

    alludes that the way Nikon sometimes writes its profile tags incamera and/or in Capture NX can cause this. It appears the way the profile is written/tagged into the image can tell or not tell a color managed app whether to see it or not. There are rules to writing code especially when color is involved.

     

    I've often dragged and dropped images posted in thread discussions where one piece of software (Apple script "Get Profile Info") says the image has no embedded sRGB profile while Photoshop sees it and sometimes Photoshop doesn't see it and says it's untagged. No way of knowing the cause.

     

    Not sure if this only applies to Nikon jpegs and/or NEF's. This use to be a real issue in the past, but now I'm guessing has been fixed with newer Nikon cameras. 

     

    Just to test I'ld suggest connie shoot two versions of the same scene with incamera profile chosen, one in jpeg and one NEF and drag them directly to the desktop and open in Photoshop, no Bridge. See if the profile is seen in the jpeg and whether the previews differ between the jpeg and the NEF which should open in Adobe Camera Raw.

     
    |
    Mark as:
  • Currently Being Moderated
    May 13, 2011 9:50 AM   in reply to Tim Lookingbill

    this is a pretty old discussion but it was probably the only resource i found that actually helped with my colour management nightmare!

     

    i spent weeks and wasted tons of ink and expensive photo paper and seemingly to no avail. all i wanted to do was to stop me and my wife looking sunburnt in my print outs from adobe photoshop. I even bought a new printer before i realised the fault lay elsewhere.

     

    I have a dell u2410, on win 6 x64. I used lightroom 3.3 x64, photoshop cs5 32 and 64 bit and a host of other colour managed programs and others that were not.

     

    what i realise now (thanks to the previous posts) was that when i opened my images in photoshop they were desaturating. This meant i over compensated in the adjustments and hence when i printed all the colours were terribly oversaturated. What i couldnt work out was that in windows 7 thumbnails and preview, i.e. not colour managed all the colours looked pretty much like the prints. But open photoshop and they were as i wanted them, neutral skin tones.

     

    i checked and checked again that i was letting photoshop handle the colour management for prints and am 100% certain had the settings correct.

     

    i went down the route of various ICC profiles and luckily did not invest in a calibrating device for my monitor.

     

    to cut a long story short I found that the problem was with the ATI software and specifically the display color options (via DVI) - the color temperature control!! This was set to use EDID when unticked i found that when i opened photoshop my colours no longer desaturated!!! Woo hooo.

     

    and the other thing was definitely disable the windows color system service mentioned in a previous post - although it sounds like it shouldnt make a difference it definitely does.

     

    So now I had what I expected, colours look a bit naff in non colour managed software but "fairly" closely resemble what i see in photoshop, and now when i print to my canon mg5250 (using photoshop colour man) my prints "nearly" match what i see in photoshop!!

     

    Perhaps I would now benefit from true calibration and creation of a custom icc profile but i am pretty happy with the results.

     

    hopefully this will help anyone else in this situation

     

     

     

     

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 14, 2011 12:26 PM   in reply to conniez68

    Conny, I feel for you. A dreadful ordeal.

    I seriously suggest you shift over to Mac for the simple reason they have been built for graphics from the moment of birth in 1984. When the Mac O/S9 was found wanting it was completely ditched and a new O/S built on an reliable language, Unix. To the best of my knowledge all Microsoft upgrades are rebuilds on top of primitive DOS underpinnings. I mean primitive. Like a house on weak foundations. What is remarkable to me is that Windows works as well as it does despite this fact. But it remains a 50 year old product with numerous upgrades. It was originally created for business and accounting software, not graphics.

     

    As a user with experience of both systems, I would say reliability is far greater with Mac and ease of use leaves Microsoft for dead. Where the Mac connects and software automatically, provides free programs and tools, Windows posts dialogue boxes asking you to do this or that, to check this or that, it requires you to buy extra security and cleaning tools and if you need help ask your administrator! Two different worlds. Macs are not perfect but far easier to trouble shoot with an O/S that is packed with useful apps and tools.

     

    It is no small matter to pay for another Adobe Suite but as you are working commercially a way to fund it can be found. Believe me, after you make the change to Mac, you will wonder why it took you so long.

     

    Just my experience

    Good Luck

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 7, 2011 4:10 AM   in reply to conniez68

    Hi there,

     

    I just read your questions and the answers you got fom people all over the world. That's great!

    But none of them provided you with an answer. I think I have it.

    You can read it here: http://forums.dpreview.com/forums/readflat.asp?forum=1006&thread=37521 609&page=2.

    I think it's got to do with the camera raw settings, which you can change in the preferences panel in photoshop.

    I had exactly the same problem on my system (Mac OS 10.6.8) and I was running the latest version of photoshop.

    Only Jpegs and Tiffs showed this problem, when I looked at them in Bridge they turned from nice, warm looking to a cold blue and unsaturated color tone.

    When I fixed my settings in the camera Raw prefs, it all went back to 'normal'.

     

    Hope this will help.

     

    B

     
    |
    Mark as:
  • Currently Being Moderated
    May 24, 2012 11:45 AM   in reply to conniez68

    The same exact thing is happening to me. The "domino" effect of saturation going out happened.

     

    I tried the following for troubleshooting:

     

    I rebooted the computer.

     

    I unplugged and replugged in the monitor cable.

     

    I installed adobe updates

     

    I deleted all the files, and re-downloaded all the image files.

     

    I went in to the camera raw settings in photoshop and bridge and made sure they were matching

     

    I looked at the calibration of the monitor, but i know it’s not the monitor because the image looks fine in “windows picture viewer” application.

     

    If I minimize bridge and then maximize, the image will look correctly saturated, but when I click my mouse, or move the window, it returns to being desaturated and has a color shift.

     

    problem2.jpg

    It seems like a bug to me because all the profiles match.  I'm really not sure what to do here.

     

    --Paige

     
    |
    Mark as:
  • Currently Being Moderated
    May 24, 2012 6:19 PM   in reply to partyonpizza

    Paige,

     

    You apparently didn't go to the link provided above.  It's the Camera Raw Preferences from the Edit menu.  No rebooting necessary, no unplugging, and not a calibration issue.  Here is the dialog box:

     

     

    Capture.JPG

     

    Just make sure you have jpeg and tiff support disabled as shown.

     
    |
    Mark as:
  • Currently Being Moderated
    May 25, 2012 6:03 AM   in reply to Chris_BC_1

    Chris,

     

    This did not fix the problem.

     

    Thanks,

     

    Paige

     
    |
    Mark as:
  • Currently Being Moderated
    May 25, 2012 10:18 AM   in reply to partyonpizza
    I looked at the calibration of the monitor, but i know it’s not the monitor because the image looks fine in “windows picture viewer” application.

     

    Anyway, tell us which OS you use and what monitor profile is configured for the OS

     

    If I minimize bridge and then maximize, the image will look correctly saturated, but when I click my mouse, or move the window, it returns to being desaturated and has a color shift.

     

    This sounds like smaller previews where create with the correct colorprofile, while larger are not - either before or after a change must happend. What happens when you delete Bridges cache? Same same, or did it help (they all look okay) or are the smaller previews desaturated as well then?

    Jörg

     
    |
    Mark as:
  • Andrew Rodney
    1,386 posts
    Apr 16, 2009
    Currently Being Moderated
    May 25, 2012 10:44 AM   in reply to ablichter
    I looked at the calibration of the monitor, but i know it’s not the monitor because the image looks fine in “windows picture viewer” application

    Windows Picture Viewer isn’t color managed. It is incorrect (even if you prefer the appearance). Camera Raw, Photoshop, Lightroom are color managed. The appearance is correct** even if you don’t like the way they look.

     

    Assuming the documents have the correct embedded profile and the display profile is correctly defining display behavior.

     
    |
    Mark as:
  • Currently Being Moderated
    May 25, 2012 11:34 PM   in reply to partyonpizza

    Paige,

     

    Another way of phrasing Andrew Rodney's most authoritative comments would be to say is that if your monitor has not been accurately calibrated and profiled, then your monitor profile is indeed causing your problem.  Note the conditional "if " in the preceding sentence.

     

    You can never judge the true colors of an image in a non-color managed application, such as Windows Picture Viewer.  You can only evaluate the colors using an accurately calibrated and profiled monitor in a color-managed application like Photoshop.

     
    |
    Mark as:
  • Currently Being Moderated
    May 26, 2012 8:25 AM   in reply to station_two

    I would agree with all that if it wasn't for the fact that Windows Photo Viewer is fully color managed. Not only does it honor the embedded profile, but it also converts to the monitor profile. It has been color managed since Vista, when it was called Windows Photo Gallery. In XP, however, it was not color managed.

     

    But there could still be a problem with the profile, with Photo Viewer not reading all the properties of the profile.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 24, 2012 12:28 AM   in reply to twenty_one

    here's what I found through various tests regarding Windows Photo Viewer on Win 7:

     

    > as D Fosse stated, the general Windows Photo Viewer (open image via WPV) is color managed. If an image is untagged it will be displayed via sRGB (unfortunately not your default system profile, which could be your custom calibration profile)

     

    > Windows Photo Viewer in SLIDESHOW MODE (open image in WPV and then click the large center Slideshow button) is non-color managed and will display images via your default system profile, the same applies to MS Paint and Windows explorer thumbnails

     

    So on a wide gamut display, soft proofing an image in PS via your monitor RGB has the same appearance as that image in WPV in Slideshow mode or MS Paint, which is more saturated...

     

    The above information is valid for  ICC v2 profiles - Windows has issues with ICC v4 profiles...

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 8, 2012 12:32 AM   in reply to Iron_Mike

    I have a similar problem in this conversation http://forums.adobe.com/message/4757046#4757046

    Did you resolve it?

     
    |
    Mark as:
  • Andrew Rodney
    1,386 posts
    Apr 16, 2009
    Currently Being Moderated
    Oct 16, 2012 9:45 AM   in reply to Iron_Mike

    Iron_Mike wrote:

     

    here's what I found through various tests regarding Windows Photo Viewer on Win 7:

     

    > as D Fosse stated, the general Windows Photo Viewer (open image via WPV) is color managed. If an image is untagged it will be displayed via sRGB (unfortunately not your default system profile, which could be your custom calibration profile)

    That's a problem because assigning or assuming sRGB may or may not be the right assumption for this untagged image. On Mac, several OS app's assume untagged doc's are in display RGB (based on your display profile). Well depending on what version of Mac OS you are running. Apple seems to move all over the map here. Anyway, the best way to be working here is without using untagged documents !

     

    So on a wide gamut display, soft proofing an image in PS via your monitor RGB has the same appearance as that image in WPV in Slideshow mode or MS Paint, which is more saturated...

    Which is a process whereby you make PS provided an incorrect preview to match the other incorrect preview. If you look at the soft proof options, you'll see Monitor RGB (use your specific display profile) or Legacy Macintosh or Internet (sRGB).

     

    The problem with an untagged doc is even a color managed app has to make an assumption of the scale of the RGB numbers (are they sRGB, ProPhoto, display RGB, or any other flavor of RGB). When the assumption is correct, you should get a match.

     

    If the image is tagged in sRGB and you use your display profile for soft proofing (Monitor RGB), the preview is wrong! It looks way over saturated on a wide gamut display. The image is in sRGB but you're telling Photoshop to show you how those numbers should appear if they were the display RGB which is wide gamut, thus over saturated. And if you opened the same image in a non ICC aware app, it would look very similar. If you assumed display RGB here, instead of the correct assumption (sRGB), again, incorrect preview that is over saturated.

     

    This is a 'problem' with Wide Gamut displays in an sRGB centric world, non color managed world. We're to believe that sRGB is some standard behavior and to some degree, it is although the beavhior it defines reflects a CRT we haven't had around for years and years. To put it another way, if all sRGB similar displays were replaced with Adobe RGB like displays and all applications treated untagged data as Adobe RGB (1998), the differences in the previews would be much less. Your LCD isn't really an sRGB device. Your wide gamut display is really quite different. Untagged sRGB assumed as such or not on a sRGB like device looks pretty close (there can be differences of course). Untagged sRGB assumed to be Adobe RGB is just the wrong assumption and such, the preview is wrong.

     

    Bottom line, 9 times out of 10, if an image doesn't match between Photoshop, Lightroom or other ICC aware applications and the one you're comparing to, chances are, the other application is not ICC aware or it is treating the RGB numbers incorrectly due to the lack of an embedded profile.

     
    |
    Mark as:
  • Currently Being Moderated
    Dec 3, 2012 6:47 AM   in reply to conniez68

    Connie,

    i have exactly the same problem, only  i got it straight after the calibration with i1display pro. All colors shifted to some desaturated thing with slightly greenish hue all over the images. It looks **** indeed.

    There's no replies afte Oct. 16th here on, did you manage to fix the problem.

    I'm on win8 64bit (same thing was on win7 64bit).

    Thanks a lot for any update!

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 17, 2014 6:37 AM   in reply to conniez68

    I had the same problem.

    I used LUT Manager ( http://fotomania.nixz.net/lutmanager/ ) to load .ICC file. It solved my problem finally

    But it does not work after reboot. I saves it as a .LUT file that associated with LUT Manager and I droped it in Statup folder to run it automatically at startup.

     
    |
    Mark as:
1 2 3 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points