35mm v4 Summicron auto-codes as "Summilux-M 1:14/35 on CL

[norm_snyder]

Advertisement (gone after registration)

I now have the Leica M-Adapter L for my CL, and mounting my 35mm f2 v4 Summicron, 6 bit coded, it is recognized by auto-recognition on the CL as "Summilux-M 1:1.4/35."  Has anyone else encountered this behavior?  I can manually code it as a 35mm Summicron-M  11310, but if I unmount it, use another lens and remount it later, it will again code as the Summilux.

 

I thought there wasn't even a 6-bit code for the pre-aspheric Summilux.  My Summicron had been coded by DAG some years back, and codes properly on my MM, M9 etc.  Other 6-bit coded lenses all auto-code properly.  My 35mm Summicron is coded 000110.

 

Has anyone else encountered this?

[lct]

The Summilux 35/1.4 pre-asph is not coded by Leica so i have no idea how its name can appear if you did not choose the "35 f/1.4 11869/11870/11860" profile through the Lens Profiles menu of the CL. I would check if you did not choose this profile and would clean all contacts on body, adapter and lens if i were you.

[norm_snyder]

I did clean it, and I know the pre-ASPH Summilux has no 6-but code, although it is on the manual list in the camera. Nonetheless, that’s what Auto setting selects when camera is turned on and v4 Summicron mounted. The same lens codes properly on other cameras. Probably not a big deal, except for the EXIF data, as those two lenses are so similar in formula. Not sure if it’s a bug. All the other lenses I have code properly on Auto setting.

[lct]

I have no coded 35/2 v4 so i cannot check on my gear sorry.

[norm_snyder]

Thanks, LCT.  Hopefully someone will be able to check this on a CL, or has encountered this with the adapter on a T or TL.

[thighslapper]

If your lens is 'properly' coded .... ie. not a self coded attempt then I suspect it is a bug.

 

I'm afraid I got rid of both my 35/2 and 28/2 as they perform poorly on digitals apart from the M itself. 

[lawman]

Advertisement (gone after registration)

I now have the Leica M-Adapter L for my CL, and mounting my 35mm f2 v4 Summicron, 6 bit coded, it is recognized by auto-recognition on the CL as "Summilux-M 1:1.4/35." Has anyone else encountered this behavior? I can manually code it as a 35mm Summicron-M 11310, but if I unmount it, use another lens and remount it later, it will again code as the Summilux.

 

I thought there wasn't even a 6-bit code for the pre-aspheric Summilux. My Summicron had been coded by DAG some years back, and codes properly on my MM, M9 etc. Other 6-bit coded lenses all auto-code properly. My 35mm Summicron is coded 000110.

 

Has anyone else encountered this?

I was curious so I just put my v4 on the CL, and yes, it did come up as the 35mm 1.4. This is a self coded Jin lens flange, but it works perfectly with my M9/240/246, so I suspect it’s a software issue. One more Leica peculiarity to ponder [emoji848]

[thighslapper]

I was curious so I just put my v4 on the CL, and yes, it did come up as the 35mm 1.4. This is a self coded Jin lens flange, but it works perfectly with my M9/240/246, so I suspect it’s a software issue. One more Leica peculiarity to ponder [emoji848]

 

Please report by email to Leica ...... unless someone tells them it will never be fixed .....

[norm_snyder]

To whom should the email be addressed?

[sleepyhead]

I’ve experienced the exact same issue when I mount my coded 35/2 IV on my Leica SL via the Leica M adapter. With lens detection set to Auto, the camera suggests that the newly mounted lens is the 35/1.4 pre-ASPH Summilux. The first time I saw this I thought it was odd because I know that there is no 6-but code for the old Summilux.

I think that this is a bug.

 

 

Sent from my iPhone using Tapatalk

[norm_snyder]

I agree, Sleepyhead, and one contact at Leica Store SF recalls this happening with a TL.  I think it should be reported as a possible bug, and will endeavor to do so.

 

In the meantime, I am now manually coding this as a Summicron "35f/2 11310/11311" [as cited in the list of lens profiles] which corresponds in the profile with v4 Summicron.  If I mount my 75mm, for example, it will auto-profile properly and on remounting the 35mm Have to manually reset it, unless I am feeling lazy.

[lct]

[...] If I mount my 75mm, for example, it will auto-profile properly and on remounting the 35mm Have to manually reset it, unless I am feeling lazy.

 

Or you may wish to assign a User Profile to your 35/2 v4 and choose it easily with the FN button. Works fine for my uncoded MATE and Summilux 35/1.4 v2. I don't have to look for those lenses in the Lens Profiles menu this way. 

[norm_snyder]

Or you may wish to assign a User Profile to your 35/2 v4 and choose it easily with the FN button. Works fine for my uncoded MATE and Summilux 35/1.4 v2. I don't have to look for those lenses in the Lens Profiles menu this way. 

 

Well, LCT, it looks like the alternative solution for you, for now, is to hand code your Summilux v2 as a Summicron v4, and it will profile correctly.  Actually, though, your suggestion makes sense.  Thanks, as it may be the interim [hopefully, only interim] fix.

[sleepyhead]

I agree, Sleepyhead, and one contact at Leica Store SF recalls this happening with a TL. I think it should be reported as a possible bug, and will endeavor to do so.

 

In the meantime, I am now manually coding this as a Summicron "35f/2 11310/11311" [as cited in the list of lens profiles] which corresponds in the profile with v4 Summicron. If I mount my 75mm, for example, it will auto-profile properly and on remounting the 35mm Have to manually reset it, unless I am feeling lazy.

Norm, since I don’t have a 35/1.4 pre-ASPH, I don’t bother manually selecting the 35/2 IV, I know from the EXIF data that it was actually the Summicron that I used.

 

 

Sent from my iPhone using Tapatalk

[norm_snyder]

Just an update--

 

Thanks to Leica USA support, in the person of Mark Brady, who has responded to my query about this possible bug.  He notes:

 

"Though the issue was not known here before, your detailed overview is quite convincing.  All we can do is forward your message to the Leica factory in Germany to make sure they are aware of the situation, and wait for a likely firmware update solution to come along."

 

I guess it means that we may get a fix, but who knows when.  On the other hand, it's nice to know that they responded so quickly, and will pass it along.

 

 

 

[norm_snyder]

From Mark Brady at Leica, USA, a further update regarding mis-profiling of v4 Summicron 35mm pre-asph:

 

"I received word back from our associates in Germany.  They state that the issue is known to them and will be addressed with a firmware update.  Unfortunately they are not able to predict when new firmware will be released."

 

​Thanks to Mark at Leica Tech support in New Jersey.  Now all I have to do is wait for what will, at some point, be a firmware update.  I hope the firmware update will be released sooner than the time it took to get the sensor replaced in my Monochrom.  Well...eventually.  I must say, communication from them has been great.  

 

 

 

 

 

Edited March 9, 2018 by norm_snyder