The variants apparently don't work, see:
https://github.com/lensfun/lensfun/commit/a48bc3afb87d72b48f176890e080a0b094d31b01#diff-50e22dbf0edf411c0bec00e9df83a7ae
But they shouldn't be needed in this case anyway.
Otherwise, not sure why that wouldn't work.
On Sat, May 20, 2017, at 12:24,
Hello everyone,
new Darktable user here. I've recently started shooting RAW with a great
Sony RX100 and - as a longtime Linux user - I'm learning a
bit-more-than-amateurish postprocessing.
I'm referencing the Darktable manual, which is great (thanks for the
authors efforts), and I've joined
On samedi 20 mai 2017 13:22:22 CEST Romano Giannetti wrote:
> Hi all,
>
> I have a problem with DT 2.2.4 --- I have bought a new camera, and
> trying to see if I like it --- a Panasonic TZ100. The lens is not in the
> stock lensfun database yet, but I found the entry in the lensfun
>
Thanks to all the people who tested out my problem CR2 raw file. It
seems likely that Canon has written the white balance into the exif for
such multiple-exposure files in such a way that darktable stumbles when
reading it. I have had no problems with single-exposure CR2 raw files in
I've run a few checks on openSUSE 42.2. And I made a few funny discoveries:
1. In DT, if I turn the white balance module off, the picture looks very
much ok.
2. Gwenview shows the picture ok by default.
3. Kolourpaint shows the picture ok by default.
4. Gimp shows the picture ok by default.
Hi all,
I have a problem with DT 2.2.4 --- I have bought a new camera, and
trying to see if I like it --- a Panasonic TZ100. The lens is not in the
stock lensfun database yet, but I found the entry in the lensfun
database --- reported below hoping it's correct. Now, I tried to put it
in
Same issue with darktable 2.2.4. Preview looks OK until opening the photo
in darkroom. Turning off the white balance module makes it look OK again,
or in white balance module, pushing the tint up all the way to 1.5.
On Sat, May 20, 2017 at 9:32 AM, Swee Oon wrote:
> On