Re: [darktable-dev] PSA: Does anyone still use gcc-4.8/4.9 ?

2017-04-07 Thread Michal Babej
On Tue, 28 Mar 2017 19:02:24 +0300
Roman Lebedev  wrote:

> That is actually the very important point - running git master of
> some software on supported Enterprise distribution. Does anyone here
> actually do that?

I did that with Darktable for a while, but it's an uphill battle, and
eventually you have to build your own glib2/gtk/everything... i've
given up on it, long time ago.

> New distro version will contain
> newer gcc, and will be able to update darktable.

Actually RHEL7 and Centos7 do have new compilers (gcc 5.3 and 6.2):

https://www.softwarecollections.org/en/scls/rhscl/devtoolset-6/

... so gcc is not a problem, the rest likely will be (sooner or later).

Cheers,
-- mb
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org



Re: [darktable-dev] Lens correction based on EXIF data on Sony cameras

2017-04-07 Thread Kelvie Wong
On the plus side, distortion is not, and CA is relatively easy to correct.

Vignetting is hard to manually correct with the current darktable modules,
however, without doing some type of stacking of vignette modules or
exposure with circular masks.

I have a theory that with the corrections on, the vignetting will still be
under corrected by a constant amount (independent of lens), but I'd need to
do more tests.

On Fri, Apr 7, 2017, 01:09 Matthias Andree,  wrote:

> Am 07.04.2017 um 09:38 schrieb Heiko Bauke:
> > Hi,
> >
> > Am 05.04.2017 um 07:33 schrieb Kelvie Wong:
> >> I just realized that on my Sony a7R II (and this probably applies to all
> >> of the cameras in this series, probably even the NEX), if you have
> >> certain camera settings, some lens corrections are baked into the ARW
> >> files (Sony's raw format) -- that is the bit values appear to change,
> >> not just the metadata.
> >
> > just for the record: This seems to be a common feature of Sony
> > cameras. If I understand the settings menu correctly, also the Sony
> > Alpha 6300 can apply in-camera vignetting correction to raw files.
> > This feature is turned on, when default factory settings are applied.
> > The pictures, which have been utilized to generate lens correction
> > data in liblensfun, have actually been taken with Sony Alpha cameras.
> > Thus, it would be interesting to know, if liblensfun data is based on
> > raw raw files or on raw files with in-camera vignetting correction.
>
> The lensfun profiling instructions tell people to switch those
> corrections off, but it might be necessary to re-profile everything
> paying heed to the settings; there may have to be two settings for each.
> I will recheck the images I've used for my profile parts in the lensfun
> database.
>
> OTOH, some people expect "RAW" images to be free of all preprocessing.
>
> And, finally, if the camera always bakes a certain correction into the
> raw images regardless of settings (or because it won't permit you to
> switch a certain correction "off") then of course the lensfun data will
> have been produced based on pre-processed RAW.
> ___
> darktable developer mailing list
> to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
> --

-- 
Kelvie Wong

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Clipboard is not available between darktable and lighttable modes

2017-04-07 Thread Alexander Rabtchevich
Hello

If some history items are copied with Ctrl+Shift+C in lighttable mode, the clipboard cannot be pasted in the darkroom mode. Current git.

 

With respect,

Alexander Rabtchevich

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org





Re: [darktable-dev] Lens correction based on EXIF data on Sony cameras

2017-04-07 Thread Matthias Andree
Am 07.04.2017 um 09:38 schrieb Heiko Bauke:
> Hi,
>
> Am 05.04.2017 um 07:33 schrieb Kelvie Wong:
>> I just realized that on my Sony a7R II (and this probably applies to all
>> of the cameras in this series, probably even the NEX), if you have
>> certain camera settings, some lens corrections are baked into the ARW
>> files (Sony's raw format) -- that is the bit values appear to change,
>> not just the metadata.
>
> just for the record: This seems to be a common feature of Sony
> cameras. If I understand the settings menu correctly, also the Sony
> Alpha 6300 can apply in-camera vignetting correction to raw files. 
> This feature is turned on, when default factory settings are applied. 
> The pictures, which have been utilized to generate lens correction
> data in liblensfun, have actually been taken with Sony Alpha cameras. 
> Thus, it would be interesting to know, if liblensfun data is based on
> raw raw files or on raw files with in-camera vignetting correction. 

The lensfun profiling instructions tell people to switch those
corrections off, but it might be necessary to re-profile everything
paying heed to the settings; there may have to be two settings for each.
I will recheck the images I've used for my profile parts in the lensfun
database.

OTOH, some people expect "RAW" images to be free of all preprocessing.

And, finally, if the camera always bakes a certain correction into the
raw images regardless of settings (or because it won't permit you to
switch a certain correction "off") then of course the lensfun data will
have been produced based on pre-processed RAW.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org