OP
dark goob
•
Contributing Member
•
Posts: 985
Re: Focussing problems with 7D
Sorry, it was busy yesterday, didn't get a chance to post any trials. I have been able to fully test and verify this issue. It does seem much easier to reproduce on a fast prime, though he provided me RAW files from the 70-200 F/4L that also exhibited these symptoms.
I set up the camera on a tripod using the cable release and 50mm F1.4 for this (note the indoor shots). The problem did occur as you will see. We'll be providing a full report to Canon tech support regarding this issue. Hopefully it's something minor they can fix with a firmware update, or just a defect isolated to certain serial ranges.















The original files are quite large so I'll avoid posting them inline here, so add the protocol prefix to the URLs and you can view them in your browser.
To post them all was 350mb even in a ZIP file, so here are just three from the sequence shown in 7d_Focus_issue06.jpg:
www.io.com/%7Ejjj/IMG_0379.JPG
www.io.com/%7Ejjj/IMG_0378.JPG
www.io.com/%7Ejjj/IMG_0377.JPG
I used JPG since most of you probably don't have the new Canon Digital Photo Professional software to read these RAW files (maybe it's a free update though, I haven't checked). Really, it would need to be RAW anyway because we're looking at AF performance which is not affected by being in RAW mode, or not.
I can post the .CR2 files of those outdoors shots (which were provided by a customer) if anyone really wants. Frankly I'm not here to "prove" anything to anyone, just hopefully illustrate what the issue is, exactly, so people can test their cameras for it in case they care to.
Just a note: I'm not out to give Canon a bad name, which is impossible -- this is a fantastic camera. This isn't about brand bias. If you actually read any of the messages I've posted in the Olympus forums too, I also posted a huge thread there when my E-3 was exhibiting AF problems. And guess what? Olympus released the 1.4 firmware for the E-3 not long after that, which resolved the issue. I'm equally critical of all brands... lol.
Anytime an issue such as this is brought to my attention then I prefer to make the issue known in case that knowledge might help anyone. If knowledge has become a crime then assuredly we are living in dark, dark times. I have no doubt Canon would prefer there to be no issues with their latest product but, if there's an issue, then consumers ought to be aware. That does not mean you should avoid buying this camera.
As a dealer I'd like to avoid selling my customers a defective product if I can avoid it. Therefore if I can provide them the OPTION to check their camera and verify that it does NOT to have this type of issue, or advise them if this issue exists whether it will affect them based on their shooting, or get in touch with Canon with as much info. as possible in order to get any issues resolved ASAP, then I will do so.
The reason I'm posting this in these forums is that hopefully someone can tell me the reason why this is happening and if there is any possible work-around, or if there is just something that we're doing wrong. Of course, I'm not so interested in people demanding my real name, social security number, insinuating there is some type of conspiracy, etc. I have a customer who is a seasoned photographer and found this problem unacceptable; does not have this problem with his 5D MkII, nor his D700, etc. I personally have never seen an issue like this on Canon (even with the 1D MkIII, I never actually saw one that had the supposed problems).
So yeah, take it or leave it. HOPEFULLY this issue does not affect many of these cameras, or is just due to seismic activity in Oregon, solar flares, or whatever.