Re: [darktable-user] lensfun priority troubles with Ubuntu 18.04
Am Tue, 22 May 2018 10:03:35 -0400 schrieb Šarūnas : > On 2018-05-21 15:50, Аl Воgnеr wrote: > > Am Mon, 21 May 2018 14:41:41 -0400 > > schrieb Šarūnas : > >> There is no correction data for Sigma 70-300mm F4-5.6 DG OS on a > >> "full-frame" sensor in lensfun (not in github calibration > >> repository). > > > > Yes, and therefore I added a line: > > > > > > Sigma > > Sigma 70-300mm f/4-5.6 DG Macro > > If I understand this correctly, the matching will still be done for > the above line. The only thing that the lang line does is change the > display name of the matched lens for given locale... > > > Sigma 70-300mm F4-5.6 DG OS Sorry, if I write "maybe". If I do this the correction works, otherwise not. > The only way to have a lens alias for an optically identical one is to > duplicate the entire element and then change the in it. Not sure, I discussed this already in the lensfun-list. It should, but my experience is, that the "trick" with helped very often, but not always. > If you'd like to have that, you should probably raise an issue on > github/lensfun, which is used for the correction database maintenance. This thread was originally started as crossposting to the lensfun-list and the lensfun people have subscribed the list. If I am pretty sure, that it is correct, what I am writing and if I detect a bug, I will send them a mail of course. In the meantime I have some lenses corrected, which did not work before. I do not use "update" anymore and then it works in ~/.local/share/lensfun if I do not use a version. I decided to create an own file there for every lens which doesn't work. I am still fighting with the Pentax DFA 24-70. It doesn't help to use the correction file from 16.04 (which worked). My next step will be a local exiv2-info-file. Al darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] lensfun priority troubles with Ubuntu 18.04
On 2018-05-21 15:50, Аl Воgnеr wrote: > Am Mon, 21 May 2018 14:41:41 -0400 > schrieb Šarūnas : >> There is no correction data for Sigma 70-300mm F4-5.6 DG OS on a >> "full-frame" sensor in lensfun (not in github calibration repository). > > Yes, and therefore I added a line: > > > Sigma > Sigma 70-300mm f/4-5.6 DG Macro If I understand this correctly, the matching will still be done for the above line. The only thing that the lang line does is change the display name of the matched lens for given locale... > Sigma 70-300mm F4-5.6 DG OS The only way to have a lens alias for an optically identical one is to duplicate the entire element and then change the in it. If you'd like to have that, you should probably raise an issue on github/lensfun, which is used for the correction database maintenance. -- Šarūnas Burdulis math.dartmouth.edu/~sarunas signature.asc Description: OpenPGP digital signature
Re: [darktable-user] local contrast → bug or feature?
On 22/05/18 11:34, Remco Viëtor wrote: On mardi 22 mai 2018 10:34:09 CEST Tobias Ellinghaus wrote: Am Dienstag, 22. Mai 2018, 07:31:35 CEST schrieb Timur Irikovich Davletshin: yes, that seems to be the case. I guess the 120% are a better default, even if it makes the module not a NOP by default. Comments? Unless you want to stick to a policy of "default = NOP", I don't see a problem with defaults different from NOP where it makes sense. I rather like having defaults that show the effect of the module for things like "local contrast", "shadows/highlights", "Velvia", etc. Those are modules where the effects go from "none" to "too strong". Of course, for "exposure" and such, neutral (NOP) values are the sensible default as any other choice will probably be the wrong way half the time... I agree with Remco. Moreover, if all modules had the default = NOP, the ON/OFF status would be redundant (modulo optimization thing). When available, an "auto" mode could be a nice default. Romano -- -- Romano Giannetti http://www.rgtti.com/ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] local contrast → bug or feature?
On mardi 22 mai 2018 10:34:09 CEST Tobias Ellinghaus wrote: > Am Dienstag, 22. Mai 2018, 07:31:35 CEST schrieb Timur Irikovich Davletshin: > > Hello everybody! > > Hi, > > > Reseting local contrast module parameters results in 120% detail and > > local Laplacian filter but double-clicking detail parameter to reset it > > gives 100% (both for loc. Laplacian and bilateral). Other modules (as > > far as I remember) in both cases give same value. > > yes, that seems to be the case. I guess the 120% are a better default, even > if it makes the module not a NOP by default. Comments? > Unless you want to stick to a policy of "default = NOP", I don't see a problem with defaults different from NOP where it makes sense. I rather like having defaults that show the effect of the module for things like "local contrast", "shadows/highlights", "Velvia", etc. Those are modules where the effects go from "none" to "too strong". Of course, for "exposure" and such, neutral (NOP) values are the sensible default as any other choice will probably be the wrong way half the time... Remco darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] local contrast → bug or feature?
On Tue, 2018-05-22 at 10:34 +0200, Tobias Ellinghaus wrote: > Am Dienstag, 22. Mai 2018, 07:31:35 CEST schrieb Timur Irikovich > Davletshin: > > Hello everybody! > > Hi, > > > Reseting local contrast module parameters results in 120% detail > > and > > local Laplacian filter but double-clicking detail parameter to > > reset it > > gives 100% (both for loc. Laplacian and bilateral). Other modules > > (as > > far as I remember) in both cases give same value. > > yes, that seems to be the case. I guess the 120% are a better > default, even if > it makes the module not a NOP by default. Comments? > > > Timur. > > Tobias Personally I prefer to use less subtle settings like 80-100%, but effect is not so easy to notice and it may confuse some users. So probably I agree that 120% is a better starting position. Timur. darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
Re: [darktable-user] local contrast → bug or feature?
Am Dienstag, 22. Mai 2018, 07:31:35 CEST schrieb Timur Irikovich Davletshin: > Hello everybody! Hi, > Reseting local contrast module parameters results in 120% detail and > local Laplacian filter but double-clicking detail parameter to reset it > gives 100% (both for loc. Laplacian and bilateral). Other modules (as > far as I remember) in both cases give same value. yes, that seems to be the case. I guess the 120% are a better default, even if it makes the module not a NOP by default. Comments? > Timur. Tobias signature.asc Description: This is a digitally signed message part.
