M50 + Tamron 35 1.8 and Tamron 85 1.8, IS Not functioning

Burner100

Member
Messages
34
Reaction score
22
I have been testing my Tamron 35mm 1.8 and 85mm 1.8 on the M5 and also an M50 using the OEM EOS M Canon Adapter. On the M50, the IS does not activate on these lenses under any conditions (half shutter press, full shutter press, etc.). Of note, on the M50, an OEM Canon lens like the original 70-200 f/4 IS will run the IS continuously. On the M5, the IS does activate on all lenses I've tested, including both of the Tamron lenses, upon Power On (same behavior as adapted Canon lenses). On my EOS R, the IS runs continuously on all stabilized lenses, including these two Tamron lenses, just like the behavior on the M5. One additional data point, my Sigma 17-50mm f/2.8 OS lens will activate it's OS system upon Power On on both camera bodies. I'm not 100% sure, but guessing that what I'm seeing is a bug in the M50 firmware since these lenses behave the same on both the M5 and the EOS R but differently on the M50?

Before anyone asks, yes, I am running the latest firmware on all components - both the Tamron lenses and both camera bodies.

Does anyone have any experience with this and/or recommendations to solve?
 
Last edited:
I have been testing my Tamron 35mm 1.8 and 85mm 1.8 on the M5 and also an M50 using the OEM EOS M Canon Adapter. On the M50, the IS does not activate on these lenses under any conditions (half shutter press, full shutter press, etc.). Of note, on the M50, an OEM Canon lens like the original 70-200 f/4 IS will run the IS continuously. On the M5, the IS does activate on all lenses I've tested, including both of the Tamron lenses, upon Power On (same behavior as adapted Canon lenses). On my EOS R, the IS runs continuously on all stabilized lenses, including these two Tamron lenses, just like the behavior on the M5. One additional data point, my Sigma 17-50mm f/2.8 OS lens will activate it's OS system upon Power On on both camera bodies. I'm not 100% sure, but guessing that what I'm seeing is a bug in the M50 firmware since these lenses behave the same on both the M5 and the EOS R but differently on the M50?

Before anyone asks, yes, I am running the latest firmware on all components - both the Tamron lenses and both camera bodies.

Does anyone have any experience with this and/or recommendations to solve?
I'm curious, did you ever figure out a fix for this issue? Really considering either this Tamron 35mm or the Canon 35mm for my M50.
 
I was unable to solve this issue, however, I did contact Tamron about this both with a phone call and an e-mail. I have not received a written reply to my e-mail so far and the feedback from my call to customer service was underwhelming (essentially that Tamron has not certified the lens to work on EOS M and that they couldn't do much about that). So, if the only body you plan to use the lens on is an EOS M50, I would suggest going with the Canon lens instead at this point in time. It's unfortunate because these are great lenses and they both work well on all the other Canon bodies I've tested, including the M5, EOS R, 7D Mk II and 5D Mk IV.
 
I was unable to solve this issue, however, I did contact Tamron about this both with a phone call and an e-mail. I have not received a written reply to my e-mail so far and the feedback from my call to customer service was underwhelming (essentially that Tamron has not certified the lens to work on EOS M and that they couldn't do much about that). So, if the only body you plan to use the lens on is an EOS M50, I would suggest going with the Canon lens instead at this point in time. It's unfortunate because these are great lenses and they both work well on all the other Canon bodies I've tested, including the M5, EOS R, 7D Mk II and 5D Mk IV.
That is unfortunate. I had planned to use it exclusively with my M50. Thank you for the update!
 
Hi, I am facing the same problem. I have both Tamron 35 and 85, both work fine on my M5. Then I downgraded to M50, the 35 VC works just fine but the 85 VC does not work. When attach to the 85 and I switch on the camera, there is a "VC activate noise" from the lens, but it won't continue. I am using the latest firmware on both lens by the way.

Anyway I'm glad the lens work fine on EOS R according to your info. Hope it works fine on the new RP too.
 
Hi, I am facing the same problem. I have both Tamron 35 and 85, both work fine on my M5. Then I downgraded to M50, the 35 VC works just fine but the 85 VC does not work. When attach to the 85 and I switch on the camera, there is a "VC activate noise" from the lens, but it won't continue. I am using the latest firmware on both lens by the way.

Anyway I'm glad the lens work fine on EOS R according to your info. Hope it works fine on the new RP too.
So the 35mm f/1.8 does work??
 
Hi, I am facing the same problem. I have both Tamron 35 and 85, both work fine on my M5. Then I downgraded to M50, the 35 VC works just fine but the 85 VC does not work. When attach to the 85 and I switch on the camera, there is a "VC activate noise" from the lens, but it won't continue. I am using the latest firmware on both lens by the way.

Anyway I'm glad the lens work fine on EOS R according to your info. Hope it works fine on the new RP too.
So the 35mm f/1.8 does work??
Yes.. strangely it works
 
Just picked up the Tamron 85mm VC for my EOS R and it works flawlessly. Decided to revisit this thread as I have the Tap-In console and tried some more troubleshooting with the lens on the M50.

both the 85mm and the M50 are up to date on firmware, I tried setting the 85mm to each of the VC modes using the Tap-In console: Standard, Viewfinder Priority, and Capture Priority. I had the same result on all the three modes and you can physically hear the VC activated and you receive an onscreen prompt, but it is not reflected at half or full shutter press or video recording. I tried this with both the OEM Canon adapter and the Viltrox EF EOS M2 speed booster.

Finally, I tried what the last poster suggested with turned the camera on, THEN attaching the lens and engaging VC and lo and behold it worked. This method worked for both photo AND video mode and successfully engages the VC. It’s an odd and slightly time consuming workaround but I’m glad to have it than to not have the VC at all.

Just thought I’d give anyone experiencing this issue with any of these lenses an update as they are phenomenal lenses and it would be a shame to pass on them because of missed functionality with the M50 (like I originally did).
 
Last edited:

Keyboard shortcuts

Back
Top