Help me understand this email from Leica

[crons]

Advertisement (gone after registration)

1 hour ago, lct said:

I seem to have seen this very thing in the M10 instructions manual

Maybe you're talking about auto-ISO settings for shutter speeds. I shoot all manual.  I pick the shutter speed myself. Since my lens is set to 35mm this would also work for auto-iso settings. The lens doesn't need to be auto detected. The camera knows is a 35mm lens. It goes to 35f2 ASPH as soon as I take out my 50 summicron. Not sure what this has to do with profiles only for some correction and exif data. 

I stop reading when it says "leave it to the camera" 😄 that’s for amateurs. 

Welcome, dear visitor! As registered member you'd see an image here…

Simply register for free here – We are always happy to welcome new members!

I was confised as you mixed both lenses being coded and this (which i know as minimum shutter speed auto-iso settings). Lenses do not need to be coded. You just have to set which lens you're using if it isn’t coded. Since this is the only lens with this issue then i treat it as uncoded. Just pick it from the menu. But yes, the auto-iso "shake proof" thing works just fine, just like it would with uncoded lenses that you select manually. 

Edited June 6, 2024 by crons

[Advertisement]

The Leica Q3 is available for pre-order at B&H Photo Video and Adorama

[crons]

53 minutes ago, hansvons said:

Exactly my sentiment.

Good to know I'm not going crazy thinking this isn't really a big deal. 

[lct]

42 minutes ago, crons said:

[...] Since this is the only lens with this issue then i treat it as uncoded [...]

That's what i understood but fact is you got a lens with coding capabilities that are impossible to use actually. We are all different of course but i would never keep such a lens and/or body personally. I use anti-shake shutter speeds frequently on the M11 to avoid camera shake blur at 60mp and i use too many uncoded lenses to be happy with  manual lens detection. YMMV

[crons]

5 hours ago, lct said:

That's what i understood but fact is you got a lens with coding capabilities that are impossible to use actually. We are all different of course but i would never keep such a lens and/or body personally. I use anti-shake shutter speeds frequently on the M11 to avoid camera shake blur at 60mp and i use too many uncoded lenses to be happy with  manual lens detection. YMMV

. 

In terms of every day use it makes 0 difference to me whether the coding works ot not. Everything works including your anti shake auto iso. I only own 2 lenses as I said. I don't have your problem of having to keep changing lenses manually because you have too many uncoded lenses. I never have to change lenses manually as it changes by itself when I switch lenses.

Whether I keep this copy of the lens or not is up to me. However my camera is never going anywhere. 

The closest answer we can come up with is that there is a batch of 35f2 ASPH that have a problem being auto detected on M10 cameras. If your hobby is testing equipment then you should also get a Leica M10 or M10R in to test the lens. It does nothing for this issue to test it on any other M camera. 

 

I think the bigger point being made is this. 

For someone like me who uses only 2 lenses or someone who has all coded lenses and it is having this issue with this one lens, the 11879 and the 11673 have the exact same coding 011110. Having the lens detected automatically or choosing the 11879 profile manually is exactly the same thing. As long as you leave it here in the manual menu it makes no difference whether the camera detects it or not. It'll go to it by itself and corrections will be applied. Also your auto iso shutter shake thing works. Everything works perfectly fine. Although I would encourage you to get off auto. 

For someone who has a mountain of uncoded lenses and likes the convenience of auto detection then obviously you'll have to journey back to the store and go through that headache. 

It is more hastle for me to have to deal with stores and shipping lenses here and there or opening new packaged lenses and try them on and fight with people about this and that and demand stuff and put up with having to drive there which is a royal pain than just choose it in the menu and go take photos. 

If the guy at the store knew about this issue and had said to me look. I have a brand new sealed in the box 35asph here. Problem is this year batch has a problem where it may not be detected automatically (and he already gave me a $110 discount on it since the retail price went up) and you have to just pick it manually from the menu. I would've said, eh. Don't worry about it. I'll choose it manually. 

Edited June 6, 2024 by crons

[lct]

1 hour ago, crons said:

[...] For someone who has a mountain of uncoded lenses and likes the convenience of auto detection then obviously you'll have to journey back to the store and go through that headache [...]

You don't need a mountain of uncoded lenses actually. 2 are enough. 35 + 135 for example. Just mount an uncoded 35mm lens (or an undetected lens like yours) in manual detection mode, remove it, then mount the uncoded 135 and if your camera behaves like mine, it will "think" the 135 is again a 35mm lens. No problem if you don't need coding for whatever reason, but if you do, you'll run out of a properly coded 35 soon or late, if only because you paid for that. Now, i'm not trying to persuade you since your mind is already made up, but you've asked others for their opinion so i'm just giving mine for what it's worth.

[crons]

21 minutes ago, lct said:

You don't need a mountain of uncoded lenses actually. 2 are enough. 35 + 135 for example. Just mount an uncoded 35mm lens (or an undetected lens like yours) in manual detection mode, remove it, then mount the uncoded 135 and if your camera behaves like mine, it will "think" the 135 is again a 35mm lens. No problem if you don't need coding for whatever reason, but if you do, you'll run out of a properly coded 35 soon or late, if only because you paid for that. Now, i'm not trying to persuade you since your mind is already made up, but you've asked others for their opinion so i'm just giving mine for what it's worth.

I don't have 2 uncoded lenses. So it's not my problem.

I have no idea what this means

"No problem if you don't need coding for whatever reason, but if you do, you'll run out of a properly coded 35 soon or late". I think you mean to say eventually I might need a coded 35mm lens that is automatically detected. I can't picture that scenario. Every lens I've had so far has been uncoded except for my 50 summicron and I never had any issues with them being uncoded. 

Yes you're giving your opinion but the reason you've written it about 10 times is because you're not articulating it properly. 

You can just say "if I pay for a coded lens and it's not being detected I would return it"  and that's all. Which is something I considered. But I didn't pay for it because it was coded. I never thought of it. 

Edited June 6, 2024 by crons

[lct]

Advertisement (gone after registration)

12 minutes ago, crons said:

Yes you're giving your opinion but the reason you've written it about 10 times is because you're not articulating it properly. 

Let's leave it at that.

[crons]

35 minutes ago, lct said:

Let's leave it at that.

Right. You say return it, others say keep it. And that's all really. It's not complicated. 

[lct]

I'm just waiting for a demo copy i borrowed to see how it works on my M11 and M240. Flawlessly i hope but i shall see.

[crons]

1 hour ago, lct said:

I'm just waiting for a demo copy i borrowed to see how it works on my M11 and M240. Flawlessly i hope but i shall see.

If you have a coded v1 it'll work the same. 

[lct]

I'll check mainly the effect of the new 11 aperture blades and if v2 shows less color friging than v1.

[crons]

7 minutes ago, lct said:

I'll check mainly the effect of the new 11 aperture blades and if v2 shows less color friging than v1.

As far as I hear the bokeh is nicer. But I just never pay attention to those things. I'm sure my Nokton 35 frigned a whole lot. I just never saw it. 

So far I'm loving the 35f2. It's so nice and smooth my copy. Every time I get a nice copy of something I'm reluctant to send it off or replace it if it absolutely necessary. I've heard of nasty stuff like loose elements or rough focusing or flaws in the glass itself. My copy is flawless (minus the weird coding thing)

[lct]

Just received a demo copy of the Summicron 35/2 asph v2. It has the same 6-bit code (011110) as v1, its coding pits look identical and it is automatically detected on both my M11 and M240 bodies. V2 has also the same lens ID as v1 in exif data (Summicron-M 1:2/35 ASPH). As far as 6-bit coding is concerned, v1 and v2 are the same lens then. This doesn't help understanding why v2 is not detected by some M10 bodies but it doesn't matter if the OP prefers keeping things as is anyway. Remains to see how v2 compares on photos with v1 but it is another story that has been treated elsewhere i suspect.

[crons]

6 hours ago, lct said:

automatically detected on both my M11 and M240 bodies

Yep. As expected. Can you take a photo of the back of your M11 with the lens mounted and press the center button to see what it says?

[lct]

i'll do that tomorrow i you don't mind as it is 03:53 AM where i live so it is time to 😴

[crons]

1 hour ago, lct said:

i'll do that tomorrow i you don't mind as it is 03:53 AM where i live so it is time to 😴

Cool. This is why this is so strange. If I send you my lens it'll be detected on your camera also. 

[lct]

8 hours ago, crons said:

Can you take a photo of the back of your M11 with the lens mounted and press the center button to see what it says?

"2/35mm", same as with the v1 of the lens or with any uncoded lens hand-coded the same way. When the camera reads the code, it believes that it is a Summicron 35/2 asph but it has no means to know if this is a v1 or v2 of the lens, nor if it is an Ultron 35/2 hand-coded the same way. Same experience with v4 and v5 of the Summicron 50.

[lct]

6 hours ago, crons said:

If I send you my lens it'll be detected on your camera also. 

Yes or no i suppose. Yes if the camera is the only culprit in your case. No if it is the lens that would have a glitch in the coding pits for instance, such as it is seen as uncoded or otherwise hand-coded on both your M10 and my M11. I guess a good way to know more would be for you to watch the exif data of a DNG file or for your store to mount a v1 on your body.

[Advertisement]

Hallo,

Look here: Leica M

[crons]

28 minutes ago, lct said:

"2/35mm", same as with the v1 of the lens or with any uncoded lens hand-coded the same way. When the camera reads the code, it believes that it is a Summicron 35/2 asph but it has no means to know if this is a v1 or v2 of the lens, nor if it is an Ultron 35/2 hand-coded the same way. Same experience with v4 and v5 of the Summicron 50.

Same as me then ... all is well 😀

Since i will never and have never owned more than 2 lenses, i just set it and forget it

Welcome, dear visitor! As registered member you'd see an image here…

Simply register for free here – We are always happy to welcome new members!

Edited June 8, 2024 by crons

[crons]

9 minutes ago, lct said:

Yes or no i suppose. Yes if the camera is the only culprit in your case. No if it is the lens that would have a glitch in the coding pits for instance, such as it is seen as uncoded or otherwise hand-coded on both your M10 and my M11. I guess a good way to know more would be for you to watch the exif data of a DNG file or for your store to mount a v1 on your body.

In every case this happens, the lens is detected on other non M10 cameras. And the camera reads other coded lenses (same as mine)  I don't have any other M camera but I don't have any reason to believe mine is any different than every other case. 

Edited June 8, 2024 by crons