dante Posted January 25, 2016 Share #21 Posted January 25, 2016 Advertisement (gone after registration) It's actually pretty useless for most lenses except for the metadata that would help you see what lens you are shooting. Wides: you get corner correction (vignetting and color shift) and the metadata that lets LR do its distortion thing. The usefulness of this is somewhat limited given the the amount of corner correction you need is dependent to a degree on the focusing distance. 40-50mm: doesn't do anything except give you the metadata. >50mm: doesn't do anything except metadata. Owning several Zeiss lenses that can't be coded, I've pretty much given up on using automatic or even manual coding. If the color shift and vignetting are bad enough, I use Adobe Flat Field. Dante Link to post Share on other sites More sharing options...
Advertisement Posted January 25, 2016 Posted January 25, 2016 Hi dante, Take a look here Why is lens detection such a big deal?. I'm sure you'll find what you were looking for!
Jared Posted January 25, 2016 Share #22 Posted January 25, 2016 The in-camera corrections are for vignetting (colour and optical) only. The LR corrections are for distortion. In a sense both are destructive in a sense that the camera corrections will change the brightness values in the corners, but the LR ones shift pixels. For both kinds you'll be hard put to see any quality loss- in other words - of no relevance. In general JAAPV is correct, but it can actually get a bit more complex when discussing third party lenses. The LRvprofile for the Zeiss 18mm f/4 Distagon, for example (currently my only non-Leica lens) corrects for distortion as well as edge color cast and vignetting. If you were to code this lens in the camera manually you would actually be double profiling and would introduce green edges and over correct vignetting. I believe that JAAPV is correct for all the Leica M lenses, though. Lightroom makes corrections to vignetting and color edges based on the six bit coding, and fixes distortion based upon the manual lens profile selection. One other thing to keep in mind is that LR does not fully correct vignetting based on the 6 bit profile since it doesn't really know the aperture used. The amount of vignetting varies with aperture for most lenses, so the 6-bit coding is a little conservative and only corrects the vignetting you would see with the lens stopped down. This ensures you never get over correction of vignetting. - Jared Link to post Share on other sites More sharing options...
bencoyote Posted January 25, 2016 Share #23 Posted January 25, 2016 This is not a troll, I promise. I don't get it. The camera doesn't care what lens you use. None of my lenses or adapters are encoded. Everything works fine. I understand that the camera can do some processing with wide angles but I don't see any problems with mine. Perhaps I'm an outlier because I don't care what camera or lens I use-or even where the picture was taken but that's another story. I just care about the image. I'm a 40 year Leica user and this is not a troll, I promise. I just don't get it. You mean other than having the right frame lines when you don't have a selector lever? :-) Other people have mentioned EXIF data but this video really shows how a modern photographer, one who probably was wearing diapers when you first picked up a Leica, makes use of EXIF data. There is nothing wrong with not doing this but you can see that there can be benefits to doing it. Additionally, having the image is one thing. Finding the image is another. With digital being essentially free even a hack like me can shoot a couple thousand images a month and when statistics work in my favor and I do get a good one, I need to continue to be able to find it. All those things like where it was taken, when, what lens... all are clues that can help me find things. Admittedly which lens is less useful as a search term at least occasionally. Metadata is for curation and retrieval. Link to post Share on other sites More sharing options...
jaapv Posted January 25, 2016 Share #24 Posted January 25, 2016 Lens coding does not trigger frame lines... Link to post Share on other sites More sharing options...
jdlaing Posted January 25, 2016 Share #25 Posted January 25, 2016 Lens coding does not trigger frame lines... How many times have we repeated that? Link to post Share on other sites More sharing options...
Joshua Lowe Posted January 25, 2016 Share #26 Posted January 25, 2016 Besides the benefits of in-camera correction the reason it's important to me is organization. One of the reasons I got rid of my CV and Zeiss glass was the amount of time fixing the EXIF data of a day's worth of photos was adding to my workflow. What's worse, it was easy to forget to switch detection back on after changing to a Leica lens. So I'd end up with a confusing mess of incorrectly tagged photos with the incorrect adjustments applied. By switching to coded Leica glass all of those problems disappear and hours of my time are saved. Link to post Share on other sites More sharing options...
Mornnb Posted January 29, 2016 Share #27 Posted January 29, 2016 Advertisement (gone after registration) This is not a troll, I promise. I don't get it. The camera doesn't care what lens you use. None of my lenses or adapters are encoded. Everything works fine. I understand that the camera can do some processing with wide angles but I don't see any problems with mine. Perhaps I'm an outlier because I don't care what camera or lens I use-or even where the picture was taken but that's another story. I just care about the image. I'm a 40 year Leica user and this is not a troll, I promise. I just don't get it. Two reasons. Because it allows lens corrections for distortion and corner colour issues at the raw level, before it reaches Lightroom. And to identify the lens for your audience incase they're curious (i.e. sites such as Flickr). Link to post Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.