On Thu, Feb 21, 2019 at 2:45 PM Remco Viëtor <[email protected]> wrote:
> On jeudi 21 février 2019 14:09:53 CET fht233 wrote: > > Hi, first of all I have to say that it is a great software and I like a > > lot. > (... long explanation about how any module works) > > > > Maybe it was already discussed or it is not a good idea But I think that > a > > clear and understable setting would be easier than having to perform all > > the investigation and setting up things by yourself when you are not yet > > familiar with the software and the terms. Googling and finding 'activate > > the setting' would be easier than having to learn to set up the preset by > > yourself, IMHO. > > The lens correction module works like almost any other module (exceptions > are modules that are absolutely needed for raw files, like demosaic). > I found the darktable documentation very complete, not only the manual, > but > also the other info accessible through the Darktable web site. Presets are > described in section 8.5, btw. > No doubt about it. > As in most programs, changed automatic presets are only applied to newly > imported items. Good thing too, as (with Darktable) you might want to > change > the presets when you change camera (body/brand/lens/...). In your case, > say > you decide to change one of your lenses for a newer model, with > *different* > distorsion parameters. Do you really want that autoapplied to older > images? > If you change the lens I assume that it would be identified as another version. But ok, you are right that it is not a good idea in general. And it was not my point anyway. There is another catch with the lens correction module, related to the way > lenses are identified. The lens identification in the metadata is based on > an > ID value provided by the lens. This value is NOT unique between brands, so > a > given value can refer to several lenses. Also, cameras don't necessarily > know > all ID values possible (esp. for 3rd party lenses), which means the lens > identification is uncertain. > Then there is the possibility of extender rings, focal multipliers, > converters, ... > Yes, this is true, it wont always work. My point was to try to make things easier to most users and most of the cases, that of course I don't know if this would be always true. The lens I have tried are identified properly with brand and model and it works pretty fine. > > Darktable/Lensfun just have no way to figure out which lens you have used > beyond the image metadata... > In my case (mostly 3rd party lenses), I have to specify the lens used 'by > hand', and in most cases distortion correction is just not needed. So I > don't > need that module activated by default. > It should only activate the correction if the lens is properly identified. I dont know if there would be many 'false posives'. In case that you dont want the correction applied for a concrete lens you can disable it for those images, or remove the lens profile if posible. Or directly don't activate the option "Apply lens correction by default". In my experience with other software I have it always active and works for most of my lenses, except one, what means that it works for 99% of the images and saves time, in my case. It was just a suggestion, maybe you are right and it is not such a good idea. I understand also that DT tries to avoid doing things 'behind de scenes' by default. But maybe could be a compromise that works. > > Remco > > > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to > [email protected] > > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
