Lightroom 3.5 Raw Image Magenta Colour Cast

My Nikon D7000 raw files all have a magenta cast to them when imported into Adobe Lightroom 3.5, and I wasn't shooting on multiple exposure. I am running Windows 7 64-bit, and have Adobe Photoshop CS4 as well as a trial version of Adobe Lightroom 3.5 (testing to see if I would like to buy as I can't read my raw files in CS4).
If I convert my raw files to DNG, and then view them using camera raw (CS4), the magenta cast is gone. However, if I view those same DNG files with Lighroom, they have the magenta cast. I have tried re-importing my catalogue, but everytime they all have the same strong magenta cast. Help would be much appreciated as I can't seem to find anyone else having this problem, and I otherwise can't access my raw files.

I managed to fix it actually. I don't know if you can update camera raw with just LR, as I did my update through PS5. So looking for updates in PS5, it updated my camera raw and now the problem is gone. Last time, with LR3, it was a stupid thing Adobe did, where you could only get the most current edition of camera raw by upgrading to PS5 (and I had been on PS4) ... so after upgrading to PS5, I could finally get the correct camera raw version. Hope it helps.

Similar Messages

  • Magenta colour cast added to exported jpg photos

    I shoot raw with my Canon EOS 5D and import the raw images to LR. There is no Development preset. Colours in LR look OK on my calibrated monitor - this is not a camera calibration problem as suggested in LR help and knowledgebase; I have tested these solutions with no change. Basic edits are usually about exposure correction or spot removal.
    When I export the photos as a jpg files they have a magenta colour cast, sometimes quite strong. LR cannot be used for reliable prediction of what an exported photo will look like.
    I checked with Canon Digital Photo Professional. The colour of the original photo shown in DPP is exactly the same as the jpg colours. This makes me think that LR display render is unreliable.
    My system is as follows
    LR 1.4.1 on PC with XP Pro service pack 2
    LR installed on C: with over 80GB free space
    LR catalogue on second internal F: with over 34GB free space
    Photos on USB drive with over 220GB free space
    2GB RAM 2.4 GHz P4 with Dell 2408WFP LCD monitor
    LR export to sRGB 80% jpg 1000 pixels short edge (reduced from 4368x2912 pixel)

    >I calibrate my monitor with Monaco EZcolor 2.6.5 and an i1 calorimeter from x-rite. I have profiles for day time with natural light and for evening with artificial light. I have also tested the monitor with various pictures for black and for colour rendering.
    Excellent! Be aware that I have seen problems on this forum before because of defective colorimeters (a calorimeter is a device that measures heat BTW!).
    >I use LR and Photoshop CS2. I use Canon software to download the photos from my camera to sub folder of my own choice then I import them to LR. The colour rendition by LR and Photoshop are identical.
    That is a very good sign. If the color rendition between Lightroom and Photoshop is identical, you do not have a bad monitor profile, so we have to think about something else.
    >The exported jpg files are uploaded onto a web page at panoramio.com for use on Google Earth. Therefore I view the jpg files with Mozila Firefox 2.0.0.14 and with Google Earth 4.2 The colour rendition by Canon Digital Photo Professional of the raw file is identical to the jpg rendition by Firefox of the web site photo.
    Be aware that DPP can be set up to not color manage. There is a preference you have to turn on to make it color manage (you should if you want to trust the color). If you see a difference between Lightroom/Photoshop and an unmanaged browser, it is usually due to the fact that the browser is unmanaged. You cannot trust an unmanaged browser to show you the correct color even on a calibrated monitor. You still should not have a color cast in the neutrals though! Perhaps you should post some examples such as a direct Lightroom export (perhaps simply a link to the panoramio page) and a screenshot of what it looks like on your machine. That could perhaps narrow the issue down.
    Do images such as the third image down in the left column (labelled "sRGB Standard RGB 2.2 gamma") on this page http://www.gballard.net/psd/go_live_page_profile/embeddedJPEGprofiles.html look normal (i.e. normal skintones, not too saturated, neutral whites) on your screen?
    >I don't know about Firefox 3.0, it has not been offered in the normal auto update. I don't know about the secret setting for Firefox.
    Read this: http://lagemaat.blogspot.com/2008/06/firefox-30-released.html

  • Camera raw images change colour in adobe bridge

    I have photoshop CS4 and import my camera raw images into Adobe Bridge.  When I view the thumbnails in bridge my raw images look vibrant and exactly like they appear on the camera but when I go to open them in camera raw edit they change colour and look washed out before I've made any changes.  Can anyone help me figure out how to correct this?

    ssprengel wrote:
    My camera is set to shoot sRGB JPGs and is set to all zeros for the brightness/contrast/saturation parameters.
    What is your camera set to as far as these basic toning settings, as well as any automatic things like DLighting or highlight compression and perhaps any custom curves or whatever that is called for Nikons?
    First paragraph - so is mine.
    Second paragraph - all other settings are neutral/zeroed/turned off, as per my post to which you responded. That is, no additional tone curves - Active D-Lighting turned OFF (why anyone would let the camera decide what to do do with highlights and shadows is beyond my level of trust) , Jpg compression is Optimal (least possible) et cetera.
    Think I now have an explanation for the different displays in ACR (and Bridge) that I have been experiencing. Took a new duplicate Jpg/Raw shot with the in-camera Picture Control set to Neutral. Now, when both the Jpg and .NEF Raw are viewed in ACR, with the ACR Camera profile set to Camera Neutral, they appear, ASAICT, identical. Saved Camera Neutral as the default ACR Camera profile. Now back in Bridge, the images also appear pretty much identical.
    I think what was happening previously was that I had failed to save Camera Standard in ACR as the default Camera profile, and it was defaulting to Adobe Standard, and hence it was rendering Raw thumbnails for Bridge to that Camera profile - hence the difference in appearance between the Jpg and Raw in Bridge. Unless I have got it completely wrong,  I think my problem is now solved.

  • Has anyone had issues with poor image quality when using lightroom to process raw images from Canon 7dmk2

    Hi everyone..
    ..I have been having image quality issues when using Lightroom to process raw files from a 7d mk2... They are all soft with poor clarity.....tonight in despair I tried processing them  using  canon's software and they are totally different..."much better"
    anyone else had similar problems....Andy

    I have a 7D2 and have not had what I interpret as poor image quality that has anything to do with the camera.
    Can you post a screenshot of what you’re seeing and what specifically you don’t like?  Maybe there is something you can do differently or at least there may be an explanation for what you’re seeing.
    And if you have a raw image that you wouldn’t mind sharing in a public forum, upload to http://www.dropbox.com/ then post a public share link to it in a reply, here.
    In other words post a screenshot of what you see in LR, another of what you see using DPP, and a link to the raw file you’re processing.

  • Lightroom not seeing RAW images from Canon 20D

    I am running Lightroom and if I take RAW images on the Canon 20D and I click Import, select the 20D as the source, it says "No images to import" now if I open the EOS transfer utility and download it there, save it as a CR2 and then Open it in Lightroom it all works fine. Am I doing something wrong?

    I'm having horrible problems uploading my RAW files, captured with my 20D, using a cardreader. More often than not, Lightroom hangs after a dozen or two files, though more are imported than are actually displayed. Even when a "successful" import occurs, at least ten or fifteen files are ignored or rejected for reasons that are utterly unclear. I never have similar problems with Photoshop Bridge.
    I'm running Windows XP with 2GB of RAM, an AMD Athlon 64 3400 Processor (2.2 GHz), NVidia GForce FX5500 graphics card, and an absurd amount of free space in my RAID array twin internal 250GB HD's and 320GB external drive. Courtesy of absurd problems with Roxio in the past, I've updated DirectX and all my drivers and UNinstalled and roll-back my OS to Windows MediaPlayer 10 (ver. 11 really screwed up my system, a problem lots of people, apparently, have encountered).
    PLEASE HELP! I've read and heard so much positive feedback on Lightroom - but for me, the darn thing, thus far, has been a bit of a waste of money. Workflow tools aren't worth anything if the beginning of the proces - uploading images - is a huge problem.
    Regards,
    Bill
    [email protected]

  • RAW Images show colour spots (Nikon Capture NX 2 vs. Aperture 2)

    Hi All,
    if I compare my RAW images in NX 2 and Aperture 2.1 then Aperture is loosing that game in terms of image quality. After playing around since yesterday I see more details and much more sharpness in NX 2. To find out whats going on I did some comparisons. If I enhance sharpness in Aperture I see sooner or later artefacts, not really comparable.
    But there is one more issue: I see colored spots (blue, green, orange). I didn't apply any changes to the RAW, just import and view "original file". I can't see those spots in NX 2. I disabled everything in NX, even all camera/lens adjustments.
    Please see some example images there: http://home.arcor.de/stocky2605/
    picture.jpg: an overview, the whole image
    crop aperture.jpg: screen shot of Aperture import, no changes made
    crop nx.jpg: screen shot of NX 2 import, no changes made
    crop nx brighter.jpg: screen shot of NX 2 import, a bit more light to the shadows
    Are there any ideas or hints what's going on here? What are these little spots?
    Thank you very much.
    Kind Regards
    Klaus

    OK, time to say good-bye, I like Aperture in terms of managing my images, but today I switched over to CaptureNX 2. Over the last 15 months I learned a lot about developing RAW images, thanks to Aperture. Now it's time for a change, my images look much better with less time to develop then in Aperture. On the other hand, it takes me more time to organize them now. It seems, it's not possible to have the best of all "worlds" within one app.
    So, thanks to Aperture and good bye.

  • How can lightroom 5 accepts raw images from om-d camera

    I need help as I want to use lightroom 5 but when I download the images lightroom 5 will not import it.

    If you updated to version LR 5.6 you should have support for all the Oly OMD models. See the link below for all supported camera models.
    Camera Raw plug-in | Supported cameras

  • Magenta color cast problem on canon 7d raw files

    when i import canon raw files (cr2) into lightroom 3, i get a magenta color cast over the whole image. the thumbnail image looks fine, but when lightroom opens up the image, it get's a magenta color cast over the whole thing. i shot raw+jpeg mode too, and there's a huge differnce in color between the two. the jpeg looks like how i shot it in camera but the raw image has the ugly magenta color. not only do i get this ugly color, but it seems like there's added noise compared to jpeg image.
    i tried converting the cr2 into a dng. but when i open that in lightroom, i get the same problem.
    i use aperture 2.1 (i only use the lr3 trial so far), but i have the same problem there.
    i use cs3 but i downloaded cs5 trial.
    acr i have is 6.1
    help.
    thanks.

    Go to develop and the callibration tab and change it in the pull down menu to a canon default like 'Neutral' and not the adobe one which is made by somebody totally colour blind or obviously a Nikon fan.
    Although this is weird as the problem for me has always been canon JPG's with the cast and not the RAW.
    Also check your white balance cause Lightroom seems to change it whatever..  'AS SHOT' is a big fat Adobe lie so use a preset from your camera in the drop down box.. Why?  I shoot with Canon's flash WB setting which i know to be 5500k with the tint at zero.  On import, Lightroom changes it to 6150 and adds an amazing +7 on the magenta tint, if i chose 'FLASH' things suddenly turn to what i see on the camera LCD..  I'm sure that is where the big fat tint has come from since day one.

  • Help with importing .raw images and b+w filters

    I have recently been taking alot of b+w images.  With most of these images I apply a red in camera filter.  When I then import the pictures into lightroom 2.3 a color version of my picture is then rendered, without the red in camera filter that i took the pictures with.  Does anyone know of a way to restrict lightroom from changing .raw images to their color version and to show them as they were taken.  If it matters I shoot with a Canon 1000D.   PLEASE HELP!!   Thanks.

    Lightroom ignores metadata settings which are what is applied when you work with RAW and use Canon's Picture Style settings.  
    Those will be applied to JPG, but not RAW.  This is actually a feature, not a bug, because it's considered to give you more control by using the settings in Lightroom for Monochrome, and apply red tints-- plus you could always still have the flexibility of making a color print if you wanted, which you'd lose if RAW enforced the Picture Style settings.  If it bugs you, shoot in RAW+Jpeg (or just Jpeg), and bring the Jpegs into LR, but I'd recommend sticking with RAW and applying the edits you want in Lightroom instead.

  • Importing images with Lightroom 2  & Camera RAW 4.5

    The following query has been raised with Adobe Technical Support (5 days ago and I am still waiting for a response/reply. They claim to reply within 24 hours but they have not on this occasion......they seem to be ignoring me
    Perhaps a fellow user can help to identify or resolve the problem.
    Operating System:
    Windows XP Professional (Service Pack 3)
    Software:
    Adobe Design Premium CS3 (10.0.1); Photoshop Lightroom 1.4 (which was working fine) and Lightroom 2 (on trial and not working particularly well)
    I am using a trial download of Photoshop Lightroom 2 (with Camera RAW 4.5 in Photoshop CS3).
    I am having a few problems with editing Lightroom 2 images in Photoshop CS3 but I understand that Adobe is currently investigating a solution to this problem.
    I have also noticed another potential problem since I have started to import images from a computer drive to Lightroom 2 and converting the Manufacturers RAW files to DNG (with the option to leave the files at their current location/drive).
    My RAW and JPEG files open ok in Camera RAW (v 4.5) for basic editing and subsequently to Photoshop for more detailed work. The problem is that all my images are now opening as Smart Objects by default in Photoshop CS3, as opposed to opening as a Background layer". (I have not knowingly opted to use the Open as Smart Object option.
    I am not entirely sure how this came about but I have also lost the capacity to edit images with empty Levels adjustment layers or percentage (%) grey fill option).
    I am able to highlight the respective layer and create the empty Levels adjustment layer, change the blend mode to either Multiply or Screen, fill the Layer Mask with Black (Alt & backspace), change the opacity level as desired, select the brush tool and change the foreground colour to white to enable the applicable Dodge or Burn processes.
    Unfortunately, it does not function irrespective of the preferred opacity level. The Dodge or Burn feature is static with no effect on the image.
    I cannot recall any settings to open all files as Smart Objects in Photoshop CS3 but would welcome some help in identifying such a setting if it exists. Alternatively, I would welcome any other suggested methods of correcting the above difficulties.
    The same difficulties are evident when I try to use the Dodge or Burn features via the Edit and Fill option with a percentage of Grey and the Overlay Blend Mode.
    The "Common Denominator" of the above difficulties appear to be Lightroom 2 and Camera RAW 4.5 (individually and or collectively) and now I am stuck between a rock and a hard place.
    Are any other users experiencing similar issues or have any suggestions about how I might correct or resolve these problems? ......
    I am not afraid of hearing or accepting that the "Dummy Factor" has played some part or how I may release myself from the said "Dummy Factor".....any help is welcome help.
    Adobe Technical Support seems to be ignoring me......I wonder why?
    Regards
    Bob Wallace

    Essentially you are wrapping the raw image data into a special type of layer, a "smart object". You can then revisit and fine tune the Camera Raw conversion as often as you want and take advantage of working directly on the raw data in its pre-Photoshop purity. You can also apply to this smart object layer a number of Photoshop adjustments and filters - and again redo and fine tune them as often as you wish.
    You'll find them explained in a number of recent books. I know Scott Kelby is keen on them, there are examples on Russell Brown's site, and my own book last year on B&W strongly advocated their use.
    Have a play.
    John

  • Strange colour cast in LR3 with Canon G11 RAW

    Hi all,
    I recently bought Lightroom 3 to work with the RAW output from my Canon G11. The majority of the shots want to process are taken underwater around the UK coast. I'm having an issue with colour casts which I hope someone may be able to shed some light on.
    With these underwater shots LR3 seems to import them with a very strong green colour cast, even though, when diving, I set the manual white balance at regular intervals. By comparison, Canon DPP imports the RAW files correctly (what I consider correct), and I get the same correct results with Raw Therapee, GIMP and Capture 1. PhotoShop Elements gives the same results as LR3, but I assume they both use ACR 6.1.
    I would expect Canon DPP to be correct as it is processing it's own RAW files, but as the other RAW converters match the Canon output, I get the feeling that my problem is with LR3, or possibly ACR. I've scanned both the Adobe LR forum and ACR forum, but can not see any posts where people are having similar issues to me. I did find several post's saying that LR3's support of the Canon G11 was now finished, maybe it has just been tuned for land based shots, not underwater.
    I have tried using Adobe DNG Converter, to no avail, and I have also tried all the white balance pre-sets within LR3. Even the custom white balance picker does not give sensible results, it just changes the shots to a slightly different shade of green.
    Playing around with other setting in LR3 can make slight improvements, but it's a slow, shot by shot process, and still does not produce a usable finished product, or even a reasonable starting point for fine tuning.
    I have found that I can use Canon DPP to output to TIF, which LR3 then opens correctly, but I feel that as I'm not then working with the RAW file, I'm not going to get the best out of LR3's features.
    Is there some particular setting within LR3 or ACR that I have missed ? If not, am I actually loosing detail by converting to TIF before opening LR3 ?
    I've attached example output from LR3 and DPP. Both use white balance of 'As Shot', and neither have had any processing done on them. The LR3 shot looks lees green that it does in LR3, I assume thats because I've saved it as a low res JPG.
    Thanks for any advise people can give.
    LR3 output
    DPP output

    Thanks for that answer, it shows that I may have some settings which need tweaking.
    All the LR3 settings are as standard when first loaded, playing with this bunch of shots (about 20 in all) was the first thing I ever tried in it. I wouldn't even know how to apply split toning even if I wanted to (you probably guessed by now that I'm a new user to this software). All the on land shots I've messed around with import correctly, so it's definitly only the underwater ones.
    One thing that I've just remembered, may be important, when I select shots to import in to LR3, the thumbnails look fine. It's only when the import process has finished the green colour cast appears. It's almost as if something is being applied right at the last minute.
    I haven't tried to white balance the JPEG. I assumed it wouldn't work with the RAW, it would be the same with the JPEG.
    I did process some shots using PS Elements a while ago, and don't remember any stong colour casts in that. They were from shallow fresh water rather than deeper salt water, may make a differeence. I believe the ACR plug in with PSE 8 at the time was in the 5.x range. I did manually upgrade the ACR plug in for PSE 8 to 6.1 after loading LR3. I can try backing that out and seeing if I still get the colour cast.
    Hmmm, it's looking more and more like a problem with ACR 6.1. At a guess I'd say it's not interpreting the 'as shot' information correctly, or completly ignoring it.
    I'll have a go with white balancing the JPEG when I get home. If you can do it, but I can't, it points directly with a setting on my system. I'll also have a look at uploading the RAW file somewhere.
    Cheers

  • I am using Lightroom 5.7, 64 bit with Windows 7 Professional. For no apparent reason, I now get an error message when I export a photo, say a raw image to a JPG. However, the exported image seems to be OK. But now I notice that my LR directory of folders

    I am using Lightroom 5.7, 64 bit with Windows 7 Professional. For no apparent reason, I now get an error message when I export a photo, say a raw image to a JPG. However, the exported image seems to be OK. But now I notice that my LR directory of folders in Library view does not show images correctly: If there is a folder with sub-folder(s), the folder will indicate 0 images, but the sub-folders show the proper number of images. What happened and is there a fix? I tried uninstalling Lightroom and re-installing, but problem persists.
    Here is a screen shot of the error message:
    Message was edited by: Joseph Costanza, Jr.

    See here for a solution.

  • Can't move Raw images in Lightroom 4

    Hi all,
    I've watched all of the tutorials and read all I can to get to the bottom of this to no avail. I understand that I need to use the foilders panel in the library module to move photos, my problem is that the folder module does not show any destination folders at all!
    When I import my images I create a job and place the images in a subfolder named Raw Files eg.  2013 Jobs > 075 Robert and Jess E-Shoot > Raw Files
    This way all of my images are in a folder that is job related. Occasionally, however, I will forget to change the import folder when importing the Raws, and the images for the next job will go into the Raw folder for the previous job. I'd like to be able to move the raw images to the correct folder, but in the folder panel the only path showing is the path I've imported to.
    In the case above, my 2013 Jobs file should show 75 subfolders of individual jobs, but there is only one showing. I need to be able to see the destination folder in lightroom to move the Raws to their proper home. As I can't see the destination folder I can't move any files, and I end up having to try to work it out in the operating system.
    Can anyone tell me how to get all of the subfolders to show?
    Thanks, Antony

    Create the folder here:
    Then you can move your files to it.

  • My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images

    Any ideas?

    My student has been using Lightroom 4 with Photoshop CS5 on her Mac for well over a year. Because of the difference between the Camera raw version available to her in Photoshop CS5 and the raw process in Lightroom 4, she has been exporting her raw images from Lightroom and choosing the "Render using Lightroom option when it popped up in the dialogue box. She has been doing this for over a year and a half without any problem. Today when she hit Command E no dialogue box appeared and the image just opened in Photoshop. I'm concerned that all of her Lightroom edits are not being rendered to Photoshop. Anyone have an idea as to how we can get the "Render using Lightroom" dialogue back?

  • Oversaturated RAW images in Lightroom 4

    All of a sudden, all of my RAW images are oversaturated and over contrasted in Lightroom 4.  When they are initially "loading" the photo looks great, but then when it loads the pictures it is WAY oversaturated and overcontrasted.  I have not changed any settings in Lightroom, so I am not sure what has happened.  I have attached screen shots to show it when it's loading and when it is loaded.  This is a HUGE difference.  All of my settings on the menu on the right are at 0 or whatever the original setting is in the Develop mode.  I've checked everything in the column on the right in the develop mode, settings, etc. I have checked to make sure that my Lightroom is not pending any updates and that my camera is up to date. I've looked in several forums.  From what I can see, there have been others with this issue, but I can never seem to find a resolution to fix it.  Any help would be greatly appreciated!!
    Camera: Nikon D7100 (if this matters)

    If something changed recently, it is likely one of:  you’ve recently shifted from shooting JPG to shooting RAW, a LR Preset being applied in Import, your LR defaults are different than before, your monitor profile is different, your video drivers have been updated, your video-card’s control-panel settings are different, or your monitor’s own settings are different.
    When you newly import an image are all the toning sliders still set to zero?  (i.e. Exposure, Contrast, …, Clarity, Vibrance, Saturaton)  A screenshot of the Basic panel at the top right of the Develop module would show this.
    What Profile do you have selected in the Camera Calibration area?  A screenshot of the bottom right of the Develop module would show this.
    To confirm whether your LR defaults have changed to something non-zero, you can make a virtual copy of a representative image and then click the Reset button and see if all the toning sliders return to zero in the Basic panel, and also check the Profile setting in the Camera Calibration area.
    If you want to upload that specific pumpkin image to http://www.dropbox.com/ and post a public download link to it, here, then others can load it on their systems and see what it looks like, to compare with your screenshots.
    So far the difference between the two screenshots appears to be camera-embedded JPG and default LR settings which will never be the same.  The 2nd (right) screenshot in your initial post also looks out-of-focus compared to the initial camera preview which seems odd.  Maybe things hadn’t fully-rendered, yet.

Maybe you are looking for

  • USE OF ZERO AND BLANK CELLS IN CALCS

    Hello Everybody, I'm making a new script logic that acumulates the values month by month, it means that february=januaryfebruary, march=januaryfeb+mar, etc. Everything was workin fine, until i had some values in blank in few months, in those cases th

  • About  "abstract class cannot have be instantiated"

    in java coding it means ======== abstract  class X   public X(); }======== no {} is allowed to public X or i can not write a invoke as ======== X x=new X();======== or both of them are forbidden by abstract class? why body{} is related to instantiate

  • AP1231 crashes when adding Mac to access list

    I have a AIR-AP1231G-E-K9 it is running c1200-k9w7-mx.123-8.JEC2/c1200-k9w7-mx.123-8.JEC2. I am using a Mac Access list to restrict users access to it - however when I add an address now it crashes the AP and has to be rebooted. Is there a limit to M

  • Play button no longer works

    I installed the 2014 version of CC and since then the play button (space bar) no longer works. Everything else seems to be working fine but I can't play my timeline. I can scrub through the footage but it won't play. Does anyone else have this issue

  • Why does clicking on "Preferences" (to change home page) shut down Safari?

    What can I do to prevent Safari from immediately shutting down when I click on "Preferences" in an attempt to change my home page? Any help will be greatly appreciated.