6 Bit Coding Question

[S.Rolf]

Advertisement (gone after registration)

I'm new to the LEICA M arena and have an MP .72 35mm on the way.

I also purchased with it the 35mm f2.4 ASPH lens.

 

I'm just now noticing in the specs for my lens that it states the lens has "6 bit coding".

I am not sure what this means especially as it relates to the MP.

The MP will accept lenses with the 6 bit coding correct?  Because I've got my eye on the 50mm 2.0 that also states that it has this coding.

 

BTW - I'm jumping back into LEICA film cameras now and the last one I had was an R7 SLR LEICA.

Back then "coding", to the best of my knowledge, was not a consideration.

 

Thanks,

[Advertisement]

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

[duckrider]

Coding only for digital cams, has nothing to do with film based ones. There is of course no sensor in and film-M.

Digital cams can calculate color fringing caused by wide lenses away e.g., that's the sense of coding.

2nd benefit is info which lens was used in the files.

Thomas

[S.Rolf]

Yes, I did some more digging and found that it's perfectly fine to use coded lenses on a film camera.

Thanks.

[jankap]

A 6 bits code delivers 63 (64 mathematically) possibilities only.

Jan

[jaapv]

No - 192. Of which 2 must be deducted for the MATE.

[duckrider]

No - 192. Of which 2 must be deducted for the MATE.

Jaap, how do You calculate this?

         2^            makes

            0              1

            1              2

            2              4

            3              8

            4            16

            5            32

            6            64

            7          128 

            8          256

            9          512

          10        1024

          11         2048

          12         4096

          13         8192

          14       16384

Edited March 8, 2016 by duckrider

[jaapv]

Advertisement (gone after registration)

The frameline setting adds two positions per code (three in total), except for the MATE, which takes up three positions instead of one, so 3x64-2

[Herr Barnack]

@S.Rolf,

 

You may have figured this out by now, but I would like to sum it up for those who may still be unclear about coding.  All new M lenses are now coded for use with digital M cameras. 

 

The coding is nothing but a series of black and white squares on the lens mount which the camera can read to compensate for vignetting.  Other than that, the lenses are the same as their previously non-coded brethren in terms of optics, design, construction, etc. (a type 5 50mm Summicron built in 1995 is the same optically as a type 5 built in 2013, except for the coding on the 2013 copy).

 

I am unsure if coding compensates for color fringing; I spoke with the Leica NJ tech guy and he spoke only of vignetting (my f/1.0 Noctilux is coded but it still produces purple fringing in some high contrast situations).  

 

Hope this helps.

Edited March 8, 2016 by Carlos Danger

[MT0227]

I know this lens is quite prone to fringing, and have the same problem with by Nocti f/1.0 (v4) .  Mine was stated as being 6bit coded, LR sees this lens in the meta data but there is no camera profile available except for the 0.95. 

 

 

@S.Rolf,

 

I am unsure if coding compensates for color fringing; I spoke with the Leica NJ tech guy and he spoke only of vignetting (my f/1.0 Noctilux is coded but it still produces purple fringing in some high contrast situations).  

 

[S.Rolf]

@S.Rolf,

 

You may have figured this out by now, but I would like to sum it up for those who may still be unclear about coding.  All new M lenses are now coded for use with digital M cameras. 

 

The coding is nothing but a series of black and white squares on the lens mount which the camera can read to compensate for vignetting.  Other than that, the lenses are the same as their previously non-coded brethren in terms of optics, design, construction, etc. (a type 5 50mm Summicron built in 1995 is the same optically as a type 5 built in 2013, except for the coding on the 2013 copy).

 

I am unsure if coding compensates for color fringing; I spoke with the Leica NJ tech guy and he spoke only of vignetting (my f/1.0 Noctilux is coded but it still produces purple fringing in some high contrast situations).  

 

Hope this helps.

 

 

Basically all I really wanted to know is if lenses with the new coding feature can be used on film cameras like my MP 35mm.

I just wanted to make sure that I didn't buy something that can ONLY be used on a digital camera.

I called B&H (where the MP and two M lenses are coming from) and they said "No problem".

Sorry to get you guys off on a tangent.  My fault for not being clear in the first place.

 

Thanks for all the input though.

I can tell this forum will be very valuable for me once I get my feet back into the "emulsified waters" again.

[duckrider]

I know this lens is quite prone to fringing, and have the same problem with by Nocti f/1.0 (v4) .  Mine was stated as being 6bit coded, LR sees this lens in the meta data but there is no camera profile available except for the 0.95. 

 

try this:

 

Noctilux-M 50mm f/1 11821 & 11822 - 011111 ⬜⬛⬛⬛⬛⬛  instead of

Noctilux-M 50mm f/0.95 ASPH 11602 - 110001 ⬛⬛⬜⬜⬜⬛

 

 

 

from page

http://lavidaleica.com/content/leica-lens-codes

 

Thomas

Edited March 9, 2016 by duckrider

[CheshireCat]

I am unsure if coding compensates for color fringing; I spoke with the Leica NJ tech guy and he spoke only of vignetting (my f/1.0 Noctilux is coded but it still produces purple fringing in some high contrast situations).  

 

 

Digital Leica cameras will only correct color vignetting based on the lens code.

Color fringing is caused by chromatic aberration in the lens, it is more difficult to correct, and must be corrected in post. Use Lightroom's "Defringe" sliders.

Edited March 9, 2016 by CheshireCat

[CheshireCat]

No - 192. Of which 2 must be deducted for the MATE.

 

And other 3 of which must be deducted for the 0 code (uncoded/no lens).

[jaapv]

try this:

 

Noctilux-M 50mm f/1 11821 & 11822 - 011111 ⬜⬛⬛⬛⬛⬛  instead of

Noctilux-M 50mm f/0.95 ASPH 11602 - 110001 ⬛⬛⬜⬜⬜⬛

 

 

 

from page

http://lavidaleica.com/content/leica-lens-codes

 

Thomas

It will do nothing for fringing though.

[MT0227]

I think my Lens is coded properly....in the metadata is shows Noctilux-M 50mm f/1.   When I go to the lens selection under profile, Noctilux-M 50mm f/1 is not an option, only Noctilux-M 50mm f/0.95 ASPH.  Is there a way to add a profile to LR?  I not sure one even exists for this lens,  I'm trying to find one.

 

 

try this:

 

Noctilux-M 50mm f/1 11821 & 11822 - 011111 ⬜⬛⬛⬛⬛⬛  instead of

Noctilux-M 50mm f/0.95 ASPH 11602 - 110001 ⬛⬛⬜⬜⬜⬛

 

 

 

from page

http://lavidaleica.com/content/leica-lens-codes

 

Thomas

[CheshireCat]

Is there a way to add a profile to LR?  I not sure one even exists for this lens,

 

Profiles won't help. Just use the "Defringe" settings in Lightroom.

Read this first:

http://www.l-camera-forum.com/topic/257728-how-to-remove-purple-fringing-in-noctilux-photos-at-overgaarddk/

Edited March 10, 2016 by CheshireCat

[rjsphd]

Any idea what it costs to have older Leica lenses coded by Leica customer service?

[CVickery]

Any idea what it costs to have older Leica lenses coded by Leica customer service?

I just had my Summilux 75 and a Summicron 50 coded by Leica and the cost was $300/lens

[Advertisement]

Hallo,

Look here: Leica M

[BBHewee]

Would that include a CLA and calibration for digital?

[arno_nyhm]

leica sure wont let a dirty lens leave the service coded. or would they?