RAW files look corrupted with color streaking during import

During import in Lightroom about 25% of my files look corrupted (with color streaks, etc.). The RAW images upload perfectly in iPhoto on the same computer but for some reason will become corrupted in Lightroom. I am able to delete the corrupted images in the LR Library and reload them with about a 50% success rate. I've tried different memory cards, cf importers, etc. Only an issue in LR. Sometimes they export with the streaking and other times they export perfectly fine. Even if they export fine it makes it impossible to edit in LR. Below is an example of how the image appears. Any answers?

Raw files have a camera-embedded JPG. 
I would guess the files are corrupt, LR is showing you this corruption, while other programs are only interpreting the JPG and hiding the corruption.
Can you upload one of these photos that iPhoto shows as ok, while LR shows corruption?  Upload one to www.dropbox.com <http://www.dropbox.com>  and post a public download link, here.

Similar Messages

  • I am having issues when I shoot raw + jpeg. Raw files seem corrupt!!

    I am having issues when I shoot raw + jpeg.  It seems the raw files get corrupted.  I have shot raw without an issue.  It is only when I shoot raw + jpeg.  The raw files will not show in Photoshop elements.  I installed the Canon software and was able to see all the raw files; however, I noticed that when I tried to view some full screen they would not show.  I also noticed that these raw files look block-ish.  They appear more digital looking.   Is there a specail card needed to shoot raw + jpeg?  I formatted the ones that I have prior to using them.
    Solved!
    Go to Solution.

    While it could certainly be a card-reader problem, data corruption of any kind can be any of the following:
    1) the card
    2) the cable (if used)
    3) the card reader (if used)
    4) the computer RAM,
    5) thecomputer hard drive (or SSD)
    A failure of any one of the above will result in corrupted images when viewed.  Since it seems to be RAW file related, as they are signifantly larger than JPGs, it's likely anything but the card reader or cable. 
    The only way to 'beat it' is eliminate each of the possibilities, starting with the easiest/cheapest fix. 
    1) Use the cable.  If that solves the problem, replace the card reader.
    2) Use a different card.  If that solves it, toss the old card.
    3) If multiple sticks of internal computer RAM, swap them.  If that fixes it, or, the problem 'moves' to other images, replace the RAM.  It could be only 1 of 2 sticks bad, though, so use only 1 of the old sticks for a while to see if the problem recurs.
    4) If you have multiple hard drives in your computer, or an external one, use that to store the photos for a while.  If the problems go away, it's the drive.  Note that hard drive failures typically start slowly and increase gradually.  On occassion, though, your computer won't boot and it's all over.  If you are down to thinking it's the hard drive, it's time to get a good backup...NOW! 
    For what it's worth, I had a similar problem with corrupted photos.  Both RAW and JPGs were affected.  But as the problems were after having loaded and initially viewed them on my HD, I knew it was a computer problem.  It dogged me for a couple of weeks.  I even played swap the memory sticks, pull one out and run on one only, swap the one for the other (running on one), and it STILL kept happening.  I finally gave up and replaced both sticks of RAM.  That solved the problem.  So much for lifetime warranty from Hong Kong.  A very well regarded brand of RAM, no less.  My SSD drive was the next one on the list, it the new RAM didn't solve it.

  • Open the same raw file in PS5 with two different White Balance settings

    I'm trying to open the same Raw File in PS5 with two different White Balance settings.  One setting "as shot" the other in "daylight", then blend them.  The tutorial I'm watching says to "stack" the images.  The tutorial shows one White Balance setting as the "Background" layer and the other setting as "Layer 1".  I don't know how to do this and the tutorial is not specific.  Can anyone either point me to a step by step instruction or offer some assistance?

    Also look at the "Snapshots" feature of Camera Raw itself.  It allows you non-destructively to keep multiple sets of settings for a single raw file.
    Learning about it far exceeds the scope of what can be done in this particular forum.  I would recommend this book as essential reading:
    http://www.amazon.com/Real-World-Camera-Adobe-Photoshop/dp/0321713095/ref=sr_1_1?ie=UTF8&q id=1313502199&sr=8-1
    Additionally, there's a dedicated Adobe Camera Raw forum:
    http://forums.adobe.com/community/cameraraw
    Wo Tai Lao Le
    我太老了

  • Why do Sony DSC-RX100M3 raw files look strange in PE9 when flash has been used in the shot?

    I have just bought a Sony DSC-RX100M3 camera and use it to shoot raw + jpeg.  I want to use the raw files in my Photoshop Elements 9, which has the Camera Raw plug-in version 6.5.0.216 installed. I have downloaded the Adobe DNG converter version 8.7.1.311 so I can import my Sony raw files into PE 9 as they cannot be used directly. Most of the time these raw files look OK, but when I use the flash on my camera and then look at the raw files in PE9 they look far more pink than the corresponding jpeg files. The jpeg files look more or less as I remember the scene when I shot the picture.
    When I look at the same raw and jpeg files in Sony's own Image Data Converter software (version 4.2.04.17270) the raw and jpeg files look very similar to one another, and there is no pink colour cast in the raw file.
    What am I doing wrong in Photoshop Elements? I though the DNG converter keeps all the information from the original raw file and makes no changes to it, so why does the raw file look so different when flash has been used?
    Thanks for any help you can give!
    AVM

    Looking at the pictures of the camera online, I'd say there is no lens shade--a device to keep light from the sides from causing lens flare--and the camera lens, itself, was just too far extended and there was a lens shadow.  You probably can't use the flash that close up and should back off and zoom in further.  Experimenting would give you a sense of what situations will have a shadow of the lens or not.
    Your ACR plug-in is old enough not use have Process Version 2012, yet, only 2010 and 2003 so Adobe didn't have the idea to put the selector down next to the camera profile. The toning options are better with Process 2012 so that would be a reason to upgrade, but I am not sure that the Camera Neutral profile in PSE9 would be different than PSE13.  If Adobe changed the camera profiles then people's pictures would look different once they upgraded to a new version and that's not something that's supposed to happen.
    You can certainly download the PSE13 trial and see if things look any different, but they may not:  Download a free trial or buy Adobe products | Adobe downloads   There would be newer minimum OS version requirements for the newer versions of Adobe software so check those out before trying to install, unless you're on Windows 7+ or OSX 10.8+ then it should be fine.
    One more thing, the White-Balance tint is set to +10 by the camera:
    This As Shot WB is more magenta and even when using the Adobe Standard profile, moving the Tint down to +0 makes things a little more green like your camera JPG.  So there is more than just changing the camera profile that you can do:

  • My RAW files look washed out jpegs are OK

    My RAW files look washed out, in camera I introduced warm colours by setting it on cloudy and set to vivid. They look great in other programs, how do I retain the original colors?

    Buddy, the issue is that Photoshop Camera Raw / Bridge don't use the parameters you set in-camera at all.  It may seem odd that it doesn't, but that's the way it works. 
    The idea is that these software tools give you full control over literally hundreds of factors that go into your raw conversions, and trying to emulate the presets on the camera just doesn't make sense.
    You need to save new Camera Raw Defaults to deliver color you like in new exposures you haven't opened before.  Check especially the Camera Profile setting in the Camera Calibration tab in Camera Raw.  Adobe does provide some options that will get you close to what the camera does, then you can tweak the settings further.
    For what it's worth, it's not wrong to want the color to match, especially if you like the color the camera delivers.  I've created Camera Raw Defaults for my own cameras that provide a very good match between the in-camera color and what a new exposure looks like when first opened in Camera Raw...  I don't always leave it that way, though. 
    -Noel

  • Why are my RAW files looking like infrared?

    Hi All,
    I use Aperture frequently for my editing - just recently had a ridiculous problem that results in my RAW files looking infrared.
    Have I enabled only a red channel or something?? Please help!  See pic!

    Wow, what a silly oversight - I knew I had had an update to do, but hadnt bothered with it yet. Thanks a bunch Ernie, I should have thought of us.
    Much appreciated.

  • I ran MacKeeper and demo'd my wife's iPhoto archive bigtime: RAW files appear corrupted and lotsa pix w/no thumbnails or "!" marks instead. Help!

    I ran MacKeeper and demo'd my wife's iPhoto archive bigtime: RAW files appear corrupted and lotsa pix w/no thumbnails or "!" marks instead. Help!

    Should I take it that recco'd means 'recommended'? Still have no idea what demo'd means in the context you use. I've often seem it as an abbreviation for 'demonstrate' but that makes no sense. The problem with idiosyncratic abbreviations is that other people don't understand them.
    Option 1
    Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
    If that fails:
    Option 2
    Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
    Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. .
    Regards
    TD

  • 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

  • HT1338 My fuji x100s has RAW file compatibility issue with OS 10.8.2

    My fuji x100s has RAW file compatibility issue with OS 10.8.2, my iphoto11 cannot recognise the file format.  Anyone know of this issue too? Appreciate if anyone can offer some helps.  Thanks

    Correct.  The Fuji X-100s is not currently supported by iPhoto or Aperture (or the RAW converter in OS X itself).  You can submit feedback via iPhoto and request this.

  • RAW files being corrupted by Aperture

    Some of my RAW files stored in Aperture come in clean but eventually show up as corrupt. Specifically, a rectangular portion of the image will become banded with colors that don't belong there.
    Sometimes I see this happen to a file just after some simple operation--say, adding a keyword. Whats' going on?
    Here's an example.
    http://lyonsimaging.smugmug.com/gallery/3547082

    Just to add my own recent image corruption problem. I was getting a pattern on some images, almost like heavy rain in vertical streaks. I thought it was an Aperture bug at first as it only appeared in Aperture. However, I could transfer images to other apps, and the fault had gone. The fault was only occurring when using the Highlight and Shadow tool.
    Thanks to a suggestion here, I finally found it was caused by my graphics card. I upgraded from my original Nvidia 5200FX 64MB, to a Radeon 9600XT 256MB. I was able to refit my old card, and the faulty was fixed. Turned out that the Radeon was overheating (these appear a lot in other forums, and an upgrade to the cooling is recommended). I have now refitted it with a Zalman copper cooler, and heat sinks to all the chips, and the problem seems to be cured.
    It does seem strange that yours are corrupted back to the master though.

  • Raw file rendering problems with Canon EOS 5D in Aperture 3

    Since upgrading to Aperture 3, I have had serious problems with the rendering of Canon EOS 5D (not Mark II/III) RAW files. With Aperture 2, both the preview and full-sized images looked basically the same as the original images as displayed on the camera's display, without any adjustments.
    With Aperture 3, each preview images initially look fine after import, but when Aperture re-renders it from the RAW file (e.g. when displaying the full-size image), the colors are drastically intensified, and the hue is shifted generally towards green/blue. I've checked the RAW Fine Tuning, and it is set to the defaults. If I turn the default RAW Fine Tuning settings all the way down, the image is still not at all like the preview from the camera - it becomes much darker and stays too blue/green, with washed-out colors.
    A friend with a Canon EOS 5D MkII also recently upgraded her Mac from Aperture 2 to 3, and hasn't experienced any problems. We've tried importing RAW files from my (non-MkII) camera to her Mac (with the default RAW Fine Tuning settings), and get the same results as with my own Mac (i.e. strange colors), so the problem seems to be related to the camera model.
    I've also noticed that scanned greyscale tiff images (including images that were originally imported under Aperture 2) are changed when first displayed by Aperture 3 - they become darker and more contrasty, with lots of information lost in the shadow areas.
    I've also tried removing Aperture preferences, Aperture itself, and re-installing from download, with no change in the problem. (Aperture is the current latest version, 3.3.2.)
    Has anyone experienced similar problems?

    I'm having the same problem.
    iMac running Mac OS X Lion 10.7.4 and Aperture 3.3.2.  Workflow is importing through Canon's DPP and then using referenced images in Aperture.  The images look great in LR4, or Canon's DPP but are flat and dingy in Aperture.
    There's a free preset that goes part way to fixing it at http://theapertureblog.com/2011/02/10/my-aperture-workflow-for-working-with-cano n-5d-mark-ii-files/
    but as good as this fix is, it doesn't quite do the trick. [not being a hater, and not saying I can do better]
    I just got back from shoooting 1,500 images with a 5DMii and a T2i using Canon 24-105L IS, 70-200 2.8L, 50 1.8 and a Sigma 120-400 and the T2i images are not just better, they're in a different league.
    I've tried shooting in Faithful, Neutral and also toggling these presets in different ways and still can't get Aperture to match what I see on the camera's screen or in other Apps.  I love the interface and DB of Aperture, but what's the point of using it if it doesn't produce and awesome image in the end?

  • D600 RAW files look different that D300 raw files

    Please help me understand what's going on and more importantly, how to fix it.
    RAW files from my D300 and my D600 look completely different. These are both NEF files, imported to Lightroom 4.2 using exactly the same import preset. I did NOTHING to either file, except that the D300 one was at 1/160 second and the D600 one was at 1/200 second, so I changed exposure on the D300 one by 1/3 stop so they would match. What I did was to shoot the D300 picture, then carefully changed the lens over to the D600 without moving anything, changed the D600 to DX mode to match the field of view and shot the same picture. The files should be essentially identical.
    [b]This is from the D300:[/b]
    [b]This is from the D600:[/b]
    You will notice that the saturation on the D600 image is much higher. And it's much more yellow. The pictures were shot 2 minutes apart, from the same spot. Same lens, same camera settings.
    First thing I did was to change the color temperature and tint to match: from  4150/+6 to 4200/+2. There was no visible change (I'm looking at them in compare mode in Lightroom on a calibrated monitor).
    Next, I tried to change the D600 image to match the D300 one. I had to make substantial changes to both color balance and saturation of various colors, as well as contrast and black levels to get close. I'd give you absolute numbers but it varies from image to image. In this case, I had to drop the color temperature to 3500, for instance. The easiest way to do this was to use the white balance eyedropper on a grey area in the road.
    I'm wondering if this is related to how LR handles the D600 NEF files. LR 4.2 says the D600 algorithm is 'preliminary'. Could this be part of it?
    Anyone else here have a D600 and noticed the same thing?
    Message title was edited by: Brett N

    I'm not really good at using the right technical terms. Let me go back to basics.
    Adobe came out with Lightroom 4.2 which has (preliminary) support for the D600. I installed it. I put the memory card from the camera into the card reader and Lightroom popped up because that's what I had set for the default for uploading photos. I told it which folder to store the image in (J:photos/2012-10/2012-10-05) and where to put a second copy (D:/px/lightroom import copies). Then I told LR to "save Current Settings as New Preset..." and I named it "D600 imports". Then I clicked "Import".
    When I looked at the files afterwards in Lightroom, the sliders were all at zero except for the ones I noted before. I don't know why Lightroom chose 25 for the sharpening, but it did. Coincidentally, that's the same number it chooses for my D300 imports. I also don't know why it chose a color temp of 4200 and a tint of +4 (I was shooting on auto white balance).
    Then I plugged in the card from the D300. I decided not to touch the preset (which still said "D600 imports") and I clicked "Import". The files went to the same folders and presumably, had the same sharpening and other slider levels applied.
    Now when I look at the camera calibration in the develop module, under profile it says "Adobe Standard" on the D300 images and "Beta" on the D600 images, so Lightroom somehow knows which camera I used and sets itself accordingly.
    At no time did my fingers ever leave my hand, and I did not modify, click on or even breathe on any of the Lightroom default settings. FWIW, my programming days are 35 years behind me and I'm a total non-tekkie user now. I wouldn't know how to 'hack' the D300 files if my life depended on it.
    I know that conditions could have changed in the 98 seconds between the D600 shot and the D300 shot. Trust me when I say they didn't.
    Regarding Noise Reduction: as far as I know, there are only two user accessible settings in the cameras: "Long Exposure Noise Reduction" and "High ISO Noise Reduction". Generally I have both of those on... but since these shots were at 1/200 sec and ISO 400, they wouldn't have kicked in anyway.
    For WB, I used exactly the same spot on the road in both images. But you're right, I should use a grey target and I will next time.
    To make the two pictures match as best I could tell onscreen (I changed the D600 image to match the D300 one), I had to change the temp from 4200 to 3500, the tint from +4 to +18, the exposure to -.33, shadows to -48, blacks to -19 (these are huge changes) and it still didn't look as good as the D300 image. It was 'harder' or 'crisper'. There was no mood, no softness to it. It's like looking at a "vivid" Jpeg vs. a "Standard" Jpeg, or a cooked HDR, if that makes any sense.
    This isn't so much a complaint as a request for understanding, so that I know when I bring up an image, how to fix it. I shot a landscape and blew it up onscreen to 200%. I could see every leaf, every twig, every shadow's hard edge. That's not a bad thing, that's amazing: I just want to be able to control it.
    Glenn

  • LR5.2 Destroys raw-files if working with network drives

    I have a serious bug with LR5.2: It destroys my raw files CR2 (Canon ESO 60d) if I work with my local network drive. All my pictures are stored on this network drive. If I try to import from sd card or local drive new pictures and copy/move them via import or synchornize to my network drive the files are corrupted. I also can't open them with other sw-programms like DPP from Canon. The original files on the sd card are okay. Even if I copy the files via explorer to the network drive I can open them with for ex. DPP, but after I imported them into LR5.2 the files are corrupted and I can't open them with DPP again.

    LeeScoresby wrote:
    I have a serious bug with LR5.2: It destroys my raw files CR2.
    Lr doesn't write CR2 files, except if moving/copying, and then only via call to operating system. If your raw files are going bad, you probably have a system/hardware problem.

  • Sony a77 raw files look noisy/grainy when opened on cs6?

    HI
    i'm having problems with my images looking quite harsh when opening the raw files, this didn't happen on the trial version, i've only just got the cs6 from adobe so is there a setting i need to change?
    thanks Andy

    You misinterpreted me.  I meant that without seeing what you're seeing it's hard to provide accurate help, and that answers would be more like "shots in the dark".
    Can you please post a photograph (or small crop from one)?  Perhaps even a link to a representative raw file, with which someone else could try and reproduce what you're seeing.
    -Noel

  • Olympus EM-1 raw files look flat in LR 5.3 RC

    Raw (ORF) files from the OM-D EM-1 look much flatter in 5.3RC than with the Olympus Viewer software.  I'm having to add considerable exposure and contrast adjustments to give good results.  Is the support for the EM-1 optimized in the Release Candidate?
    A second question:  Why are there no lens profiles for micro four thirds lenses?  I'm having to manually correct vignetting.

    One approach is to stop shooting JPGs with your camera and concentrate on getting the look you want from your raw files in LR.  
    It could also be that LR isn’t able to display your images properly due to an incorrectly calibrated monitor.  Are you using hardware calibration?
    Many micro-four-thirds cameras have always-on profiles built into LR, so you won’t see them listed.  This is due to Adobe needing to agree to non-disclosure agreements with some camera manufacturers for help in profiling their camera lenses and not being able to show the images raw from the camera, and not even being able to say whether a particular camera has a built-in profile or not. 
    You can see the distortion of the original using a program like RawDigger:
    http://www.rawdigger.com/
    (click on the red version number at the top download)

Maybe you are looking for

  • Sharing calenders on one computer

    My wife and I share a mac via Fast User Switching where I am the administrator. However, there doesn't appear a way for us to share our iCal information. We don't need to be able to write to the shared calenders (however, that would be nice). Is ther

  • Creating and Setting up web services for both inbound and outbound comms

    Hi I would like to know the process of setting up inbound and outbound web services using Siebel - is there a tech note /bookshelf article that can guide me through to setting up a 'new/custom' web service. I have read up on bookshelf that both busin

  • What does the bit depth symbol mean (*, #,..)?

    In the title bar of the image in PS (CS3 on Vista 32b, in my case) it is indicated what "mode" the picture is in (Image>Mode), eg for an RGB picture with 16 bit color depth it says "[file name] @ [scaling] (RGB/16)". The bit depth can be followed by

  • Audio from one clip plays in preview, not on burned DVD

    Have just completed burning a DVD of a 23-minute movie. Everything works fine except that the audio associated with one clip in the movie is almost non-existent. If I turn up the volume when playing the burned DVD through my DVD player/television, th

  • Sales order proposal dates

    Hi Gurus, Sales order dates proposals are showing tommorrows even though i have given 10 days in house production time and first date in the sales order line item showing todays date. So could you tell me where exactly these dates are driving from? A