Jump to content

Recommended Posts

Advertisement (gone after registration)

Would that be for the type V1 & V.

 

There are two codes for the 50/2. Both would work to show the focal length and aperture in the Exif - and both would be inaccurate anyway for corner correction purposes.

 

You may actually be able to get a "better" corner correction for a J-8 by trying other codes (eg, those designed for wider Leica lenses), but this (a) is much easier to do with an M9 using the lens selection menu and (B) would mess up the Exif, unless you are prepared to use Lens Tagger (see below).

 

I just use the 100001 code to get the Exif right and then make any image correction in LR.

In any event, the J-8 is far from being optically flawless, so you may as well leave the corners alone and use the character of the lens for what it is...

 

If you use LR as well, the Lens Tagger plug-in by Dirk Essl (donationware) also enables you to edit the Exif to show the proper lens name and information.

  • Like 2
Link to post
Share on other sites

Any advice as to the best 6 bit coding for the above lens on a Leica 8.2 body.

 

If your coding purpose is in fact EXIF data storage for easier identification of which lens was used in which photo, you might use another approach, if you use an image management software as Adobe Lightroom or Aperture.

 

I use Lightroom and when copying my files from the card, I do tag all photos with the lens, I used.

This sounds complicated, but is actually very easy and fast.

 

I usually don't use more than 5 different lenses on one body during a shoot, so at the very most, I tag the whole card with 5 different lenses upon import.

After the files are imported, I simply go through them while editing and click or un-click the respective tag in the keyword panel on each photo, while doing my usual edit.

This costs me less than 3sec/ photo, if many lenses are involved and less than a second, if I had only one or two lenses on one body.

 

I don't bother coding any lenses (I use many vintage lenses), which would create a mess.

 

Coding lenses for what they don't are usually gets messy latest when one adds the lens, one has coded another lens for and can't discern the data, which was which - with the key wording approach, this is straight forward (I even have the SN of each lens included, as I have a few samples of some lenses, which I like to separate data wise as well).

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...