I just picked up a new 70-200/2.8 IS last night and I've got to say so far it seems like a GREAT lens. I was wondering if the IS was going to be all that impressive, as it's helpful but not great on the 28-135IS... I must say it's AMAZING the stability the IS adds at 200mm.
So my question - do other 70-200 IS lenses make a slight audible "tick" or "click" when the IS spins up or should I exchange this lens for a different one?
Yeah, noise is expected... Just that initial spin up starts with a tick/click and it doesn't SOUND great, but is understandable. The 28-135IS makes a softer tick when locked onto the body (power on or off).
It's like it starts to spin up (you can feel it), a few hundred ms later it "knocks" and then stabilizes... I must just be paranoid about this very expensive purchase
It's normal. Had me worried at first as well since it is more pronounced than what happens with my Canon IS binoculars My guess is that it is moving much larger elements around.
good stuff. thanks for the confidence boost, Ed
Now with a lens capable of f/32, that blue-sky dust test is troubling... but not enough to get my panties in a bunch, since I shoot way more open than I do closed.
You don't want to be using f/32 if you can avoid it, especially with digital. You start to get softer images due to diffraction. I try to keep the f-stop to a max of f/13 or rarely f/16 unless I'm shooting long exposures of water...
Ed,
Yeah, I would never shoot stopped down that much. Just thought I'd give the ol' CMOS a look for dust... There is enough that I didn't even need to download the image (or even zoom in!) to see it. Thanks for the concern, tho
You guys are right, there is a moving optical element and a set of gyro sensors that feedack the motion detected to these optical elements to cause a so called anti-shake. I think the syncup takes the delay and the moving optical element makes the noise. The optical element might have been smaller in your 28-135 lens. But this is very normal and don't be worried about it.
Thanks again everyone for the confirmation. I was pretty sure this was the case, but it's always good to get a confirmation from other experienced users. I think this puts the issue to rest. Thanks!
My guess is that it is moving much larger elements around.