if at all, such support should go into lensfun or be implemented as a
converter script (also see
http://www.mail-archive.com/[email protected]/msg00468.html).
personally i don't care too much, i hardly ever use lens correction (maybe
once or twice every 10k images for a fisheye
Why should be supporting closed source data instead of promoting the open
options so they are more complete?
El 20/07/2013 12:16, escribió:
> Currently, darktable uses lensfun to correct lens distortion,
> chromatic aberration and virgetting. However the current lensfun
> database is very limite
I have a Sony laptop (VPCSA) which can switch between the Intel
Sandybridge graphics and AMD Radeon 6600M graphics card. I have 13.101
Radeon drive installed from the AMD website which enables me to switch
between the Radeon and Intel Sandybridge graphics card. Generally I
prefer the Sandybridg
sorry for the delay, looks good to me, and works as advertised in a quick
test. thanks for working this out!
pushed to master,
-jo
On Tue, Jul 2, 2013 at 1:20 AM, Yari Adán Petralanda wrote:
> Hi!
>
> Sorry for the late response. I reworked the patch to address your comments:
>
> - I removed I
Currently, darktable uses lensfun to correct lens distortion,
chromatic aberration and virgetting. However the current lensfun
database is very limited and it does not have many lens such as the
Canon 18-135mm zoom. Yet for a novice, it is very tedious to create a
lens profile manually, and mista
