p.72 #1 · ['NEW Fix' UPDATE!] - MkIII AF still broken
lermite,
I gave up on the camera a while ago and trade it in for a 1DsMkIII. After months of fighting, Canon agreed to take it back and hopefully it went into a deep pit somewhere.
p.72 #2 · ['NEW Fix' UPDATE!] - MkIII AF still broken
Lermite, I could not tell from your response if you specifically tried changing CFIII-4 to 1 (disregarding AF point expansion). On my body, this causes the constant focus hunting with static subjects to almost completely cease (at least with the lenses I have tried). I can still get it to hunt from time to time, but it is quite a significant improvement.
I only have experienced with one sample of this camera, so I don't know if mine is "typical" or not...
p.72 #3 · ['NEW Fix' UPDATE!] - MkIII AF still broken
garyvot, I had set CFIII-4 all the time to 1, tracking priority (seemed more logical for my type of shooting). I didn't specifically test if setting it to 0 changes something.
p.72 #4 · ['NEW Fix' UPDATE!] - MkIII AF still broken
Interestede to see what the new firmware has done for some of the main posters here, if any have tried it, esp those shooting sports or with focus plane issues.
p.72 #5 · ['NEW Fix' UPDATE!] - MkIII AF still broken
New firmware did nothing for my camera, although I suppose it is possible (based upon recent flaky results with the 24-70) that it made it worse. I hadn't thought of that...
p.72 #7 · ['NEW Fix' UPDATE!] - MkIII AF still broken
gfiksel wrote:
It's probably totally wrong, but could it be because when the camera starts off from an unfocussed state each AF sensor receives information from all over the frame and not only from where the sensor is pointed at? Some sort of "phase mixing" occurs when strong patterns outside of the sensor area prevail and affect the camera's decision where to focus.
A seemingly plausible explanation except that the subject was already in focus in some cases and the camera AI Servo decided to look elsewhere. I was tracking accurately and so there was no justification for that camera behaviour.
The new cameras have a larger sensor for extreme defocus situations but as it homes in on the subject the designated standard sensor is supposed to take over and finish the job. Therefore even a massively defocused subject should either be found eventually by the designated sensor or else not found at all.
If the problem is not with the AF or sensor hardware then I am beginning to suspect there is a flaw in the Digic III computer. I recall that Intel Pentiums had a flaw at one stage that produced incorrect results in some calculations, and I guess the Digic III could be doing the same sort of thing no matter how well Canon double-check the AF program code. The Digic III is common to all of the recent camera models but not every camera uses every feature.
p.72 #10 · ['NEW Fix' UPDATE!] - MkIII AF still broken
Jeff wrote:
New firmware did nothing for my camera, although I suppose it is possible (based upon recent flaky results with the 24-70) that it made it worse. I hadn't thought of that...
Firmware 1.2.3. made all the difference in the world in my blue dot. I went from not trusting the MKIII to using it for everything. I may be in the minority, but it really changed how my MKIII works....for the better!
p.72 #11 · ['NEW Fix' UPDATE!] - MkIII AF still broken
Well, for all of you that have kept up: I sent a second letter to Canon's president on Saturday, I think. I got a call from a Canon rep this afternoon, to tell me that they are exchanging my Mark III. There is already a shipping label on the way, and once I can prove that the old body has shipped, they will send me a new (hopefully, probably refurbished) body...Too bad this process has been close to a year!
p.72 #14 · ['NEW Fix' UPDATE!] - MkIII AF still broken
lermite wrote:
- Center AF point only, pointing on a stationary subject, stable support (tripod or bean bag) --> the AF is continuously adjusting back and forth by a significant amount even if camera and subject aren’t moving at all. This results in a lot of out of focus images (even at f8), as with wildlife you haven’t always the time to switch to One Shot mode. (The MkIII white paper states: " Even if AI Servo AF is used to focus on a still subject, stable control is enabled so that the lens drive isn’t constantly fine-tuning. If the subject starts to move, the focusing responds immediately to detect the subject constantly.”)....Show more →
My photography (sports, corporate, events) isn't quite the same as yours but I found that after installing firmware 1.2.3 the issue of AI Servo twitch dropped off considerably, though not completely gone. Certain of my lenses, particularly the faster ones and the 50 f/1.2L in particular, still cause substantial AI Servo twitch. But with lenses like the 70-200 f/4L, 400 2.8 IS or 600 IS, the camera is much calmer and doesn't feel like it's trying to focus on every molecule of air between it and the intended subject.
One note that might interest you: You can quickly switch between AI Servo and One Shot by setting CF III-6-4 and using the AF stop buttons on the big IS tele lenses. Personally I prefer III-6-5 to enable IS start and remove AF start from the shutter release so I can lock AF by letting go of the AF-ON button (I actually reverted back to the * button).
- The slower a subject moves the less reliable is the AF tracking. I had rather good results at 10fps testing on cars driving towards me on a motorway at 120km/h, but with 4fps and birds slowly flying, walking or swimming towards me, more than half of the images are out of focus.
Yes, I found this too and Rob Galbraith has also reported it. I noticed it in photos of people walking or running at a slow pace. Those tend to have a higher number of out of focus images in a sequence. I can't say I've found a solution for it...
p.72 #15 · ['NEW Fix' UPDATE!] - MkIII AF still broken
I've actually seen that as well. AI Servo of people merely walking toward the camera befuddles the AF system to an abnormal extent (regardless of FPS). It's like it's expecting the subject to be a certain speed or something...
p.72 #16 · ['NEW Fix' UPDATE!] - MkIII AF still broken
Jeff wrote:
I've actually seen that as well. AI Servo of people merely walking toward the camera befuddles the AF system to an abnormal extent (regardless of FPS). It's like it's expecting the subject to be a certain speed or something...
if the AF algorithm in ai-servo is "predictive", then it's reasonable to assume that it extrapolates the subject's distance and/ or speed toward/away from the camera based on previous data points. that assumption, coupled with the 1d III AF servo's aggressively fast tuning = error prone.
the following factors also kill things more, for any ai-servo system:
- fast subject speed
- close subject to camera distance
- non-constant subject speed
- wide lens aperture
i don't think you can get accurate and fast at the same time. i'm sure they (canon engineers) strove for a good balance, but didn't quite get there. i have fought these challenges with robotic servo control before (and lost), with better servo motors.
