Re: [darktable-dev] Adjustable panel width removal

[Jean-Luc Coulon (f5ibh)]

Le sam. 4 janv. 2020 à 09:53, Timur Irikovich Davletshin <
timur.davlets...@gmail.com> a écrit :

> Wow, I'm not used to this approach in darktable.
>
lot of surprises !

>
> Best wishes for this year!
>
The same for you ;)

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

Re: [darktable-dev] Adjustable panel width removal

[Jean-Luc Coulon (f5ibh)]

Hi,
Because you can now adjust it from the gui by grabbing the limit and move
it around...

J-L

Le sam. 4 janv. 2020 à 09:19, Timur Irikovich Davletshin <
timur.davlets...@gmail.com> a écrit :

> Good Saturday morning dear developers!
>
> What is the reason of removing adjustable panel width in recent commits
> both to master and 3.0 branches? Was something broken?
>
> Thanks in advance,
>
> Timur.
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
>

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

Re: [darktable-dev] [note] in darktable everything is written in lower case -- update translation

[Jean-Luc Coulon (f5ibh)]

Hi,
It is difficult to say that it is a "rule".
In French, for instance, the uppercase at the beginning of a sentence is
"orthographic".
This means that the lack of such an uppercase letter violates an
orthographic rule.
It is the same, BTW (and in French), for the diacritics on uppercase
letters.

So, maybe there is this kind of a *rule* in other languages also.

Regards

Jean-Luc

Le mer. 11 déc. 2019 à 11:25, Pascal Obry  a écrit :

> Hi Pierre,
>
> > I will update the German translation accordingly in the next few days.
>
> Note that this rule is for the English strings. I suppose a translation
> can be made as you like it. We cannot impose a style for all languages.
> It was also discussed to change the rule and actually use mixed-case in
> the interface. But that would be a huge work !
>
> Regards,
>
> --
>   Pascal Obry /  Magny Les Hameaux (78)
>
>   The best way to travel is by means of imagination
>
>   http://www.obry.net
>
>   gpg --keyserver keys.gnupg.net --recv-key F949BD3B
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
>

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

[darktable-dev] Parametric mask and associated GUI

[Jean-Luc Coulon (f5ibh)]

Hi,
When we use the parametric mask, we can select L a b C h.
There is an associated GUI which displays a "ribbon" with a grey scale or a
colour gradient.
If we use the picker to select a value/colour in the image, it is fine for
all but for the "h" entry.
With the h entry, the colour "ribbon" use very subdued colours and the
picked value is marked with a thin white vertical bar.
This does not give enough contrast for this value to be easily seen.

Is it possible to change the colour of this bar in this case (blank would
be nice) and/or increase the line thickness?

Regards

Jean-Luc

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

Re: [darktable-dev] darktable 3.0 - let's start translations

[Jean-Luc Coulon (f5ibh)]

Hi,
There is another way with gettext to give information to the translators:
in the source code, you add a comment with /// (triple slash) and it will
appear in the .pot / .po files/
e.g.
///TRANSLATORS: this applies to CIRCLE
g_strlcpy(a->name, _("[CIRCLE] change size"), sizeof(a->name));

with give the following in the pot file:

#. TRANSLATORS: this applies to CIRCLE#:
src/develop/masks/mask.c:293msgid "[CIRCLE] change size"msgstr ""

Regards

Jean-Luc


Le dim. 3 nov. 2019 à 01:04, Pascal Obry  a écrit :

>
> Hello Pierre,
>
> > I have started with the translation into German.
> > In the po.file I will fine some entries:
> >
> > [CIRCLE] change size
> > [BRUSH] change opacity
> > ...
> >
> > Can I also translate the part in the square bracket or are they control
> > commands for darktable?
>
> No, not needed. The word in square bracket is the context in which the
> string is used. It is only a hint to help translating the string
> properly.
>
> Cheers,
>
> --
>   Pascal Obry /  Magny Les Hameaux (78)
>
>   The best way to travel is by means of imagination
>
>   http://www.obry.net
>
>   gpg --keyserver keys.gnupg.net --recv-key F949BD3B
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
>

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

Re: [darktable-dev] 64-stroke limit in "spot removal" module?

[Jean-Luc Coulon (f5ibh)]

Hi,
I also experienced this.
The workaround is to open a second instance of the module.

Regards

Jean-Luc

Le jeu. 29 août 2019 à 06:44, August Schwerdfeger 
a écrit :

> Recently when editing a dusty film scan I tried to use the "spot removal"
> module to take care of the dust. After adding 64 strokes, I discovered that
> any further strokes were no-ops, producing no visible change to the image
> when added. I then created a second instance of the module; strokes added
> there worked as expected.
>
> Is there an implicit limit of 64 strokes in the "spot removal" module?
>
> --
> August Schwerdfeger
> aug...@schwerdfeger.name
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>

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

Re: [darktable-dev] Re: Lens correction behaviour depending of correction choice

[Jean-Luc Coulon (f5ibh)]

Git master, from the "about": 2.7.0+1113~g248fbccd6-dirty

J-L

Le sam. 4 mai 2019 à 21:42, Patrick Shanahan  a écrit :

> * Jean-Luc Coulon (f5ibh)  [05-04-19 15:25]:
> > OK, so :
> >  1 - if I left the default scale value to 1.028 and vignetting only and I
> > switch on/off the module, then the image "move" (cropped / resized) while
> > switching the module while the scale stay at 1.028.
> >
> > 2  - if I set the scale to 1.000 and vignetting only and I switch on/off
> > the module, then the image stay with the same aspect (dimensions) on the
> > screen.
> >
> > There is also an other issue (maybe cosmetic). If the scale factor is
> 1.028
> > (default), when the module is active, I get "only vignetting" in the
> > "correction done" field. If I set the scale factor to 1.000, the field
> > "correction done" is empty always but the first time I switch the module
> > on/off (while the correction is applied).
> >
> > BTW,  I forgot to tell I use the git version of darktable.
> >
> > J-L
> >
> > Le sam. 4 mai 2019 à 20:41, Torsten Bronger <
> bron...@physik.rwth-aachen.de>
> > a écrit :
> >
> > > Hallöchen!
> > >
> > > Jean-Luc Coulon (f5ibh) writes:
> > >
> > > > When I apply the correction it is set automatically to 1.028.  I
> > > > can manually set it to 1.000.  Then It stay adjusted to this
> > > > value.
> > > >
> > > > (I'm not sure I've understood the question correctly).
> > >
> > > You said:
> > >
> > > I get also some kind distorsion correction
> > >
> > > My question is that you still see this when you set scaling to 1.
> > > If you then switch the lens correction module off and on, does the
> > > image change apart from vignetting correction?
> > >
> > > Tschö,
> > > Torsten.
> > >
> > > --
> > > Torsten Bronger
> > >
> > >
> ___
> > > darktable developer mailing list
> > > to unsubscribe send a mail to
> > > darktable-dev+unsubscr...@lists.darktable.org
> > >
> > >
> >
> >
> ___
> > darktable developer mailing list
> > to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
> >
>
> the "git" version is constantly changing.  you will need to specify the
> version number and master or stable.
>
> --
> (paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
> http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
> Registered Linux User #207535@ http://linuxcounter.net
> Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode
> ___
> darktable developer mailing list
> to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
>

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

Re: [darktable-dev] Re: Lens correction behaviour depending of correction choice

[Jean-Luc Coulon (f5ibh)]

OK, so :
 1 - if I left the default scale value to 1.028 and vignetting only and I
switch on/off the module, then the image "move" (cropped / resized) while
switching the module while the scale stay at 1.028.

2  - if I set the scale to 1.000 and vignetting only and I switch on/off
the module, then the image stay with the same aspect (dimensions) on the
screen.

There is also an other issue (maybe cosmetic). If the scale factor is 1.028
(default), when the module is active, I get "only vignetting" in the
"correction done" field. If I set the scale factor to 1.000, the field
"correction done" is empty always but the first time I switch the module
on/off (while the correction is applied).

BTW,  I forgot to tell I use the git version of darktable.

J-L

Le sam. 4 mai 2019 à 20:41, Torsten Bronger 
a écrit :

> Hallöchen!
>
> Jean-Luc Coulon (f5ibh) writes:
>
> > When I apply the correction it is set automatically to 1.028.  I
> > can manually set it to 1.000.  Then It stay adjusted to this
> > value.
> >
> > (I'm not sure I've understood the question correctly).
>
> You said:
>
> I get also some kind distorsion correction
>
> My question is that you still see this when you set scaling to 1.
> If you then switch the lens correction module off and on, does the
> image change apart from vignetting correction?
>
> Tschö,
> Torsten.
>
> --
> Torsten Bronger
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
>

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

Re: [darktable-dev] Re: Lens correction behaviour depending of correction choice

[Jean-Luc Coulon (f5ibh)]

Hi,

When I apply the correction it is set automatically to 1.028.
I can manually set it to 1.000.
Then It stay adjusted to this value.

(I'm not sure I've understood the question correctly).

J-L

Le sam. 4 mai 2019 à 12:51, Torsten Bronger 
a écrit :

> Hallöchen!
>
> Jean-Luc Coulon (f5ibh) writes:
>
> > Hi,
> >
> > Ah yes... well no, it is at 1.028.
>
> I don't know where exactly this value comes from but Lensfun by
> default scales slightly when using its autoscale facility.  This is
> because rounding errors should be eliminated.  However, Lensfun
> scales by 1.001 (1.002 with TCA).  Possibly 1.028 was the value in
> older Lensfun versions.  But I can't tell for sure.
>
> And if you set this to exactly 1, do you still see distortions?
>
> Tschö,
> Torsten.
>
> --
> Torsten Bronger
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
>

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

Re: [darktable-dev] Re: Lens correction behaviour depending of correction choice

[Jean-Luc Coulon (f5ibh)]

Hi,

Ah yes... well no, it is at 1.028.

This is the default value it gets everytime if I click the "default
parameters" icon or double click the scale.

J-L

Le sam. 4 mai 2019 à 08:36, Torsten Bronger 
a écrit :

> Hallöchen!
>
> Jean-Luc Coulon (f5ibh) writes:
>
> > If I use the lens correction and I ask for "vignetting only", I
> > get also some kind distorsion correction, or at least I can see
> > the image is resized/cropped. This is not exactly the same as when
> > I ask for distorsion correction.
> >
> > In fact, I soon as I select the module, even if distorsions are
> > set to "none", I get "something".
>
> Is the scale slider still at "1" after having activated the
> corrections?
>
> Tschö,
> Torsten.
>
> --
> Torsten Bronger
>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
>

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

[darktable-dev] Lens correction behaviour depending of correction choice

[Jean-Luc Coulon (f5ibh)]

Hi,

If I use the lens correction and I ask for "vignetting only", I get also
some kind distorsion correction,  or at least I can see the image is
resized/cropped. This is not exactly the same as when I ask for distorsion
correction.

In fact, I soon as I select the module, even if distorsions are set to
"none", I get "something".

Regards

Jean-Luc

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

Re: [darktable-dev] do not use dt 2.7

[Jean-Luc Coulon (f5ibh)]

Le sam. 30 mars 2019 à 10:48, Pascal Obry  a écrit :

>
> This should be fixed now. As usual with master branch make sure the db are
> backup!


It seems to be right with the images where I had problems.

About the database, why is its default location in .config ? Shouldn't it
be in something like .local/share as usual fot this kind of data?

Regards

Jean-Luc

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

Re: [darktable-dev] do not use dt 2.7

[Jean-Luc Coulon (f5ibh)]

I get the problem but only when the image is rotated according to the exif
(orientation module).
A normal lanscape image is displayed normally.
A portrait image is rotated 180°

J-L


Le sam. 30 mars 2019 à 00:53, Patrick Shanahan  a écrit :

> * Patrick Shanahan  [03-29-19 19:36]:
> > * Pascal Obry  [03-29-19 19:11]:
> > >
> > > Please see:
> > >
> > > https://github.com/darktable-org/darktable/issues/2310
> > >
> > > Wait for a solution to be proposed for this.
> >
> > I do not see this with git829.9c9ed7e64-1090 on openSUSE Tumbleweed
> > 20190327
> > or I have failed to set the conditions which result in this.
>
> disregard, sorry.
>
> --
> (paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
> http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
> Registered Linux User #207535@ http://linuxcounter.net
> Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode
> ___
> darktable developer mailing list
> to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
>

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

[darktable-dev] Fwd: lens correction and shape of the masks

[Jean-Luc Coulon (f5ibh)]

Anyone with a fix or a workaround for that please?

Thanks

Jean-Luc

-- Forwarded message -
From: Jean-Luc Coulon (f5ibh) 
Date: mer. 6 mars 2019 à 18:16
Subject: lens correction and shape of the masks
To: darktable forum 


 Hi
I've used a 14 mm Samyang lens on a Canon EOS 6D MkII to shoot the Milky
Way.
I've applied the lens corrections from darktable (in this case, distorsion
is relevant).

If I use thereafter a drawn mask with a gradient, the shape of the gradient
is curved the opposite way the correction is done.

i.e. the distorsion is basically a barrel.
And the curve of the gradient depends where I put it: it is straight in the
middle and concave in the lower or upper part of the picture.

This is quite annoying because I'm always chasing the right position of the
gradient.

Jean-Luc

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

Re: [darktable-dev] Lens correction with FF lenses used on APS-C

[Jean-Luc Coulon (f5ibh)]

In the database (in liblensfun-data package, file slr-canon.xml for Canon),
you will find the various bodies / lenses.
For each lens, there is a comment like:
 
This allows you to know how the lens was calibrated.

J-L

Le sam. 23 févr. 2019 à 19:31, David Vincent-Jones  a
écrit :

> On my system the camera and correct lens is found by default  which is
> what I want!
>
> David
> On 2019-02-23 9:12 a.m., Sturm Flut wrote:
>
> Hi,
>
> Am 23.02.19 um 16:34 schrieb Florian W:
>
> Thanks for your answers guys.
>
> Simon, I'm curious to know why to you it's not the best idea ?
>
> (oversimplifying it a bit)
>
> Full-frame lenses are designed to deliver their full sharpness across
> the whole full-frame image circle. If I put a full-frame lens on my
> APS-C D7100, I am basically expecting it to deliver 24 megapixels within
> the smaller APS-C image circle the sensor is cropping out. That means I
> expect the lens to deliver about 24*2,25 = 54 megapixels over the whole
> full-frame image circle. Which not that many standard lenses will do.
>
> If put my standard 24-70/2.8 on a Nikon D850 and (let's say) it only
> delivers 40 megapixels of actual resolution instead of the ~46 the
> sensor wants, that's not going to be a catastrophe. If I put it on a
> camera with a lower resolution sensor, e.g. the 24 megapixel sensor in
> the D750, there is zero problem. But if I put the same lens on the
> D7100, the cropped area will only get around 40 / 2,25 = 17 megapixels.
> That's suddenly 30% less than what the sensor needs. And not every lens
> will even deliver these 40 megapixels. Good APS-C and especially
> Micro-Four-Thirds lenses are expensive and hard to make because they
> have to be very sharp within the smaller image circle.
>
> Prime lenses are usually sharper to begin with, so with your 50/1.8 and
> 28/2.8 it might not be that much of an issue. But I can clearly see the
> problem with my 24-70/2.8, and especially with the good old 70-300/4.5-5.6.
>
> cheers,
> Simon
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>

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

Re: [darktable-dev] Rotate Tool

[Jean-Luc Coulon (f5ibh)]

Hi,
The second menu entry in crop and rotate module is "angle".
You choose an angle (slider or keyboard) entry or you can draw a line on
the image (right-clic then move), this line will be the horizontal or the
vertical of the picture that will be rotated accordingly. This is explained
in the manual.

Orientation is for portrait / landscape orientation of the picture (or
upside-down), it rotates the image by 90° steps.

Jean-Luc

Le mer. 26 déc. 2018 à 15:33, DavidJr.  a écrit :

> Hello!
>
> I just installed the new 2.6 version of darktable and was curious as to
> why the "rotate" tool was not listed under the "crop and rotate" module?
> Instead it is in its own module called "orientation".  Its seemed a little
> out of place when there is no rotate option in the "crop and rotate" module.
>
> Thanks!
>
> David Landis
>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>

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

Re: [darktable-dev] Translation issues

[Jean-Luc Coulon (f5ibh)]

Le dim. 16 déc. 2018 à 01:55, Jeronimo Pellegrini  a
écrit :

> [ ... ]
> - "color checker patch"
>

A "color checker" is a target with a set of small squares of different
colours.
patch is the name these squares are called.

This is the meaning in this string : a sample square (patch)  from a target
(color checker).

Regards

Jean-Luc

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

Re: [darktable-dev] DarkTable

[Jean-Luc Coulon (f5ibh)]

Hi,

The Canon EOS 760D is supported by the latest version of DT (v 2.4.1).
Probably you are using an old version.

Jean-Luc

2018-02-15 16:47 GMT+01:00 Andreas Klemmed :

> Sehr geehrte Damen und Herren, seid langer Zeit benutze ich Darktable um
> meine Bilder von meiner Nikon Kamera zu bearbeiten. Es war für mich
> immer DAS Top-Programm überhaupt! Jetzt musste ich jedoch auf Canon
> umsteigen und habe eine EOS 760 D. Leider kann ich die Bilder von dieser
> Kamera nicht mehr mit DT bearbeiten. Anscheinend wird diese Kamera nicht
> von DT unterstützt. Wird es noch ein Update für diese Kamera geben, bzw.
> eine neuere Version von Darktable erscheinen, wo diese Probleme nicht
> mehr auftreten? Ich fände es mehr als bedauerlich, wenn ich in Zukunft
> nicht mehr mit DT arbeiten könnte. Ich würde mich auf eine Antwort von
> Ihnen sehr freuen und verbleibe, mit freundlichen Grüßen.
>
> Andreas Klemmed
>
> 
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@
> lists.darktable.org
>
>

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

Re: [darktable-dev] 2.4.1 Ubuntu

[Jean-Luc Coulon (f5ibh)]

Hi,

Linux exists in many flavours. Ubuntu is not the only one.
I suppose the Ubuntu maintainer has other things to do for the moment...
There is one  MAC release (BTW the guys who are using MAC has been
complaining a long time not having 2.4.0)
There is one Windows release
For Linux, there is:
- Debian (the only real distribution
- Ubuntu
- Gentoo
- Fedora
- Mageia
- ArchLinux
- [add many]

And it is quite easy to build your own from source.

Regards

Jean-Luc

2018-01-24 20:24 GMT+01:00 steve :

> Thanks so much for the latest 2.4.1 release, which I am enjoying on my
> Mac book and hoping to see it in the ubuntu PPA's soon.   As a small
> comment, I think it is pretty amazing that a new version of Darktable is
> released for Windows and Mac BEFORE it reaches the ubuntu release and
> unstable PPA's.
>
> -Steve
>
> 
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@
> lists.darktable.org
>
>

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

Re: [darktable-dev] 2.4.0 build for MacOS?

[Jean-Luc Coulon (f5ibh)]

Hi,

If you don't live in a cave, you should be aware that there have been
already a discussion et some comprehensive explanations about this matter.
In short: the person who does the Mac OX image is on vacation... And
(probably) he will do the job when back.
But, as always, as it is done on a voluntary basis, there is never any
warranty, even... well... you know.

Regards

Jean-Luc

2018-01-16 19:39 GMT+01:00 Neil Schemenauer :

> Any ideas why there is no current build for MacOS?  If you go to the
> home page and follow the install link, you get 2.2.5.  If you go to
> the github release page, there is no DMG image for 2.4.0.
>
> BTW, the "Choose your OS" section of the install page is a little
> too cute for its own good, IMHO.  I have to hover over the images
> to figure out what they mean.  It would be better if there was text
> above or below each image.  The average computer user will not
> recognize the logos.
>
> Regards,
>
>   Neil
> 
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@
> lists.darktable.org
>
>

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

Re: [darktable-dev] Wrong lens detected

[Jean-Luc Coulon (f5ibh)]

The but I've opened is now closed.
There is an explanation that you can see here:
http://dev.exiv2.org/issues/1328#change-6131

Basically, you should add the following in your .exiv2 file (or add it if
it already exists):

[canon]
197=Sigma 18-300mm f/3.5-6.3 DC Macro OS HS

I've tried this on the file with the SIgma 18-300:
 exiv2 -g Lens -pt /extra/exiv2-bug-1328/IMG_4575.CR2
Exif.CanonCs.LensTypeShort   1  Sigma 18-300mm
f/3.5-6.3 DC Macro OS HS
Exif.CanonCs.LensShort   3  18.0 - 300.0 mm
Exif.Canon.LensModel Ascii  74  18-300mm
Exif.Photo.LensSpecification Rational4  18/1 300/1 0/1
0/1
Exif.Photo.LensModel Ascii   9  18-300mm
Exif.Photo.LensSerialNumber  Ascii  11  00

And it works also in darktable.

Regards

Jean-Luc


2017-12-06 21:50 GMT+01:00 Marc Mascré <li...@mascre.fr>:

> Ho nice !
>
> Thanks a lot for your help.
>
> If I can help please let me know.
>
> Marc
>
>
> Le 06/12/2017 à 11:12, Jean-Luc Coulon (f5ibh) a écrit :
>
> Hi,
>
> I've reported a bug for this problem to exiv2.
> See: http://dev.exiv2.org/issues/1328
>
> Regards
>
> Jean-Luc
>
> 2017-12-05 22:12 GMT+01:00 Jean-Luc Coulon (f5ibh) <
> jean.luc.cou...@gmail.com>:
>
>> Well, with exiftool, I get :
>> Lens Type   : Canon EF 75-300mm f/4-5.6 IS USM or
>> Sigma Lens
>> ...
>> ...
>> Lens Info   : 18-300mm f/0
>> Lens Model  : 18-300mm
>> Lens Serial Number  : 00
>> Lens: 18.0 - 300.0 mm
>> Lens ID : Sigma 18-300mm f/3.5-6.3 DC Macro OS HS
>> Lens: 18.0 - 300.0 mm (35 mm equivalent:
>> 28.0 - 466.3 mm)
>>
>> which seems to be correct...
>>
>> with exiv2 :
>> Exif.CanonCs.LensTypeShort   1  Canon EF
>> 75-300mm f/4-5.6 IS USM
>> Exif.CanonCs.LensShort   3  18.0 - 300.0
>> mm
>> Exif.Canon.LensModel Ascii  74  18-300mm
>> Exif.Photo.LensSpecification Rational4  18/1 300/1
>> 0/1 0/1
>> Exif.Photo.LensModel Ascii   9  18-300mm
>> Exif.Photo.LensSerialNumber  Ascii  11  00
>>
>> which is confusing because the Type is only on the Canon, not "or Sigma"
>> but other lens data are related to the Sigma.
>>
>> In darktable, it is wrong also because it is the  LensType which is
>> reported.
>>
>> My version of darktable is the latest git/trunk version
>>
>> Jean-Luc
>>
>>
>> 2017-12-05 20:40 GMT+01:00 Marc Mascré <li...@mascre.fr>:
>>
>>> I don't know.
>>>
>>> To confirm that the problem come from the file and not my system, if you
>>> whant, you can download the file here :
>>> http://documents.mascre.fr/IMG_4575.CR2
>>> It could be take some time, it is self hosted.
>>>
>>>
>>>
>>> Le 05/12/2017 à 08:49, Jean-Luc Coulon (f5ibh) a écrit :
>>>
>>> It seems that some informations are from the right lens and other for
>>> the wrong one.
>>> Probably these informations ARE in the file.
>>> Maybe Sigma is trying to fool the Canon body to get some optical
>>> corrections from it?
>>>
>>> 2017-12-04 22:43 GMT+01:00 Marc Mascré <li...@mascre.fr>:
>>>
>>>> That is completely crazy
>>>>
>>>> # exiv2 -pt IMG_4575.CR2 | grep Lens
>>>> Exif.CanonCs.LensTypeShort   1  Canon EF
>>>> 75-300mm f/4-5.6 IS USM
>>>> Exif.CanonCs.Lens        Short   3  18.0 -
>>>> 300.0 mm
>>>> Exif.Canon.LensModel Ascii  74  18-300mm
>>>> Exif.Photo.LensSpecification Rational4  18/1 300/1
>>>> 0/1 0/1
>>>> Exif.Photo.LensModel Ascii   9  18-300mm
>>>> Exif.Photo.LensSerialNumber  Ascii  11  00
>>>>
>>>> exiftool version here is 10.45 I can try to update it but I became to
>>>> ask myself if the wrong lens type is not write in the .CR2 by the camera.
>>>>
>>>> Marc
>>>>
>>>>
>>>>
>>>> Le 04/12/2017 à 16:36, Jean-Luc Coulon (f5ibh) a écrit :
>>>>
>>>> Can you try:
>>

Re: [darktable-dev] Wrong lens detected

[Jean-Luc Coulon (f5ibh)]

Hi,

I've reported a bug for this problem to exiv2.
See: http://dev.exiv2.org/issues/1328

Regards

Jean-Luc

2017-12-05 22:12 GMT+01:00 Jean-Luc Coulon (f5ibh) <
jean.luc.cou...@gmail.com>:

> Well, with exiftool, I get :
> Lens Type   : Canon EF 75-300mm f/4-5.6 IS USM or
> Sigma Lens
> ...
> ...
> Lens Info   : 18-300mm f/0
> Lens Model  : 18-300mm
> Lens Serial Number  : 00
> Lens: 18.0 - 300.0 mm
> Lens ID : Sigma 18-300mm f/3.5-6.3 DC Macro OS HS
> Lens: 18.0 - 300.0 mm (35 mm equivalent: 28.0
> - 466.3 mm)
>
> which seems to be correct...
>
> with exiv2 :
> Exif.CanonCs.LensTypeShort   1  Canon EF
> 75-300mm f/4-5.6 IS USM
> Exif.CanonCs.LensShort   3  18.0 - 300.0
> mm
> Exif.Canon.LensModel Ascii  74  18-300mm
> Exif.Photo.LensSpecification Rational4  18/1 300/1
> 0/1 0/1
> Exif.Photo.LensModel Ascii   9  18-300mm
> Exif.Photo.LensSerialNumber  Ascii  11  00
>
> which is confusing because the Type is only on the Canon, not "or Sigma"
> but other lens data are related to the Sigma.
>
> In darktable, it is wrong also because it is the  LensType which is
> reported.
>
> My version of darktable is the latest git/trunk version
>
> Jean-Luc
>
>
> 2017-12-05 20:40 GMT+01:00 Marc Mascré <li...@mascre.fr>:
>
>> I don't know.
>>
>> To confirm that the problem come from the file and not my system, if you
>> whant, you can download the file here :
>> http://documents.mascre.fr/IMG_4575.CR2
>> It could be take some time, it is self hosted.
>>
>>
>>
>> Le 05/12/2017 à 08:49, Jean-Luc Coulon (f5ibh) a écrit :
>>
>> It seems that some informations are from the right lens and other for the
>> wrong one.
>> Probably these informations ARE in the file.
>> Maybe Sigma is trying to fool the Canon body to get some optical
>> corrections from it?
>>
>> 2017-12-04 22:43 GMT+01:00 Marc Mascré <li...@mascre.fr>:
>>
>>> That is completely crazy
>>>
>>> # exiv2 -pt IMG_4575.CR2 | grep Lens
>>> Exif.CanonCs.LensTypeShort   1  Canon EF
>>> 75-300mm f/4-5.6 IS USM
>>> Exif.CanonCs.LensShort   3  18.0 -
>>> 300.0 mm
>>> Exif.Canon.LensModel Ascii  74  18-300mm
>>> Exif.Photo.LensSpecification Rational4  18/1 300/1
>>> 0/1 0/1
>>> Exif.Photo.LensModel Ascii   9  18-300mm
>>> Exif.Photo.LensSerialNumber  Ascii  11  00
>>>
>>> exiftool version here is 10.45 I can try to update it but I became to
>>> ask myself if the wrong lens type is not write in the .CR2 by the camera.
>>>
>>> Marc
>>>
>>>
>>>
>>> Le 04/12/2017 à 16:36, Jean-Luc Coulon (f5ibh) a écrit :
>>>
>>> Can you try:
>>>
>>> exiv2 -pt IMG_.cr2 | grep Lens
>>>
>>> I got that on an other lens:
>>>
>>> Exif.CanonCs.LensTypeShort   1  Canon EF
>>> 24-70mm f/4L IS USM
>>> Exif.CanonCs.LensShort   3  24.0 - 70.0
>>> mm
>>> Exif.Canon.LensModel Ascii  70  EF24-70mm
>>> f/4L IS USM
>>>
>>> Maybe you can try also to update your exiftool-version (I've 10.67 here)
>>>
>>> Jean-Luc
>>>
>>> 2017-12-04 0:29 GMT+01:00 Marc Mascré <li...@mascre.fr>:
>>>
>>>> Hi
>>>>
>>>> It seem to be exactly this model for my lens. But when I use exiftool
>>>> on a .CR2 file from my camera, it detect my lens as a canon EF 75-300 too.
>>>> (see file attached)
>>>>
>>>> How can I find the right exit informations ?
>>>>
>>>> Marc
>>>>
>>>>
>>>>
>>>> Le 03/12/2017 à 18:24, Jean-Luc Coulon (f5ibh) a écrit :
>>>>
>>>> Hi,
>>>> What is the exact model of your lens (from the exif)?
>>>> Is it: "Sigma DT 18-300mm f/3.5-6.3 DC Macro" ?
>>>>
>>>> If yes, it is not in version_1 of lensfun database but it is in
>>>> version_2.
>>>>
>>>> If you upgrade you

Re: [darktable-dev] Wrong lens detected

[Jean-Luc Coulon (f5ibh)]

It seems that some informations are from the right lens and other for the
wrong one.
Probably these informations ARE in the file.
Maybe Sigma is trying to fool the Canon body to get some optical
corrections from it?

2017-12-04 22:43 GMT+01:00 Marc Mascré <li...@mascre.fr>:

> That is completely crazy
>
> # exiv2 -pt IMG_4575.CR2 | grep Lens
> Exif.CanonCs.LensTypeShort   1  Canon EF
> 75-300mm f/4-5.6 IS USM
> Exif.CanonCs.LensShort   3  18.0 - 300.0
> mm
> Exif.Canon.LensModel Ascii  74  18-300mm
> Exif.Photo.LensSpecification Rational4  18/1 300/1
> 0/1 0/1
> Exif.Photo.LensModel Ascii   9  18-300mm
> Exif.Photo.LensSerialNumber  Ascii  11  00
>
> exiftool version here is 10.45 I can try to update it but I became to ask
> myself if the wrong lens type is not write in the .CR2 by the camera.
>
> Marc
>
>
>
> Le 04/12/2017 à 16:36, Jean-Luc Coulon (f5ibh) a écrit :
>
> Can you try:
>
> exiv2 -pt IMG_.cr2 | grep Lens
>
> I got that on an other lens:
>
> Exif.CanonCs.LensTypeShort   1  Canon EF
> 24-70mm f/4L IS USM
> Exif.CanonCs.LensShort   3  24.0 - 70.0 mm
> Exif.Canon.LensModel Ascii  70  EF24-70mm
> f/4L IS USM
>
> Maybe you can try also to update your exiftool-version (I've 10.67 here)
>
> Jean-Luc
>
> 2017-12-04 0:29 GMT+01:00 Marc Mascré <li...@mascre.fr>:
>
>> Hi
>>
>> It seem to be exactly this model for my lens. But when I use exiftool on
>> a .CR2 file from my camera, it detect my lens as a canon EF 75-300 too.
>> (see file attached)
>>
>> How can I find the right exit informations ?
>>
>> Marc
>>
>>
>>
>> Le 03/12/2017 à 18:24, Jean-Luc Coulon (f5ibh) a écrit :
>>
>> Hi,
>> What is the exact model of your lens (from the exif)?
>> Is it: "Sigma DT 18-300mm f/3.5-6.3 DC Macro" ?
>>
>> If yes, it is not in version_1 of lensfun database but it is in version_2.
>>
>> If you upgrade your database with the command "lensfun-update", it will
>> create the following in your home directory: .local/share/lensfun/updates/v
>> ersion_1/
>> And then the lens will be in the file: slr-sigma.xml
>>
>> Jean-Luc
>>
>>
>> 2017-12-03 18:07 GMT+01:00 Marc Mascré <li...@mascre.fr>:
>>
>>> Hello
>>>
>>> I have a lens, the sigma 18-300 f3.5-6.3
>>>
>>> The problem is, it is detect by darktable as a canon EF 75-300
>>>
>>> I see the link for raw.pixls.us but it seem to be only for camera, not
>>> for lens.
>>>
>>>
>>> How I can tell to darktable that my lens is a sigma 18-300 and not a
>>> canon 75-300 ?
>>>
>>>
>>> Thanks
>>>
>>>
>>> Marc
>>>
>>> ___
>>> darktable developer mailing list to unsubscribe send a mail to
>>> darktable-dev+unsubscr...@lists.darktable.org
>>>
>>
>>
>> ___
>> darktable developer mailing list to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
>>
>>
>>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>
>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>

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

Re: [darktable-dev] Wrong lens detected

[Jean-Luc Coulon (f5ibh)]

Hi,
What is the exact model of your lens (from the exif)?
Is it: "Sigma DT 18-300mm f/3.5-6.3 DC Macro" ?

If yes, it is not in version_1 of lensfun database but it is in version_2.

If you upgrade your database with the command "lensfun-update", it will
create the following in your home directory:
.local/share/lensfun/updates/version_1/
And then the lens will be in the file: slr-sigma.xml

Jean-Luc


2017-12-03 18:07 GMT+01:00 Marc Mascré :

> Hello
>
> I have a lens, the sigma 18-300 f3.5-6.3
>
> The problem is, it is detect by darktable as a canon EF 75-300
>
> I see the link for raw.pixls.us but it seem to be only for camera, not
> for lens.
>
>
> How I can tell to darktable that my lens is a sigma 18-300 and not a canon
> 75-300 ?
>
>
> Thanks
>
>
> Marc
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>

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

Re: [darktable-dev] Manual lens corrections - feature request

[Jean-Luc Coulon (f5ibh)]

This is BTW explicitely explained in the manual p 446:
You can process RAW images with the camera and save them as JPEG
images. As the RAW image itself does not change, you can apply different
processing conditions to create any number of JPEG images from it.

And you can apply the following corrections in Lens aberration correction
- Peripheral illumination correction
- Distortion correction
- Digital Lens Optimizer
- Chromatic aberration correction
- Diffraction correction

So the whole "package" of lens aberration correction, IN the camera WITHOUT
affecting the RAW itself.


2017-11-15 13:51 GMT+01:00 Jean-Luc Coulon (f5ibh) <
jean.luc.cou...@gmail.com>:

> I'm getting some raw+jpeg from a Canon 5D MK IV. I will tell you when I
> will have looking in them.
>
> You *suppose* that "in-camera lens correction in Canon cameras doubles the
> RAW file size".
> In fact in the 5D Mk IV, the raw is the same size. It double when you use
> the "dual pixel raw" which contains informations that allow to do some kind
> of focus micro adjusments in post-production.
>
> If I take a shoot in RAW only, I get a RAW.
> Then I go to in-camera processing to get a JPEG.
> I click the lens icone to have the lens corrections applied.
> When done, I get A JPEG but the RAW has not been modified.
>
> Jena-Luc
>
> 2017-11-15 13:35 GMT+01:00 Heiko Bauke <heiko.ba...@mail.de>:
>
>> Hi,
>>
>> Am 15.11.2017 um 12:28 schrieb Roman Lebedev:
>>
>>> On Wed, Nov 15, 2017 at 2:14 PM, Heiko Bauke <heiko.ba...@mail.de>
>>> wrote:
>>>
>> [...]
>>
>>> Contrary to the common believe that in-camera
>>>> corrections are applied to JPEGs but not to the RAW file, in-camera lens
>>>> correction in the EOS-1D X Mark II is applied to RAWs only.  See
>>>> https://snapshot.canon-asia.com/article/en/eos-5d-mark-iv-le
>>>> ns-aberration-correctiona-close-up-look-part-1
>>>>
>>>
>>> Can you quote that part where it says what you think it says?
>>> I don't see anything there about modifying the raw files.
>>>
>>
>> the article is about in-camera lens correction.  Lens corrections are
>> stored in the image data, it's not about storing meta data for lens
>> correction in post processing.  Do not be confused by the fact that there
>> is also a software tool provided by Canon that implements the same kind of
>> lens correction algorithms for post processing.
>>
>> The term RAW file is not included explicitly in the article that I
>> mentioned.  It is, however, highlighted that »The Digital Lens Optimizer
>> [...]  made its debut as an in-camera feature on the EOS-1D X Mark II. At
>> that time, its effects could not be reflected in real time on JPEG
>> images.«  I understand this statement as that the RAW file image data is
>> affected.  The camera has a special hardware component to do the heavy
>> math.  This would not be needed if just some meta data for lens correction
>> in post would be included into the RAW file.
>>
>> Furthermore, another Canon article (see https://snapshot.canon-asia.co
>> m/article/en/eos-1d-x-mark-ii-in-camera-lens-optimization-fo
>> r-high-quality-images ) says
>>
>> »The processing ability of the Dual DIGIC 6 + image processing engines is
>> what makes in-camera image processing possible. They are capable of
>> processing the vast amount of data that is yielded from the 20-megapixel
>> sensor and the continuous shooting speed of 16 fps at a high speed, and
>> achieve in-camera RAW image development and real-time aberration
>> correction. A dedicated IC has been developed and employed to enable the
>> incorporation of different aberration correction features during in-camera
>> RAW image.«
>>
>> How would you understand »in-camera RAW image development«?  It does
>> definitely not refer to the lens correction to the JPEG, because this
>> camera does not have such a feature.
>>
>> According to https://photo.stackexchange.com/questions/35324/why-does-usi
>> ng-canons-digital-lens-optimizer-double-the-size-of-a-raw-file
>> in-camera lens correction in Canon cameras doubles the RAW file size,
>> because the processed image data is stored in addition to the unprocessed
>> RAW data.
>>
>>
>> Heiko
>>
>>
>> --
>> -- Number Crunch Blog @ https://www.numbercrunch.de
>> --  Cluster Computing @ http://www.clustercomputing.de
>> --   Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke
>> --  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
>>
>
>

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

Re: [darktable-dev] Manual lens corrections - feature request

[Jean-Luc Coulon (f5ibh)]

I'm getting some raw+jpeg from a Canon 5D MK IV. I will tell you when I
will have looking in them.

You *suppose* that "in-camera lens correction in Canon cameras doubles the
RAW file size".
In fact in the 5D Mk IV, the raw is the same size. It double when you use
the "dual pixel raw" which contains informations that allow to do some kind
of focus micro adjusments in post-production.

If I take a shoot in RAW only, I get a RAW.
Then I go to in-camera processing to get a JPEG.
I click the lens icone to have the lens corrections applied.
When done, I get A JPEG but the RAW has not been modified.

Jena-Luc

2017-11-15 13:35 GMT+01:00 Heiko Bauke :

> Hi,
>
> Am 15.11.2017 um 12:28 schrieb Roman Lebedev:
>
>> On Wed, Nov 15, 2017 at 2:14 PM, Heiko Bauke  wrote:
>>
> [...]
>
>> Contrary to the common believe that in-camera
>>> corrections are applied to JPEGs but not to the RAW file, in-camera lens
>>> correction in the EOS-1D X Mark II is applied to RAWs only.  See
>>> https://snapshot.canon-asia.com/article/en/eos-5d-mark-iv-le
>>> ns-aberration-correctiona-close-up-look-part-1
>>>
>>
>> Can you quote that part where it says what you think it says?
>> I don't see anything there about modifying the raw files.
>>
>
> the article is about in-camera lens correction.  Lens corrections are
> stored in the image data, it's not about storing meta data for lens
> correction in post processing.  Do not be confused by the fact that there
> is also a software tool provided by Canon that implements the same kind of
> lens correction algorithms for post processing.
>
> The term RAW file is not included explicitly in the article that I
> mentioned.  It is, however, highlighted that »The Digital Lens Optimizer
> [...]  made its debut as an in-camera feature on the EOS-1D X Mark II. At
> that time, its effects could not be reflected in real time on JPEG
> images.«  I understand this statement as that the RAW file image data is
> affected.  The camera has a special hardware component to do the heavy
> math.  This would not be needed if just some meta data for lens correction
> in post would be included into the RAW file.
>
> Furthermore, another Canon article (see https://snapshot.canon-asia.co
> m/article/en/eos-1d-x-mark-ii-in-camera-lens-optimization-
> for-high-quality-images ) says
>
> »The processing ability of the Dual DIGIC 6 + image processing engines is
> what makes in-camera image processing possible. They are capable of
> processing the vast amount of data that is yielded from the 20-megapixel
> sensor and the continuous shooting speed of 16 fps at a high speed, and
> achieve in-camera RAW image development and real-time aberration
> correction. A dedicated IC has been developed and employed to enable the
> incorporation of different aberration correction features during in-camera
> RAW image.«
>
> How would you understand »in-camera RAW image development«?  It does
> definitely not refer to the lens correction to the JPEG, because this
> camera does not have such a feature.
>
> According to https://photo.stackexchange.com/questions/35324/why-does-usi
> ng-canons-digital-lens-optimizer-double-the-size-of-a-raw-file
> in-camera lens correction in Canon cameras doubles the RAW file size,
> because the processed image data is stored in addition to the unprocessed
> RAW data.
>
>
> Heiko
>
>
> --
> -- Number Crunch Blog @ https://www.numbercrunch.de
> --  Cluster Computing @ http://www.clustercomputing.de
> --   Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke
> --  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
>

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

Re: [darktable-dev] Manual lens corrections - feature request

[Jean-Luc Coulon (f5ibh)]

.> correction in the EOS-1D X Mark II is applied to RAWs only.  See
> https://snapshot.canon-asia.com/article/en/eos-5d-mark-iv-le
ns-aberration-correctiona-close-up-look-part-1




I cannot read on this link  that the correction in done on the RAW.
In the past, the lens identification was in the EXIF and DPP has a database
of these lenses. It was then applying the corrections. In camera the only
correction applied to the JPEG was the vignetting (this is the case on EOS
7D and EOS 5D Mk II at least).

If I follow the link to the 1D Mk II, I can read:
"The EOS-1D X Mark II is equipped with an IC that was specially developed
to enable correction by the Digital Lens Optimizer (DLO) during in-camera
RAW image post-processing."

But "in-camera processing of the RAW" doesnt mean the RAW is affected. This
is done in the RAW -> JPEG in-camera conversion.

My son is a photographer. For the newspapers, they use only the in-camera
JPEG. This is because in the past there was too many "fake" photographies.
And they have tools to say if the picture has been retouched in
Photoshp/what_you_want. All is allowed is crop / Brightness / Saturation /
Contrast.

I can be wrong about these camera but I will get some raw from a 5D MK IV
and see if the raw is affected

Jean-Luc

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

Re: [darktable-dev] Manual lens corrections - feature request

[Jean-Luc Coulon (f5ibh)]

Hi,
Personnaly, I think it is a bad idea [tm] to include anything in the raw
file.
If you change your mind, you cannot get back...

This kind of feature is very handy for jpeg shoot but even then it depends
of what you do with the jpeg: direct sharing/printing/hosting or if you
want to process it a bit later.

Jean-Luc

2017-11-15 10:44 GMT+01:00 Heiko Bauke :

> Hi,
>
> Am 14.11.2017 um 20:39 schrieb bigmack...@mail.com:
>
>> New user here, so apologies if I'm posting to the wrong list!
>> I've just switched fully from Lightroom 6 to Darktable 2.2.5 under Linux.
>> Kudos to the developers - it's superb.
>> The one and only feature I'm missing in Darktable is the ability to
>> adjust for barrel or pincushion distortion manually. I realise lenses can
>> be profiled for the "Lens Correction" module, but this is time consuming
>> and doesn't allow for fine tuning of distortion to my own tastes (sometimes
>> I don't want to fully correct, or I may perhaps add in a little
>> distortion). At present, I have to export my files to TIFF, open them in
>> GIMP and carry out adjustments in GIMP's "Lens Distortion" feature. This
>> makes no sense when other correction features are provided within Darktable
>> itself.
>> darktable-dev+unsubscr...@lists.darktable.org
>>
>
> yes this might be a useful feature, especially for those who shoot with
> exotic lenses.
>
> In case that you take pictures with Sony cameras: There is a camera app
> that does manual lens correction (peripheral shading, chromatic aberration
> and distortion) in camera.  All corrections are included in the RAW file.
> https://www.youtube.com/watch?v=CWe_ePAHSfk
>
>
> Heiko
>
> --
> -- Number Crunch Blog @ https://www.numbercrunch.de
> --  Cluster Computing @ http://www.clustercomputing.de
> --   Professional @ https://www.mpi-hd.mpg.de/personalhomes/bauke
> --  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
>
> 
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@list
> s.darktable.org
>
>

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

Re: [darktable-dev] Deconvolution and Python framework

[Jean-Luc Coulon (f5ibh)]

> but those "challenges" would only affect a small sub-set of dt users
*every* "challenge affect only a small subset of dt users…
Only base curve, demosaicing, light-contrast-saturation affect everybody ;)

2017-10-11 17:34 GMT+02:00 Patrick Shanahan :

> * Jørn Villesen Christensen  [10-11-17 11:25]:
> > On 2017-10-11 15:35, Pete Hall wrote:
> > >Just an opinion from a devoted user... It might be a very useful tool
> for
> > >me. I shoot a lot of sporting events. It's common for me to find a great
> > >shot ruined because at the critical moment, the camera focused on the
> > >wrong player, or on the goal keeper's net. Even if it can't be made
> > >efficient for the normal workflow, it could still be a very useful tool,
> > >at least for me.
> >
> > Same for me - I think that would be an awesome feature, although I am
> kind
> > of sceptical that it will be the magical bullet for you, Pete ;-)
> >
> > But nonetheless, I hope that it will be possible to fit this
> functionality
> > into the workflow of Darktable - although I do see the challenges with
> the
> > time requirements.
>
> but those "challenges" would only affect a small sub-set of dt users, the
> same as those working low-light and/or high-noise images.  and you can
> prioritize usage, work those modules last to minimize delays.
>
> --
> (paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
> http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
> Registered Linux User #207535@ http://linuxcounter.net
> Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode
> 
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@
> lists.darktable.org
>
>

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

Re: [darktable-dev] Multiple module history entries

[Jean-Luc Coulon (f5ibh)]

It would be intersting to know WHEN this happpens.
If I use "crop and rotate" (for example) many times, I get several entries
in the history.
But this is normal and when I clic on one entry in the history, I get how
was the image at this point of the history.
So, in this case, it is normal and desirable. This way, there is a mean to
undo the actions or to revert to a specific point.

Jean-Luc

2017-02-11 9:54 GMT+01:00 Pascal Obry :

>
> I have seen this from time to time. I thought it was because of some
> module version diff when editing an old picture... Not sure.
>
> Anyway for me I have always been able to "fix" that by compressing the
> history stack.
>
> Regards,
>
> --
>   Pascal Obry /  Magny Les Hameaux (78)
>
>   The best way to travel is by means of imagination
>
>   http://www.obry.net
>
>   gpg --keyserver keys.gnupg.net --recv-key F949BD3B
> 
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@
> lists.darktable.org
>
>

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

Re: [darktable-dev] Multiple white balances?

[Jean-Luc Coulon (f5ibh)]

I also asked in the past for a local white balance.
There is a good example with capture one here:
http://blog.phaseone.com/white-balance-compromises/

It is, of course, possible to get an appropriate result with some smart ans
strick use of the existing tools.
I've been at a workshop where capture one was available. I asked to see how
it really works.
The local white balance is really a nice tool.

Regards

Jean-Luc

2017-02-07 20:49 GMT+01:00 J. Liles :

>
> On Tue, Feb 7, 2017 at 10:20 AM, Thomas Werzmirzowsky 
> wrote:
>
>> Hello everybody,
>>
>> I was just wondering if there are any plans to add the feature of
>> multiple white balances to darktable.
>>
>> Usually I'm watching lightroom tutorials online as there are not many
>> for darktable and it seems to be a common thing
>> to have multiple white balances. This seems to be used especially often
>> for sunset/sunrise to have warmer tones around
>> the sun/in the sky.
>>
>> I tried to reproduce that in darktable using "color correction" and
>> "split toning" modules but didn't really succeed. Also having
>> just another white balance module with a mask seems to be much easier.
>>
>> Thanks a lot for your feedback.
>>
>> Best regards
>> Thomas
>>
>>
> Just butting in here... The color correction filter with mask can do this
> and, as already mentioned, the graduated density filter has color tint for
> a similar purpose (although you can also use a graduated mask in the color
> correction filter.)
>
> This isn't the only situation where Darktable's model of masking (each
> module may have a mask) being different from Lightroom's (one mask aka
> brush can control many parameters simultaenously) creates confusion.
>
> Lightroom's method is probably more efficient too, since a pipeline is
> being run on the image and then masked/blended in all at once, rather than
> separately applying and masking/blending in each module/operator.
>
> I'm used to the way Darktable does it, but from a usability standpoint I
> think the 'brushes' model makes more sense. When you want to color correct
> a face *and* adjust the exposure of a face *and* do something else to
> everything that's *not* a face (such as stronger NR.) it gets pretty clunky
> and slow. Especially if you want to refine that mask (later.)
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>

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

Re: [darktable-dev] lensfun git + darktable git

[Jean-Luc Coulon (f5ibh)]

This is a bit different but some time ago, I failed to build darktable with
git version of lensfun.

I've opened a bug on lensfun (#72).

I received the following reply:

As a quick workaround, you may use the environment variable

CFLAGS=-Wno-error=deprecated-declarations


Regards

Jean-Luc

2017-01-29 12:53 GMT+01:00 Marc Cousin :

> Hi,
>
>
> I'm having this error when using latest darktable from git and latest
> lensfun from git:
>
>
> [iop_lens]: could not load lensfun database in
> `/usr/share/lensfun/version_2'!
> [iop_lens]: could not load lensfun database in `/usr/share/lensfun'!
>
> I have no lens correction when I get this error, of course.
>
>
> Reverting to either latest stable lensfun or latest darktable solves the
> problem.
>
>
> I thought it was worth mentioning right now. I hope it is not an already
> known problem.
>
>
> Regards
>
> Marc
>
> 
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@
> lists.darktable.org
>
>

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

Re: [darktable-dev] strange ld crash building darktable

[Jean-Luc Coulon (f5ibh)]

Hi,

Unfortunately there was a new upgrade of binutils today on debian sid.

It is from 2.51.20161105-2 -> 2.51.20161108-1

And... the bug is here again.

It seems that upsteam developpers are not aware of it. The changelog shows
that there was a revert to fixe a problem then (today) upgrading to a new
upsteam trunk snapshot... Dangerous way to manage a so important package.
But it is sid ;)

Jean-Luc

2016-11-07 17:03 GMT+01:00 Pascal Obry :

>
> Jean-Luc,
>
> > There is a new version of binutils this morning (morning for me) on
> > debian sid :  2.27.51.20161105-2 .
> > This version fixes the ld problem for me.
>
> Confirmed. Just an ld bug after all. Thanks.
>
> --
>   Pascal Obry /  Magny Les Hameaux (78)
>
>   The best way to travel is by means of imagination
>
>   http://www.obry.net
>
>   gpg --keyserver keys.gnupg.net --recv-key F949BD3B
>

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

Re: [darktable-dev] strange ld crash building darktable

[Jean-Luc Coulon (f5ibh)]

Bonjour Pascal, hi everybody,

There is a new version of binutils this morning (morning for me) on debian
sid :  2.27.51.20161105-2 .
This version fixes the ld problem for me.

Regards

Jean-Luc

2016-11-05 22:21 GMT+01:00 Pascal Obry :

>
> Thanks Tobias and Jean-Luc, I'm not alone :)
>
> Good to see a bug report opened.
>
> Cheers,
>
> --
>   Pascal Obry /  Magny Les Hameaux (78)
>
>   The best way to travel is by means of imagination
>
>   http://www.obry.net
>
>   gpg --keyserver keys.gnupg.net --recv-key F949BD3B
> 
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@
> lists.darktable.org
>
>

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

Re: [darktable-dev] strange ld crash building darktable

[Jean-Luc Coulon (f5ibh)]

Hi,

I got the same on debian/sid with the update of binutils package from
2.27-9+b1 to 2.27.51.20161102-1.

I've opened a bug (#843164) for that.

Reverting to 2.27-9 probably needs also to revert gcc/cpp/g++ and Co as
well.

Regards

Jean-Luc
​

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

[darktable-dev] Re: Another real-life example

[Jean-Luc Coulon (f5ibh)]

I've downloaded your picture.
I've used the colour picker on the black car at the upper left.
I used the "zone" picker and drawn a square on the black car.

Without pushing the exposure but with the base curve applied, I get:
80, 80, 78
With +1EV, I get:
118, 118, 115

Is there something wrong as I don't SEE anything wrong (my monitor is
calibrated).

Regards

Jean-Luc

2016-10-23 20:45 GMT+02:00 Zbigniew :

> https://www.sendspace.com/file/dskpng
>
> Pay attention to NE corner again; the black car, of course. Zoom to 100%,
> and try pushing - you'll notice magenta-brownish "sand" even by adding just
> 1 EV - no need to push it whole 4 EV.
> --
> regards,
> Zbigniew
>

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

Re: [darktable-dev] Does darktable properly handle shadows in Canon RAW files?

[Jean-Luc Coulon (f5ibh)]

No, technicaly, I've not the answer.

But on the links you sent, there are various answers: for some it is a
noise problem, others said it is a bayer matrix problem, others said it is
the way the data are encoded (positive integer vs signed integers).

I've a Canon (EOS 7D), I've never "seen" (this means it can exists) this
magenta cast on shadows (I've more the problem when trying to recover
hightlights), noise is... noise and pretty random.

And about pushing a RAW +5EV, I've never done that, I try to have a better
exposure...

Jean-Luc

2016-10-23 19:59 GMT+02:00 Zbigniew <zbigniew2...@gmail.com>:

> On Sun, Oct 23, 2016 at 07:47:58PM +0200, Jean-Luc Coulon (f5ibh) wrote:
>
> > Do you mean that you HAVE HAD the problem you report or is it simply "to
> > know if" ?
>
> I'd like to learn it, since I'm considering a switch from LR. But I don't
> know Darktable yet, therefore got no idea whether does it suffer the same
> problem. The simplest way is to ask them who know this program much better,
> isn't it?
>
> So you don't know the answer, it seems. Anyone else?
> --
> regards,
> Zbigniew
>

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

Re: [darktable-dev] Does darktable properly handle shadows in Canon RAW files?

[Jean-Luc Coulon (f5ibh)]

Do you mean that you HAVE HAD the problem you report or is it simply "to
know if" ?

Jean-Luc

2016-10-23 4:05 GMT+02:00 Zbigniew :

> Sorry, if it's silly question - but I noticed the problem only recently,
> and
> after digging around found these threads explaining roots of the problem:
>
>  https://www.reddit.com/r/photography/comments/3q8q7o/
> purple_noise_in_shadows/
>  https://www.reddit.com/r/photography/comments/3q4tnz/
> how_to_correctly_push_5_stops_with_canon/
>
> Not sure: have suggested there software tweaks been implemented into
> Darktable already? Anyway if not - it could be worthy... it seems most of
> the software - including Adobe's LR - handle Canon's RAW files not quite
> correctly - that's why there are problem with unusual shadows' colours
> while
> pushing.
> --
> regards,
> Zbigniew
> 
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscribe@
> lists.darktable.org
>
>

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

Re: [darktable-dev] saving translated po file gives an error

[Jean-Luc Coulon (f5ibh)]

I've already reported that problem some time ago. Maybe it was related to
the manual translation.

When there is a %, it MUST be doubled.

But it must be doubled both in msgid and msgstr.

This way, the checks (msgfmt -c --statistics) are happy.
But anyway, I think we can survive with this error and the translation is
accepted.

J-L

2016-03-20 22:18 GMT+01:00 Ger Siemerink :

> if I double it in poedit it says that translated and origin do not have
> same amount of %
>
> and output
>
> ~/darktable# cd po && intltool-update nl && cd ..
> ..
> voltooid.
> 2156 vertaalde berichten.
>
> so no new strings
>
> regards Ger
>
>
> 2016-03-20 22:06 GMT+01:00 Ulrich Pegelow :
>
>> Just tried it but it doesn't seem to work in terms of the output as a
>> tooltip. Could you please check if the double %% would solve the
>> translation issue? Maybe there is something different.
>>
>> In case of doubt I will remove the whole stuff related to that unused
>> parameter.
>>
>> Ulrich
>>
>> Am 20.03.2016 um 22:02 schrieb Ger Siemerink:
>>
>>> Thanks
>>>
>>> regards Ger
>>>
>>> 2016-03-20 22:01 GMT+01:00 Ulrich Pegelow >> >:
>>>
>>> Think I already got it. I need to replace "%" with "%%". Will do so
>>> asap.
>>>
>>> Ulrich
>>>
>>> Am 20.03.2016 um 21:26 schrieb Ger Siemerink:
>>>
>>> Hello,
>>>
>>> Saving my translated nl.po file gives me an error.
>>> ​
>>> String​ 831:the level of lens dependent correction, 100% for full
>>> dependency, 0% for the generic case
>>>
>>> poedit reports:
>>> msgstr isn't lequal for C, different than msgid.
>>> in directive number 1 character "b" not a valid conversion
>>> specification
>>>
>>> Any idea what is wrong???
>>> ​ Thanks for helping!
>>>
>>
>> ___
>> darktable developer mailing list
>> to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
>>
>>
>
>
> --
> met vriendelijke groet / kind regards Ger
> mailto:g.siemer...@gmail.com website: www.gersiemerink.net
>
> ___
> darktable developer mailing list to unsubscribe send a mail to
> darktable-dev+unsubscr...@lists.darktable.org
>

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

Re: [darktable-dev] hover and other visual aspects of the gui

[Jean-Luc Coulon (f5ibh)]

Hi,

As everything is based on grey scales, the way the monitor is
calibrated has a big impact on the various shades used in dt.

But anyway, there is a nice .css file (darktable.css), probably, in
/usr/share/darktable, it is possible to copy it into the personnal
configuration directory (maybe .config/darktable I suppose) and then
play with it.

It is harmless as it is possible to delete the file are find again the
default if something went wrong ;=)


2015-12-31 12:11 GMT+01:00 Tobias Ellinghaus :
> Am Dienstag, 29. Dezember 2015, 17:48:54 schrieb simon:
>> Hi All,
>>
>> Thanks for the 2.0.0. it is a marvel of coding!
>>
>> A few visual things I noticed in this version:
>>
>> -If you can tag a option with a checkmark, there is no visual
>> information where to do that. i.e. the tag has no square box behind it.
>
> Not sure what you mean there, please file a bug report [0] and attach a
> screenshot.
>
>> -highlighting things when hovering is confusing. if i change a reating
>> from lets say 2 to 3 and click the 3, it remains the same until i move
>> the mouse.
>
> That is a bug but has nothing to do with highlighting.
>
>> other example is clicking a image in the lighttable or
>> hovering over it. it is not clear if the image under the mouse is
>> selected or not.
>
> We should probably change the hover lightness.
>
>> is the hover strictly necessary?
>
> Yes.
>
>> that can be solved by giving the hover a distinct different color shade
>> than grey
>
> Just a different lightness would be enough. Adding color is a bad idea, it
> distracts from the images.
>
> Tobias
>
> [0] http://redmine.darktable.org/projects/darktable/issues/new
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Trouble with drawn masking...

[Jean-Luc Coulon (f5ibh)]

Hi,

There are other problems related to the masks.

I remark that if I'm editig a mask quite a lot with zoom & pan to see
exactly what I'm doing, then with "zoom to fit", the mask layout
borders are corretly displayed but the underlaying picture is not: it
is correctly displayed for a very short time and then appears zoomed
in. The preview in the upper left corner doesnt display the zoom
outlines. I can zoom 100%, 200% but "to fit" is not working.

If I go to the lighttable and bck to the darkroom, it is fine.

All that is done in the monochrome module.

I think this can be related.

Jean-Luc

2015-12-23 19:45 GMT+01:00 Ulrich Pegelow :
> One of the sample images in redmine ticket #10805 has a similar issue. I'm
> currently trying to find out what's happening.
>
> Ulrich
>
> Am 23.12.2015 um 19:36 schrieb Samuel Simmons:
>>
>> I think I may have found a bug here.  After I draw a mask with add path
>> on a file, the outer ring of the selection sometimes disappears, and
>> when it does, I can't move the selection.
>> Can anyone else reproduce this? I'm using version 2.0.0.
>>
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
>
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org