I have a problem while using 650D + EF-S18-135 STM in Movie Crop mode.
Settings Canon:
Movie Servo AF: Enable
ML Settings:
Movie Crop Mode: ON
In the first few seconds there is often no problem, but then suddenly the picture freezes regularly about half a second, thus producing still images during video recording.
Now when I switch off one or both of the above two settings, there is nothing to worry about and the recording is ok.
Can other users of this lens confirm the problem?
EDIT August 23:
Error has been confirmed with these settings:
Canon menu:
AF method: Flexizone - Multi <-- this was not included before
Movie Servo AF: Enable
ML menu:
Movie crop mode: on
No, I can't confirm this. It works fine for me.
Which build? Which SD card? More info please.
Can't confirm either using the "tiny" 18-55 IS STM (or any other lens)
Quote from: satriani on August 19, 2013, 09:51:10 PM
No, I can't confirm this. It works fine for me.
Which build? Which SD card? More info please.
Currently I'm using your ML_N_19.08.2013 (and update on a regular base), but I first noticed the problem with the very first 1.0.4 update.
I did use the ML 1.0.1 version, but I bought the EF-S 18-135 IS STM after updating the camera to 1.0.4 and while waiting for the compatible ML. Crop Movie was introduced in the same period, but I was not able to use it because of my camera update.
Lens Firmware: 1.5.0
IS and AF both enabled
SD card: SanDisk 32GB Extreme Pro 95MB/s
There's no problem with my other lenses.
BTW. I forgot to tell that the problem is most noticeable in fast panning scenes or scenes with a lot of activity.
Example video I posted 2 weeks ago (just sweeping the camera): https://www.youtube.com/watch?v=ZFKlpw7m5xk
I have been a programmer on various systems and languages for about 30 years... And somewhere in my subconscious raises a voice telling me that perhaps the 650D AF-sensor may be distorted/cut-off in video crop mode. But then... I don't have problems with the EF 40mm STM, which uses the same AF-system (distance / contrast meassurement).
I didn't study the Canon DSLR technology (yet), so it's just a feeling... but I learned to listen to voices from the subconsiousness when debugging hard- and software troubles ;D
So, you know what to do, it's time to use the warranty :)
But, do you see the frame freezes on the cam display while recording?
Quote from: satriani on August 20, 2013, 12:19:07 AM
So, you know what to do, it's time to use the warranty :)
That's the first thing I thought about... and I realized that they will send it back to me with the message:"
Nothing wrong. 80 euro's please.", because there is nothing wrong when you use it without ML. Servo AF works fine without Crop Movie ;D
QuoteBut, do you see the frame freezes on the cam display while recording?
Yes. Identical to what will be recorded.
Okay... While thinking about how the AF could be disturbed in Movie Crop Mode, I did some further testing... and found another setting that has an effect on the freeze-error.
Canon menu:
AF method (above Movie Servo AF): FlexiZone - Multi
There's no temporary freezing when set to Tracking or Flexizone - Single.
So, the correct test conditions are:
Canon menu:
AF method: Flexizone - Multi
Movie Servo AF: Enable
ML menu:
Movie crop mode: on
EDIT (further thinking):
The manual says that 21 AF-points are used in video mode / Flexizone - Multi (25 AF-points in 640x480 resolution)... and I'm sure they are talking about the full imaging chip instead of a cropped chip. So this would mean that active AF-points outside the crop-zone could drive the software crazy because of receiving strange unexpected data while trying to find the right AF-point... or the other way around; It tries to auto-select an AF-point that is outside the crop-zone... I guess...? :o
BTW: CPU info from ML Debug menu keeps indicating 60-62% activity (at this moment... yesterday I saw much higher values) and it doesn't change significantly during/immediatly after a short freeze... at least not visibly. The measurement might stop when the software is looping (freezing) for a short moment?
Quote from: satriani on August 19, 2013, 09:51:10 PM
No, I can't confirm this. It works fine for me.
Quote from: nanomad on August 19, 2013, 09:54:12 PM
Can't confirm either using the "tiny" 18-55 IS STM
I don't like to waste your time, but I'm very curious how your test results are with the "AF method: Flexizone - Multi" setting, as described in my previous post. :)
I love the enthusiasm. Not all at once please! 8) ;D
EDIT:
Other AF problems with the same lens:
http://www.magiclantern.fm/forum/index.php?topic=7473.msg68640#msg68640
He has movie servo enabled. That disarms follow focus
Quote from: nanomad on August 23, 2013, 11:54:04 AM
He has movie servo enabled. That disarms follow focus
Ok... but now I still don't know if there are more people with EF-S 18-135 STM who get the freeze-error with the setting "AF method: Flexizone - Multi"
To be clear... the error depends on 3 settings instead of just the 2 settings I mentioned in the first post.
Canon menu:AF method: Flexizone - Multi
Movie Servo AF: Enable
ML menu:Movie crop mode: on
Your (nanomad's) EF-S 18-55 would be interesting to test, to rule out that the problem is there with all EF-S STM zoom lenses. At least it is not there with the prime 40mm STM.
Good job. I can now confirm it with the 18-55 IS STM (no issues with the non STM version)
Now, what should we do? I think we can issue a warning if crop mode + flexi zone + servo AF is on.
Quote from: nanomad on August 23, 2013, 02:50:32 PM
Good job. I can now confirm it with the 18-55 IS STM (no issues with the non STM version)
Now, what should we do? I think we can issue a warning if crop mode + flexi zone + servo AF is on.
Thanks for confirming! It makes me feel better because I now know that my lens has no defects.
What should be done?
Hmmm... I think it would be great if the cause could be removed, but a warning to the user would be nice for the time being! :)
Maybe the error can be removed by excluding/disabling AF-points outside the crop-area?
Nanomad... maybe it already came to your mind, but I think that 700D and EOS-M may have the same problem because they use a similar Hybrid AF CMOS... and maybe 100D also, which has type II of this chip?
Also I can confirm that. How long can it take when specified too little info ;)
Yes the bug definitely affects all the similar models and that's probably the primary reason canon took crop mode out
Quote from: satriani on August 24, 2013, 06:45:50 AM
Also I can confirm that. How long can it take when specified too little info ;)
All the info was there for a few days already (august 20), but I guess you didn't read it anymore.
Heh, I just kinda don't use multi-zone AF. No focus box and crap on the screen and then it focuses on whatever it feels like.