Hi Roman,
I've included the lens info for my particular case below.
But I guess for a lot of users, lensfun might often be out of date. And
they might blame darktable for it.
The nice thing about saving a user's selection is that it's
self-correcting. If the user choses a new one, their
On Tuesday, July 19, 2016 5:29:40 PM CEST Tobias Ellinghaus wrote:
> Am Dienstag, 19. Juli 2016, 14:57:46 CEST schrieb Wolfgang Mader:
> > Hi,
>
> Hi.
>
> > most of the pixel pipeline works in CIELab. If I need the color
> > information, say, in XYZ or CIELuv, do I need to convert myself, or are
Hi,
I have created noise profiles for the Panasonic Lumix DMC G7/G70 and
uploaded the resulting tar achive to:
https://www.dropbox.com/s/zafgi8viiyqimyv/dt-noiseprofile-20160704.tar.gz?dl=0
This camera is labeled by Panasonic with two names: G70 in Germany, Swiss,
Austria and G7 everywhere
Hi,
I have a picture (Fuji XE2, XTrans, sorry :) ) with two hot (white) pixels. One
of them is perfectly corrected by the hotpixels module, the other not. If I try
to raise the strength, several other pixels (which are correct) are corrected
that shouldn't (in the red blurry flower).
Both
Am Dienstag, 19. Juli 2016, 14:57:46 CEST schrieb Wolfgang Mader:
> Hi,
Hi.
> most of the pixel pipeline works in CIELab. If I need the color information,
> say, in XYZ or CIELuv, do I need to convert myself, or are there
> ready-to-use functions?
You have to convert those values yourself.
On Tue, Jul 19, 2016 at 9:32 AM, Corey wrote:
> Hi,
Hi.
> I love darktable, but the lens I use the most is never recognized by
> automatically by the lens correction module. The result is that I have to
> manually select my lens for every photo, which not particularly
Hi,
I love darktable, but the lens I use the most is never recognized by
automatically by the lens correction module. The result is that I have
to manually select my lens for every photo, which not particularly
enjoyable.
I thought this problem could be solved if the user's lens selection