CS3 raw conversion color shift

When using the RAW converter in CS3 there is a noticeable change in color from the RAW image to the converted image. I am using two Dell E228WFP monitors that have been calibrated and this allows me to see both images at the same time. I moved the images so they sat side by side on the same monitor and a difference in color was still evident.
I suspect something is happening in the conversion process and would appreciate any suggestion to correct this.
I am using a Dell Dimension 9200 with a VISTA operating system.
Thanks

What application is displaying the raw file, and which application is displaying the converted file?
If you are looking at the preview of the raw file in Camera Raw's dialog--which application is hosting the Camera Raw plugin at the time?

Similar Messages

  • Canon 50D CS3 raw conversion noisier than DPP

    The ACR CS3 raw conversion of Canon 50D files seems considerably noisier than conversion in Canon's own DPP converter. Is this correct, and are there plans to put it right?

    ACR pretty much leaves the noise reduction up to you to configure the way you want it. The Canon software applies noise reduction automatically. I don't know if this noise issue has changed in later versions of ACR, but there won't be any more updates for your version. Have you downloaded the profiles that have been provided? Have you updated your ACR to version 4.6?

  • Raw Conversion: Colors not accurate. Correction with profile?

    Hi,
    When I create JPGs from my Raw files, the results don't look natural. Some colors have more saturation, some less. For example, the colors of the KoMi A series look somehow dirty; the reds of the Maxxum 5D seem to be oversaturated (dark reds are to bright, brown faces look rather pinkish).
    This is in comparison to the orignal objects, to the JPGs generated from the KoMi Raw converter and to the in-camera JPGs.
    Since Lightroom has tremendous color tuning options (under HSL and Color), I wonder whether a camera-specific profile can make the colors more natural. Has anybody tried for the KoMi cameras? Can anybody share a profile?
    I don't have a color checker, so this would be a tough one for me. I tried a bit, but whenever one color seemed right, another color had become worse.
    Here is my equipment:
    Cameras: Konica Minolta A2, Minolta A1, Konica Minolta Maxxum 5D.
    Other: My room has fluorescent tubes of type 950 (5000K, highest quality, Philips Graphica Pro) or of course daylight from outside. My screen is calibrated using ColorPlus hardware. I used a grey card for most of my photos. JPGs viewed with IMatch (color-profile aware).
    Regards,
    Martin

    Hallo Uli,
    there are two aspects of the color deviation:
    1. Displaying colors in LR
    This is what you are addressing in the other thread. I can confirm this behavior, but let's not touch this matter here.
    2. Raw conversion
    This is what I am talking about in this post. The effect is actually larger than the display deviation.
    Regards,
    Martin

  • Raw conversion color differences

    Yes, I know that Adobe had to guess at how raw files are encoded (I shoot Nikon)a and that perfect color conversion should not be expected but...
    I started with Capture NX2 and while I loved the quality of pictures I could get from it, it was very slow and cumbersome, and publishing photos was not possible.
    I switched to LR3 and found the photo management (publishing, collections, etc) to be marvelous (maybe other products have it as well, but I found my happy place.  However, I noticed that even with a calibrated monitor the colors were not right.  Below are two pictures labeled cnx2 and LR3.  The CNX2 version was processed to include "bluing" the sky.  Not much else was done.  The LR3 version (done as a training aid until this was found) is unprocessed except for an X-rite color checker profile applied (more on this later). Notice how the CNX2 red has turned pink or magenta in the LR3 version.  To try and fix the pink, I bought an X-Rite color checker and installed their plugin for creating profiles.  Made no significant difference.  This is really bothering me.  Sure with some skills I haven't yet acquired I may be able to target the red and fix it, but to do it correctly I'd need to know what It's supposed to look like, and I had hoped to no longer require the use of CNX2 so that wouldn't be the case.  I'm considering going back to CNX2 for raw conversions and maybe capture sharpening (I'm more comfortable with CNX2 capture sharpening numbers than I am with LR3).
    CNX2
    LR3/ACR 6.x
    Thoughts?  Suggestions?

    function(){return A.apply(null,[this].concat($A(arguments)))}
    Jeff Schewe wrote:
    Really, people tend to give Nikon and Canon far too much credit...in fact, they just barely got this stuff to work. I will say the cameras and sensors are pretty darn impressive...their image processing knowledge, not so much.
    Canon does seem to know how to make pleasing images and get the most out of their data.
    Some examples:  Canon does a better job, in some ways, at rescuing partial overexposure (compare sunset images).  And they know how to put a raw converter in a piece of silicon that runs in a tiny fraction of a second.
    But these things aren't really important...  The real issue is even simpler:
    If all you did was make the default profile for each camera produce the same colors the cameras themselves produce, while still providing all the same configurability and features, you'd cease to get complaints about colors being "off".
    Whether you think the cameras produce "good" color or the camera company engineers know anything about color is irrelevant.
    No one would be harmed by this, but you'd stop confusing customers who expect one thing and see another.
    -Noel

  • Lightroom 3.5 RAW file color shift

    I have a question about how LR interprets/presents RAW files.  I do understand that RAW files are just sensor data, and the preview that is shown by the camera is how the camera software itself is processing the RAW data into a JPG.  Also, I understand that different RAW processors interpret this data slightly differently.  That said, I like how my raw files look based on how my cameras (60D and Rebel xsi) show them.  The exposure, color, and saturation levels are great and based on this look, they would require only a few tweaks.  When I upload the RAW files to LR, initially, the files look the same or very similar as they did in my camera's preview. However, when I click on each file in library or develop, the file will initially, for about a second, show up as it originally came over, but LR will then say "loading" and the photo will get much darker and duller.  Why is this?  As I mentioned, I do understand that different programs interpret a camera's data differently, but it appears that LR is originally "seeing" the photos as I want them to look and then for some reason is interpreting them to be something different; why will the photo not stay as it originally looks when I first upload it?  This is requiring more editing on my end.  One other thing I have noted is that my RAW files already have adjustments made to them upon upload (exposure, brightness, etc.)  I noted another post that addressed this and indicated that there were settings that I would need to reset to correct this.  Is this also why the look of my photos is changing, or is that a different reason?
    Thanks!

    Lee, the auto lighting optimizer on the 60D is on the light setting I believe...there are several settings and it is on the lowest one.  As the auto lighting optimizer affects JPEGs (from what I understand), I guess I can extrapolate that the preview that the camera is showing me is "optimized" (and is a JPEG) but the RAW file is not?  As far as the values set to zero on RAW upload, I initially thought that they were NOT set to zero, but then was recently told that they were which confused me a bit, but you both have confirmed that my original thinking was correct.
    Hal, I have done some tinkering with the camera profiles but I will need to investigate it further based on your suggestion.  Thank you.
    One more question:  Would it make sense for me to upload my RAW files using Canon's software rather than LR, then transfer them to LR?  Or would this be pointless because LR is going to re-interpret them its own way anyway?  I would rather use LR only because it's so much easier. 
    Again, thank you both for your information.

  • Bad color shift for RAW photos in Adobe programs??

    I shoot photos with my Canon PowerShot S60 digital camera with the Canon RAW format [.CRW]. But whenever I open the .CRW photos in Photoshop CS3 and Lightroom 1.1, the photos look yellower [no adjustments]! Why does Adobe's programs do this? Is this normal for all RAW images opened in Adobe's programs--or is it just my camera? Is there a way to make Adobe not shift my photos colors by default??
    Original .CRW photo. Normal colors in Windows and other programs...
    http://img292.imageshack.us/img292/5214/normalrm9.jpg
    .CRW photo opened in Adobe. Yellower colors in Photoshop CS3 and Lightroom 1.1 [no adjustments!]...
    http://img292.imageshack.us/img292/6291/adobekf1.jpg
    My Canon PowerShot S60 camera:
    http://www.dpreview.com/news/0405/04051001canons60.asp

    Auto white balance is actually the culprit of these problems as your camera will attempt to measure it itself, and is often wrong. That's just the nature of these cameras. The only way to be sure is to shoot a grey card.
    > Microsoft RAW Image Viewer
    Is that the Vista version? Otherwise it does not do any correction for the display. Canon's zoombrowser has a checkbox that has to be turned on in order for it do correction and I do not know whether xnView can use a display's calibration. Of the apps you list, the only ones that certainly do color manage are the adobe programs, and, if your display's calibration is correct, are the only ones that you can absolutely trust.
    The reason the color looks different for a second when loading in LR is that it shows the embedded jpeg (the camera embeds a jpeg preview in the RAW file) until it calculates the actual RAW conversion. LR applies a default contrast curve BTW, you can try to see what happens when you use the zerod preset.

  • Color "shifted" in CS4 RAW files

    Hello everyone.
    Ill try to explain my problem. Until last year I used ACR (combined with Bridge CS3) to color manage my images. Then I would convert them to DNG using the Adobe DNG Converter, and bring them into iMatch (www.photools.com), which is the program I use to manage my image database. I would work with a calibrated monitor, and a sRGB color profile.
    The DNG images would look the same in Bridge and iMatch, and if I extracted the JPG preview from any DNG image it would also look the same.
    This year I bought a new laptop and a CS4 license (previously I was doing the CS3 work using a license from the place I work at). Ive calibrated my laptop screen with a Pantone Huey Pro screen calibrator.
    When I open my images in CS4 the color in all of them looks "shifted", as if the white balance was off. They look consistently greenish and somewhat washed out. This happens in Bridge, ACR and Photoshop.
    However, if I open any of the JPG images (the ones that I created extracting the preview from the DNG files) they look the way they should. So from this I can infer that it can't be a screen calibration problem (otherwise both the JPG and its DNG counterpart would look wrong, instead of just the DNG).
    So it seems like CS4 is rendering the DNG images differently than it should. But I havent been able to find out how to correct the problem.
    Some other info: In the ACR flyout menu I have Image Settings selected, and under the Camera Calibration I have Embedded selected. Ive already tried (at the suggestion of Adobe support) to reset the Bridge preferences by holding CTRL+Shift when Bridge loads, but this hasnt corrected the problem.
    Also, here are my system specs,:
    - Precision M6400: Intel Core 2 Duo P8600(2.4GHz,1066MHz,3MB)
    - Display : 17in Widescreen WUXGA (1920X1200)
    - Memory : 4096MB (2x2048) 1067MHz DDR3 Dual Channel
    - Graphics card: 1GB NVIDIA Quadro FX3700M (with 1GB dedicated memory)
    - Hard Drive : 200GB Serial ATA (7200RPM)
    - Operating System : WXP Pro SP3
    I have already contacted Adobe support about this a few days ago, but so far no luck. So I thought Id try the forums as well and see if anyone here has any theories as to what the problem could be. Im stuck until Im able to solve this, so any help would be appreciated.
    Thanks.

    Hello,
    I'm still having trouble with this same issue, wondering if anyone has further thoughts.
    I've read some of the similar threads, like: http://forums.adobe.com/message/1203718 and  http://forums.adobe.com/message/1203965
    But I'm still confused.
    I hadn't noticed the color shifts in Bridge being so pronounced until recently.  So maybe something got inadvertently reset?
    It would be a bad idea to change my computer's color profile to generic sRGB (as someone suggested), since I have a good calibrated color profile via the Gretag MacBeth (yeah, it's older) EyeOne Display. I've used that calibration device for years, updating every 6-12 months. Never been a problem.
    It doesn't make any sense to me that Bridge should alter the colors of thumbnails/previews for RAW images (from the very good looking camera setting) before I even open Camera Raw to work on the RAW images.  I don't work on every single RAW image, and doubt anyone does.  But if I have 50 landscape shots, and the mere act of looking at their previews in Bridge turns all their skies unnaturally purple (which is currently happening), I lose any visual record of what the skies really looked like -- or at least a much closer approximation.
    My Canon 40D's jpg previews for RAW images are quite good when they initially show up in Bridge.  I'd really like to keep them until I work in Camera Raw, to give me a good visual memory starting point until I can get to work in ACR.  Sometimes I don't start serious work on an image for many months after shooting.
    Someone please correct me if I'm wrong, but it also doesn't make sense to me that a solution is to make a new Camera Raw default based on a photo I've worked on in ACR, because the color settings always depend on the lighting situation a photo was taken in, don't they? How could a daylight photo's settings be right for an indoor or sunset shot with totally different lighting and color temps?
    Bottom line question:  Is there any way to prevent Bridge from altering the color in thumbnails/previews of RAW images before you've worked on the images in Camera Raw?  (Even if you click on a thumbnail to see the preview in Bridge, I mean.)
    Thank you very much!!!
    ~Glenn
    Message was edited by: glennooo - for clarity and to fix a link

  • Exported Raw Conversion Image Resolution and Assigning a Color Profile, etc

    In Aperture 1.1, although I set the exported Raw conversion image resolution to 300 dpi in the preferences, it continues to come out at 72 dpi which is something of an inconvenience. Also, is it possible to assign a color profile to the "exported version" so that it is congruent to my PS CS2 color workspace (if that is what its called). Is this program capable of carrying out a conversion as a background operation? Finally, can the layout windows be configured so that they remember how they have been used in the past? Thanks.

    Iatrogenic huh! Cool!
    Anyway, I'm not real clear on what it is you are trying to accomplish. Despite your obvious vocabulary skills, there seems to be some disconnect relative to what you are trying to accomplish. You are right that "exporting a version" in Aperture is roughly equivalent to what happens in ACR when you "Open" a RAW image into Photoshop. In both cases you have, hopefully, already done the adjusting of parameters you want prior to "exporting", or "opening". When you "open" or "export" you wind up with an "image" composed of pixels, whereas in the RAW adjustment phase you are just working with a temporary thumbnail and a set of mathematical instructions. Big difference, I suppose is that when you "open" and image from ACR into CS2, the resulting image is truly just pixels and has not had a "file type" applied to the file yet, until you "save" it, while in Aperture, if you "export" a file to CS2, or to the desktop, you end up with the file type already applied. Presuming you "export" a 16 bit TIFF or PSD, there is no operational difference.
    I could be wrong, but with the new Bayer Demosaicing algorithms in Aperture 1.1, and the Camera RAW adjustments, you should be able to come up with an adjusted image that is VERY close if not identical to one done in ACR, with the possible exception of lens abberation adjustment. I was very critical of the RAW adjustments in 1.0.1, but I am very happy with the capabilites in 1.1. That said, I think there is still some room for improvement in user friendliness of some of the adjustments such as Levels.

  • Pentax K-x RAW color shift problem with Aperture 3

    I have seen a few posts similar to what my problem is but not exactly.I have two Pentax K-200D's and a new Pentax K-x. I shoot RAW with all of them and the K-200D's work great. The RAW files however from the K-x are doing something strange. Sometimes (more and more though) the files are being imported into Aperture and there is a radical color shift after they finish loading. ALL of the preview thumbnails look fine in the camera and the Aperture import window. However, after importing them and processing is complete, some of the shots have a magenta color shift, but most that have this problem shift radically to a green tint. Everybody looks like they are in "The Matrix."
    I do not have any brightness correction on the camera turned on as other posts imply might be the problem. I have also remove the Aperture RAW 3.2 and tried 3.0 and 3.1 with no solution. 3.0 doesn't recognize the files at all and 3.1 does the same thing as 3.2. Here are two examples of UNEDITED RAW files:
    Frame that looks fine in RAW
    http://gallery.me.com/mattcline#100470/IMGP5982&bgcolor=black
    The next frame taken with the same settings on the camera:
    http://gallery.me.com/mattcline#100470/IMGP5983&bgcolor=black
    I do have one possible pattern. I had the camera set on rapid fire capture. It appears to me that the first frame I take when the shutter button is depressed looks and translates fine. All the subsequent frames take in rapid fire under the same shutter release have the green shift when taking shots in relative shade. Things taken in bright sunlight have the magenta shift.
    Any ideas on what is going on or how to fix this?
    Thanks.

    kb8wfh wrote:
    I just downloaded Apple's RAW 3.3 and it still made no difference.
    Going back over the files, I found that going back and forth between the two, see no difference in the RAW processing headings. I did see however that in the meta data that the two pictures I have in the example of those listed above have one difference. There is a setting on the Exposure Bias for the one that was fine was -0.3 ev and the one that has the green contrast blast has an Exposure Bias of 0.3 ev. So the one that looks right is slightly negative. Doesn't seem like that should be a big difference, but apparently it is.
    I did take some pictures with the RAW+JPG setting and I had the same problem with the RAW files. Some were ok, some were green, others were magenta shifted. However, all the JPG files looked just fine.
    Switching from Aperture isn;t really an option for me. I have been using it for a long time and it generally works very well...perfectly with my K-200D's. It's just some bug with the RAW decoder for the K-x.
    It's a known bug and I have been in touch with Apple staff over it, including engineers. It's not just the K-x. Other brands (Canon) and models suffer from the RAW processor gone wrong.
    Right now there is no fix. At the pace Apple works at, there may not be one for quite some time. Use JPEG, use iPhoto, or move to Lightroom.
    Another suggestion is to phone customer service and complain that their "Pro" program is not working as expected. I spent hours with an engineer going over the issue including a screen share session, only to be told to use JPEG.
    This was 4 months ago.

  • Bad D3 RAW Conversion - Clipped color in shadows...

    ...and other issues.
    Well. My thread was deleted last time and I didn't get any reasons as to why. What is up with this place? Good thing I always copy my message before posting. Never know when the internet is going to go kaboom... (or somebody is going to delete your thread.)
    I just shelled out $200 for this product and the moderators are deleting my threads?!
    I think I smell fish.
    - Issue 1.
    Aperture's raw conversion for the Nikon D3 is clipping the color from shadows.... generally. (About 99% of the time.) It is possible that the couple of images I haven't seen the problem occur in have color detail just above the clipping threshold.
    This really makes for some ugly images.
    Aperture team: How about we get an update to fix this?
    I just spent 5 hours importing and organizing ~3k images into my existing library now that Aperture finally supports the D3 but now I can't use it. Unfortunately I have been forced to use Bridge for the last couple of months due to no D3 support. Through this, I have become accustomed to its (Bridge's) speed and ACR's RAW conversion. Now Aperture flies and it is MUCH appreciated but the raw conversions are a little noisy and the colorless shadows is a BIG problem.
    In the samples below, watch the shadow on the brown wall behind her as well as the shadow areas on the neck in the close up. Note that the red strap in the file with the color clipped has almost no red left.
    I have another image I took that I was playing with to see how far I could pull the file and still retain shadow detail. The image is in color and looks alright when opened with ACR but when I open it in Aperture, there is almost no color at all in the image. This leads me to believe that Aperture's D3 raw conversion is throwing away color information at a specific level.
    I have a couple of sample images side by side here:
    http://www.uberfoto.com/images/misc/temp/colorclipfull.png
    http://www.uberfoto.com/images/misc/temp/colorclipcrop.png
    - FYI, I don't have any of these issues with D200 NEF's.
    - Issue 2.
    The RAW sharpening has absolutely no affect on any of my D3 images. I bring up the camera model because it could be a specific camera issue. I haven't heard of anybody else having this problem.
    - Issue 3.
    Where are the CA removal tools?
    I don't mean this in any sort of rude way. My intention was to bring up some issues that I have come across and see if I could get some feedback.
    -Josh

    The email I received was strictly regarding my post being deleted. I have not heard anything in reference to the RAW 2.0 problem.
    Here is a comparison of the same image. One exported from Aperture and the other opened in ACR and saved as a JPG.
    http://www.uberfoto.com/images/misc/temp/colorclipAP-ACR.jpg
    http://www.uberfoto.com/images/misc/temp/colorclip_AP-ACRzoom.jpg
    Another thing I noticed is that Aperture preview generator does not clip the color data like the raw converter does. Previews created after image adjustments retain their color in the shadows while the full composite view displays in monochrome. This is an image I took in the studio where the PW died and the flash didn't pop so it was very dark. The original image was nearly all black with no discernible details until I pulled the exposure back up. The ACR conversion looks nearly identical (discarding small differences in brand interpretation) to the "Preview" in AP2.0.
    http://www.uberfoto.com/images/misc/temp/colorclipraw.jpg
    http://www.uberfoto.com/images/misc/temp/colorclippreview.jpg

  • Color shift in cs3 and elements 7

    when loading an image into cs3 or elements 7 I am getting a large color shift to magenta and the image is getting very dark. I have reset the color settings and reset to default but no improvement in the images. the pictures look good in bridge or any other picture viewer on the computer. Any suggestions.

    I do not have access to the computer at this time but I set everything to default  srgb

  • My Photoshop CS5 color shifts where CS3 does not...

    I've been having problems with my current version of Photoshop (CS5) and its "save for web and devices" option. All photos saved for web are significantly color-shifted - more contrasty in some cases, but oddly washed out in others. I've tried altering settings in the "saved for web" feature to no avail.
    Even stranger, to my mind, the compressed photos only display the shifted colors when sent through email or posted on-line - not when looking at them in photoshop.
    By chance, I recently had to "save for web" some photos using my laptop's CS3 - and here's the rub - they were perfect. No color shift whatsoever.  What's more, the settings for my CS3 "save for web" are identical to the CS5 settings.  I'm completely flummoxed now, and have taken to transferring photo I need saved for web to my laptop and using the CS3, but this still seems like madness to me.
    I know this is a long shot, and of course there are too many variables to be accounted for, but has anyone encountered a color-shift problem with CS5 in partcular? One that does not appear in CS3?
    Maybe I should completely reinstall my CS5 and see what happens.
    sigh.

    Compare what you have in edit >> color settings
    then also in save for web >> preview
    Most major web browsers now recognize color  profiles which is good so mac & pc look alike, btu you may be viewing without profiles depending on what else you are using to view your images.

  • My nikon d3s raw files in lightroom have color shifts

    my nikon d3s raw files in lightroom have color shifts in lightroom can anyone help me please?????

    An answer to "when do you see it?" would also be helpful, just in case it relates to: http://forums.adobe.com/thread/358016

  • Color Shifts printing from CS3 Apps

    I just loaded CS3 on my system (Mac OS 10.4.10, Dual Core Intel Xeon). I have an OKI5300 laser printer. I sent my client a pdf generated through Indesign, and we are both experiencing the same problem: severe color shifts in our print-out. Indesign prints color correctly, but both Acrobat and Photoshop (I recreated the design in Photoshop by copying and pasting the elements into it) were severely out of balance. However, Acrobat 6 professional, which I still have on my system, printed the original pdf file perfectly. Your suggestions on what to do about this problem.
    Mary Moore

    Problem resolved! I called in to support, as my CS3 package was brand new, and the CS rep figured it out. When printing from Acrobat 8 to a postscript laser printer, the program has a default setting in the print window, under advanced/color profile that says something like Color management by print device. He suggested I select No Color Management, use source profile. This I did and it worked. I think generally Adobe has, in the software, pretty good color management, so letting the software and not the hardware manage color is likely the best choice.
    But you are likely right as well, i may also have to synchronize color spaces between software and devices.

  • LR 2.5 to CS3, fine; to CS4 has color shift..?

    hi everybody-          
    MBpro, 2 monitors all calibrated.  my workflow with CS3 was just fine, but after a recent upgrade to CS4 my images have a distinct color shift that looks like a profile mismatch.  i'll have my CS4 image floating over the LR window and there's an obvious shift.  if i output and open the same image the same way in CS3 it matches perfectly.  perhaps i'll cross post this to photoshop forums, but there seems to be an issue with how i've set up CS4 color spaces as opposed to CS3, even though they seem to have identical settings.  any ideas?

    okay, i figured it out, thought i'd post my solution here if anyone else has this issue.  in CS4 there's a new option in preferences>performance.  for my rig (MBpro17, 2.4ghz, samsung syncmaster 215) i had to turn OFF "enable openGL drawing".  now the colors from LR to CS4 match just fine, as they should.  what the #@&%!!
    now, what was i doing again? 

Maybe you are looking for