Got a 40D that was only a couple of months old when I bought it here off FM.
Went to the motorcycle track the next day and did some shooting in Large jpg with Daylight WB (used an EF 70-200mm f/2.8L IS). I was using a 4G Kingston 133x Elite Pro CF card. A friend at the track also gave me a 4G Transcend 120x CF card to use as well (he's used it in his 1D MKIII with no issues). So, I shot my photos onto the cards, downloaded them to my portable hard drive and brought them home after the day was done. In my prior xxD and 1 series cameras, I always used Sandisk cards (usually the Ultra II), but didn't have the money to go out and get one to shoot with yet. Never had any problems with any of my Sandisk cards. However, I haven't been able to go get one as of yet (new, just to be sure everything is good to go).
Come to find out A LOT of the shots came out weird. Meaning they had either an all green cast, all blue cast, all yellow cast or even the exposure was all messed up. Almost like it didn't save to the CF card correctly/fully. Anyone ever have problems with this
Also, if you look at a lot of the photos, the top few pixel lines (and some to the left side of the image) looked "normal", like it was trying to save properly and then the cast or "change" occurs. It's really weird. I figured maybe it was just the Kingston card or something. I've had issues with that happening when I borrowed a card in my late 1D MKIIN camera, but only when I used a non-Sandisk card. I know that shouldn't matter whether I used a Sandisk or Lexar or Kingston card...but this is just my experience, so I'm documenting it.
So, I went on a modeling shoot today (3 weeks after the track shoot) (EF 50mm f/1.8 II) and used the Transcend card only. I shot some in Large jpg, some in Large RAW & Large jpg and then just Large RAW at the end.
Well, going through the photos now...I'm getting a green and blue cast again...even on the RAW photos. However, if I open up the RAW photo in PS CS3 and click the WB from "As Shot" to "Daylight" (like it was set in the camera upon shooting), it cleans it up and the shot looks great again.
What the heck could be causing this? Do you think it might be the CF card(s)? That's what I was hoping for, but now I don't know. If it's the 40D, then I want to send it in for service now since it still has warranty on it until Jan '09. However, if it's only the CF cards, then I don't want to send the body in for service and get charged for it.
I'm just afraid now to shoot in jpg any more (especially the modeling shoots) because I might miss some nice shots due to this problem.
Any help/ideas/thoughts would be greatly appreciated.
Thanks,
Mat
Edited by SouthBayPhoto_ on Apr 05, 2008 at 11:53 PM GMT
Oh and I forgot to add that some of the jpg shots from the track shoot wouldn't even open. Basically seemed corrupted.
Here are some shots of what I'm talking about. If you look at the upper edge and/or the left edge, you can see where it either started processing correctly and stopped and/or it seemed to have included parts of the previous shot on it (or the right hand side of the shot). What's funny is the shot just previous or after each one of these shots is usually okay. I didn't overexpose any of these. Most times I meter off the track and then just shoot, checking here and there, but usually I don't vary much. So the super "over exposed" ones, aren't from me...they just saved that way. Helllllppppp...
Too weird. I've never seen anything like that. Looks as if your camera is taking a trip to the camera hospital. You did say it does the same thing with two different cards, I think.
Yup....I used both the Kingston and Transcend cards on the motorcycle shoot and since I saved them to the portable hard drive, I couldn't remember which was on what card. So, I figured, since I had an issue once before with a Kingston card (not this particular card, however), it was that card.
So, this time I only used the Transcend card and it's basically the same thing, but this time even on RAW shots (didn't shoot any RAW on the motorcycles).
The only good thing is, this time I'm "saving" the shots because I shot most of them in RAW.
Plus, I also forgot to add, there were times when the camera would pause and just say BUSY when it was writing the shot to the card. And I was not shooting any bursts. I'd go to try and shoot again, say 30 seconds to 1 min later and it still showed busy.
So, I don't know if I should just call Irvine now or wait and try and buy a brand new card (where I would assume nothing is wrong with the card) and try it.
Oh and I always format the cards prior to each use in the camera, so I don't think that's it either.
I dunno if the card had an issue, it would come out as either static, or non-displayable, I don't think it would change the exposure or color cast of a shot. That looks like a capture problem to me.
That's what I was afraid of and thinking as well, AhrenL.
There were some shots that you couldn't open the jpg files or display them at all.
I just find it hard to believe that testing with the two cards I have and a good friend used the one card in his MKIII and MKIIN before with no troubles, that it would only be the cards.
well, I'm probably going to call Canon tomorrow morning and find out what the deal is. Hopefully it won't take years for them to fix it.
If something is under warranty, do you just have to pay the shipping to them and that's it? I'd hate to send it in and then find out they are going to charge me an arm and a leg for somethin' else. Not that I really have a choice at this point, I guess.
Gochugogi wrote:
I'd do a total reset, PRAM flush and firmware update before sending to service. Sometimes that fixes haywire stuff.
Well, when I received the camera, I used all the resets on it to put everything back to "stock" so to speak. Only because I didn't know how the person set it up prior to it getting to me.
So, I think I did that part already (total reset). However, I don't know what a PRAM flush is....can you please elaborate?
I can check to see if it has the latest firmware, but I believe it does. However, I guess it won't hurt to reupload the latest again just in case.
I appreciate the info. I'll try that first and see if it corrects the situation, but if you could let me know on the PRAM flush, it would be truly appreciated.
