5Diii pink picture problem

[thatcherk1]

Good to know I'm not alone. I've not returned mine yet. I kinda wanna wait to see if a lot of others have the problem and it's a firmware problem, or universal problem. I hate having to return things.

I was doing some tests and got it to mess up the image for me some of the time. If I turn the camera on quickly and take a shot, or if it turns itself off on it's own and I wake it up with the shutter and take a shot really quick, I sometimes get that problem with pink images. It's always been just the first shot, and it's only when I take a shot really quickly after turning on the camera, and even then it's only sometimes when I do that. One time it gave me a weird "predator" (the movie) effect where everything looked posterized. I use Transcend CF card and an eye-fi x2 pro card. I can't remember for sure, but I think it still did it when I took the eye-fi card out and only shot raw to CF, but I'm not entirely sure. There was a string of a few minutes where I could get it to do it every time. Now I can't get it to do it. If I recall, it might have been sitting in the sun and was warm when I got it to shoot the pink shot. Again, not entirely sure though.

I'll keep testing. Maybe you can look at your pink shots and see if they were the first shot when you turned the camera on.

Oh and to clarify, the problem showed up on the camera screen, and on the CF raw file, and the SD jpg file. And it showed up in Lightroom4, and in DPP.

I have a feeling it's that the camera will sometimes release the shutter to take a picture before the processor is fully ready to process the image.

 

[suburbia]

must be a hardware / firmware issue, as I said before I saw the exact same symptoms when i copied all my picture files from an old drive to a disk array on a cheap new RAID controller (possibly hardware or driver related)

 

[bakker]

I also have a little problem, see attachment..

Didn't notice it on the LCD screen and it appeared when I zoomed in to a 100% in Adobe Bridge. After that it also appeared on the thumbnail in Bridge. I'm hoping this is just a PC / software issue and will be resolved with a new Camera Raw update?

Edit: No problems with the rest of the 500 shots I took. My CF card is only 4 GB and pretty old.

That's pretty much how some of my photos looked like when trying to import into Aperture/Lightroom 4.
No issues with jpegs from the MkIII, and no issues with RAWs from a MkII already on the card.
Guess we await a few fixes, and both LR and Aperture, Bridge to handle MkIII files

Ok! Good to know. I'll shoot RAW + JPEG from now on until the software gets an update.

 

[steins76]

Did a few more test today and was able to replicate the error. Please note that these were showing in the LCD screen/preview as is. When downloaded to my PC, both the RAW and JPG files are showing these images as is as well.

The first 2 images were taken one after the other... both came our REALLY bad!!!

The 3rd image were taken in burst mode too but only the first one had that black line across the pic.

The 4th image were taken in burst mode too but only the first one had that black line with the pink effect.

 

[davidpeter]

Try with JPEG on both cards, but as far as I'm concerned, that's a camera error rather than post processing or card failure. (Same glitches on both card, both in Raw AND JPEG is much more than coincidence.)

There are just too many "issues" like this with the new 5D with picture quality and AF too. I hope Canon fixes them soon with a new firmware. Although I don't really understand, why the stuff wasn't tested properly, if they were sitting on them for so long.

 

[Artstar]

There are just too many "issues" like this with the new 5D with picture quality and AF too. I hope Canon fixes them soon with a new firmware. Although I don't really understand, why the stuff wasn't tested properly, if they were sitting on them for so long.

This is exactly why I'm never an early adopter and prefer to leave a product in the market for a year or so before I decide to go shopping.

As an engineer, I can say that engineers are too close to their own product to find ways to break it. What the manufacturer should do is hand a bunch of them out to the average Joe so that they can give them a good workout and see how they fare in field testing. Problem with that though is, can you just hand them out to a bunch of average Joes and trust them with keeping it a secret when it's not due for release yet? I think not.

It's a catch 22. If you want to be an early adopter, be prepared to become an in-field tester by proxy.

 

[marekjoz]

There are just too many "issues" like this with the new 5D with picture quality and AF too. I hope Canon fixes them soon with a new firmware. Although I don't really understand, why the stuff wasn't tested properly, if they were sitting on them for so long.

This is exactly why I'm never an early adopter and prefer to leave a product in the market for a year or so before I decide to go shopping.

As an engineer, I can say that engineers are too close to their own product to find ways to break it. What the manufacturer should do is hand a bunch of them out to the average Joe so that they can give them a good workout and see how they fare in field testing. Problem with that though is, can you just hand them out to a bunch of average Joes and trust them with keeping it a secret when it's not due for release yet? I think not.

It's a catch 22. If you want to be an early adopter, be prepared to become an in-field tester by proxy.

And the hope is that this may be fixed by firmware. I can imagine as well some worse scenario.

 

[marekjoz]

Did a few more test today and was able to replicate the error.
(...)

How did you replicate it? In which exactly circumstaces does it occur?

 

[steins76]

Hi marekjoz,

It doesnt always happen but I was able to replicate it by letting the camera power down on its own (ie auto off), once it is off, I point at a subject (a building) then quickly take a few shots. Some days I can't replicate the error at all.

Anyway, I've submitted the photos to Canon and they have been on contact with me. They think it's a faulty processor so either gonna get the camera fixed or get a replacement camera.

Cheers.

Did a few more test today and was able to replicate the error.
(...)

How did you replicate it? In which exactly circumstaces does it occur?

 

[nikkito]

Not a bad idea.

Maybe the camera was in instagram mode. I'll have to check that. Didn't know the 5D could do instagram effects in-camera. What a great deal!

Instagram Mode. hahahahaha ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D

 

[nikkito]

Hi marekjoz,

It doesnt always happen but I was able to replicate it by letting the camera power down on its own (ie auto off), once it is off, I point at a subject (a building) then quickly take a few shots. Some days I can't replicate the error at all.

Anyway, I've submitted the photos to Canon and they have been on contact with me. They think it's a faulty processor so either gonna get the camera fixed or get a replacement camera.

Cheers.

Did a few more test today and was able to replicate the error.
(...)

How did you replicate it? In which exactly circumstaces does it occur?

they should give u a new one!

 

[marekjoz]

Hi marekjoz,

It doesnt always happen but I was able to replicate it by letting the camera power down on its own (ie auto off), once it is off, I point at a subject (a building) then quickly take a few shots. Some days I can't replicate the error at all.

Anyway, I've submitted the photos to Canon and they have been on contact with me. They think it's a faulty processor so either gonna get the camera fixed or get a replacement camera.

Cheers.

Did a few more test today and was able to replicate the error.
(...)

How did you replicate it? In which exactly circumstaces does it occur?

Thanks for the info.
I'm looking for upgrade from 5d2 and simply am curious if that's:
1. particular parts broken case (processor, sensor, power etc.)
2. firmware issue
3. invalid circuits/parts/sensor design.

Since I really hope to enjoy new 5d3 this year, I also hope it's not the case 3.

 

[iangrantphoto]

Hi guys, same thing happening to me. I'm pretty sure I'm only seeing it when like the other poster said- quick turn-on and shoot. Far too many pinkies today though in today's batch, kind of alarming really...

 

[ishdakuteb]

got the same problem, pink image, in last saturday while i was shooting (just one image for the entire night). i am not sure what happen inside the camera but apparently new firmware does not completely fix this problem. however, here is the summary of my setting (reason to give out this summary is that canon can limit the area to trace the problem. i guess aperture and shutter speed might not be a player in this problem, so they both will not in this list):

1. manual mode, and
2. ai servo, and
3. high iso (25,600)

anyways, even though i got a pink image, i am still happy and love my new canon 5d mark III which i bought from adorama ebay the other day and here is what i should say:

KUDO TO CANON'S AUTO FOCUS NEW DESIGNS (VERY VERY EXCELLENT).

 

[Deleted member 7828]

EDIT: Nevermind, I figured out what happened. Sounds like the lighting was the issue and not the camera...so weird because I've NEVER seen it before...(but that's a relief)

original post below
_______________________

Played with a 5D3 in the store today and noticed something very weird...just wondering if 5D3 owners have run across this one:

Shooting in fluorescent lighting (what the store had), seemed to occur at higher ISOs (3200+) there was a weird yellowish cast across over part of the photo. It was usually across the bottom ~1/4 but it's occasionally in other parts of the photo as well. Very odd...was wondering if it was the white balance or something...even in RAW can't seem to fix the color cast since it's only in 1/4 to 1/3 of the pic... maybe it's isolated to the store model or something, but I've NEVER seen this before on either the T2i or my 60D (or any other camera I've shot with)