Messages

That's good to know! How do you like this lens? There is one available nearby for $80.00, should I snag it? I have a nice set of cinema lenses but no zoom for Full Frame.

It's superb, actually. Probably the best mid-range big zoom I can recall Canon making in terms of general usability. It's got perfectly fine optics and, frankly, I prefer it to the equivalent L from the same time period because it's extremely easy to pull focus on compared to that one and some of the other ones where it can get finicky on the far end of the zoom. there are a few better overall zooms that are newer but they're $400 or more. the only issue with it is that it will fall when pointed downwards at intermediate zooms. at $80 in good condition, it's an insane deal. if you're looking to do movie shooting, though, the OIS is loud.

The lens is the issue. This design dates back to 1998 and the IS doesn't activate until half-shutter is pressed. Newer lenses (even the bottom of the line kit lens) have full-time IS (to support video modes)

if changing the behavior is very important to you It may be worth learning to compile from source code. Simulating button presses is one of the simplest coding tasks and a very good project for a beginner. The problem you'll run into is this might make your display go nuts if you are using other features that are triggered by half-shutter

When the camera is in video mode, the IS is on full time, to clarify

Never tried IS with focus stacking. Can't say if it should work or not. Try to reproduce your issue without IS.

The issue is that the IS doesn't trigger properly. It doesn't interrupt the function of the focus stacking at all. My point here is more about whether the behavior here is optimal. Can ML toggle a half press during the entire stacking process to avoid these kinds of issues altogether without breaking something else, and would that improve the overall experience? would that break anything on other cameras, is that a change that could be implemented easily in the codebase and should be implemented, etc.

Lens in use?
Build in use?
Have you manipulated focus stepping? Avoid that for debugging this issue.
Are you trying to use Expo override with aperture *not* wide open? There is a bug affecting all "modern" lenses (starting with "EF 100/2.8 L IS Macro USM" aera). You can use modern lenses wide open, only.

Sorry, I went back to get some specifics, in case I misremembered exactly which one it was triggered on. SO, with the following lens and settings:
Canon 28-135mm IS USM (2006-ish? Maybe?) wide open just in case
Expo override off
2 steps before 2 steps after

Behavior: triggering of IS is completely random. First time I tried this stack, it triggered only step 3. second it triggered steps 3 and 4, and 5. and on from there, it triggered during random steps.

running into an issue with focus stacking where it only triggers the lens IS motor for the first image and sometimes the last one, rather than starting the IS motor, taking all the pictures, and then shutting it off. is this fixable?