Found the lens decoder table in 1.09 firmware

[cbretteville]

Advertisement (gone after registration)

There may be a jump table stored somewhere else, with an entry for each lens, pointing to a subroutine. To handle each lens, the firmware would just call the subroutine associated with the lens – which may or may not be the same as the subroutine for another lens – which will perform the necessary corrections. In this case, the corrections could be highly individual and arbitrarily complex – as complex as they need to be.

 

This is my guess too at this point. There dosen't seem to be enough data (or empty space) in this table to do any more than what we've uncovered so far.

[Advertisement]

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

[oldsnapper]

Since we have the exif info and all the codes, I assume it should be pretty easy to change the line where it says that there is not code with the corresponding lens code.

 

Am I correct?

would this allow capture one to apply the correct lens corrections (vignetting, distortion, infrared...) or this only happens in camera?

 

thanks.

g.

[scott kirkpatrick]

The holy grail is to find a way to convince the camera to set the result of lens detection to whatever Leica lens most closely resembles the Zeiss, Voigtlander, Canon, Konica, or pinhole lens that you are presently using, so that one can take advantage of the M8's firmware corrections for vignetting and color correction. These can be corrected in post processing software, of course, but not without significant extra effort. Also, corrections made in camera are made directly to the raw, one color, pixel data and cause the least loss of information.

 

Now that Leica has issued hints that they prefer not to trust us to do this, except for the WATE where it is necessary, this is definitely looking like a long shot.

 

scott

[blakley]

You can already do something similar to that using hand-coding.

 

Another interesting possibility would be to "patch" the firmware to add an unsupported lens to one of the unused table entries; just pick a lens (say 50/1.2 Noctilux Asph), pick an unused table entry and the corresponding row, do a little hex editing, et voila, an a la carte M8 that recognizes your (unsupported, hand-coded) lens!

 

Of course this would require understanding what every field in the firmware entry does...