cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

5d mk III RAW issue

andreicraciun
Contributor

DPP_output_from_RAW.JPGLR5_output_from_RAW.jpg

 

Hey, i'm experiencing issues with the RAW files. I think there might be a sensor problem because i tested the original file on another computer and it's the same. Attached here, u have the same raw file exported in Digital camera Proffesional and Lightroom 5.

I'm a professional photographer and every now and then, i get this kind of errors. I usually shoot RAW+JPEG low and the weird thing is that the jpg file out of the camera does not contain any errors, only the RAW file does.

I tested everithing, from different batteries, different cards, different lenses, with/without battery grip and that problem still persists. Every 200-300-400 images one raw file is corrupt.

I cannot afford loosing images. Can somebody tell me if this is a random error everybody gets or is it a service issue and i should get my camera checked right away?

Thanks.

28 REPLIES 28

cicopo
Elite

That's usually a card issue. If the jpg is OK it can't be the sensor & as far as I know the camera converts the RAW data to the jpg

"A skill is developed through constant practice with a passion to improve, not bought."

Exactly. The RAW is converted as far as i know from the RAW file inside the camera. That's why i cannot explain myself why i keep getting these errors for the RAW files.

Unfortunatelly, i tested around 4-5 cards (all SD) and i keep getting errrors like this. Not often, but enough to be somehow worried. I have no CF card atm. Probably i will buy one and see if the problem persists.

Still, if someone has or had the same problem, i would appreciate if he would tell me about it.

Thanks.

If it fails the same way on multiple cards, it almost has to be in the camera. But my bet is that it's a bad contact in the SD card slot, rather than a sensor failure. If it fails on a CF card as well (which would disprove that theory), then my fallback guess is a flaky connection between the sensor and the processor. When the failure is that geometrically precise, it's hard to see it being in the sensor itself.

 

But it doesn't really matter. If the problem is in the camera, it's got to go to Jamesburg (or to the geographically correct venue for your locale). Let them swap components until the problem goes away.

Bob
Philadelphia, Pennsylvania USA

andreicraciun
Contributor
Aha, indeed, all failures are geometric, i uploaded just one example but most of the errors are like this, though they cover not allways the same area.
I will defenetly give it a try with a CF card, if only they where not so exepnsive 🙂 but i will invest in one just to exclude one possible issue.
Thanks for the answer.

TCampbell
Elite
Elite

I own the same camera and have never had such an error.  Usually this sort of problem indicates a flakey card.

 

If your JPEGs come out fine then it cannot be a sensor issue.  The camera always captures a "RAW" image from the sensor... and then performs an in-camera conversion to JPEG if you've opted for a JPEG output (in other words every image starts out as RAW).  If the sensor was a problem then it wouldn't be possible to get a clean JPEG.

 

Also, when sensors fail (and sometimes they do) it's usually 'columns' that go bad rather than blocks.

 

However, RAW files are big (usually about 25 MB each) and JPEGs are usually quite small (maybe around 5MB for full-resolution and minimal compression).  If there's a card problem then it is more likely to hit a RAW file than a JPEG file (probably about 5 times more likely -- because most of the space on the storage device is occupied by RAW files as compared to JPEG files.)

 

Format your cards in-camera and use the "low level" checkbox (toggle that on).  This should cause the camera to check each block and hopefully identify bad blocks and map them out.  

 

Make sure you mark the cards that have done this to you -- to determine if it's more likely sticking to just one card or if it really can happen to "any" card you own.   If I have a card going bad, then it's probably not worth the risk to hang on to it -- that card gets chucked and swapped for a new card.

 

I'm fairly fussy about which cards I buy and even which stores or online retailers I use -- memory cards are easily faked (they throw any sticker on it) so you want to make sure that if you're paying for a top-end card that you are actually getting a top-end card.

 

Tim Campbell
5D III, 5D IV, 60Da

DuaneIndeed
Contributor

This problem started for me this morning AFTER I downloaded the new versions of DPP and EOS Utility from the Canon USA site.   This screen shot shows images that are 2 years old, and were just fine in DPP and Lightroom before this morning!!   You can see that the thumbnails are fine, but the corruption shows up when I click into the image.   In Lightroom, even the thumbnails look corrupted.   Not all raw files have the problem, but many do.   To me, this indicates a problem in the Canon RAW SW running on my desktop.  The SW is in common with DPP and Adobe LR.

 

Capture.JPG

andreicraciun
Contributor
Well this is indeed weird. Allthough, in my situation, i've tested the raw files on another computer from a friend which has DPP not installed, and the problem was still present.
You got me thinking here.
I will try to install an older version of DPP, maby this will fix it. Allthough, i don't understand why lightroom shows the error aswell. I will keep you informed about the results the next days.

andreicraciun
Contributor
Ah, what do you mean by Canon RAW SW? 🙂 don't know the meaning 🙂

SW = software (I think)

"A skill is developed through constant practice with a passion to improve, not bought."
Announcements