Re: Presets setting too many parameters, sometimes (was: [darktable-user] Activating the pipeline)

2021-05-05 Thread Patrick Shanahan
* Michael Staats  [05-05-21 01:33]:
> Hi Patrick
> 
> On 04/05/2021 17:01, Patrick Shanahan wrote:
> > * Michael Staats  [05-04-21 08:51]:
> >> Hi
> >> FYI: Just opened feature request #8861
> >>
> >> "Smart Presets": More flexible presets: only set some parameters of a
> >> module
> >
> > can you not do that already by setting the scope or just "%" which matches
> > everything?
> 
> I'm not sure what you mean by "setting the scope". If you are talking
> about the matching criteria, where you can set "%" to match everything:
> Well, this can be used to decide if a preset will be applied, or not.
> But not which parameter of the module is affected, it's always all
> parameters, with values that were active when the preset was created.
> Which is fine for many cases, but not for all.
> 
> Ok, coming back to my use-case: For my Sigma 17-70, I could of course
> create, say, 10 presets in lens correction, each for a different focal
> length, and match this in the matching criteria. But I'm afraid, this is
> a bit too tedious.

so what you desire is possible but not "easy" ...

you desire an iso, exposure or aperture range that employs AI?

please explain in more detail what you would have different.

then, perhaps a "feature" request would be appropriate.

-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org



Re: Presets setting too many parameters, sometimes (was: [darktable-user] Activating the pipeline)

2021-05-05 Thread Michael Staats
On 05/05/2021 13:31, Patrick Shanahan wrote:
>
> so what you desire is possible but not "easy" ...
>
> you desire an iso, exposure or aperture range that employs AI?
>
> please explain in more detail what you would have different.
>
> then, perhaps a "feature" request would be appropriate.
>

Hi Patrick
I think I did that.

a) Allow preset customizations that let you select which parameter of a
module is set by a preset, and which not, or; alternatively, and easier
to implement,
b) hardcode that some parameters of some modules are never set by a
preset, those which just don't make sense, like focal length in lens
correction.

Option b is less flexible, and maybe someone actually _wants_ focal
length to be set by a preset, and not from the picture, who knows...
They would not like this change.

Best regards,
Michael

--
Michael Staats
michael.sta...@gmx.de

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org



Re: Presets setting too many parameters, sometimes (was: [darktable-user] Activating the pipeline)

2021-05-05 Thread KOVÁCS István
On Wed, 5 May 2021 at 13:33, Patrick Shanahan  wrote:
>
> > > * Michael Staats  [05-04-21 08:51]:
> > >> Hi
> > >> FYI: Just opened feature request #8861
> > >>
> > >> "Smart Presets": More flexible presets: only set some parameters of a
> > >> module
> > >
> > > can you not do that already by setting the scope or just "%" which matches
> > > everything?

I think these are two different aspects of applying presets.
The '%' marker influences >>>which images<<< a preset is applied to.
E.g. if I set focal length to '%', it means it'll match all focal
lengths. Whereas, if I understand correctly, Michael wants to achieve
that >>>only certain settings<<< of a preset would be applied (e.g. in
lens correction, set the module parameter 'corrections' to 'only
distortion', but leave all other parameters as they are read from the
camera or at default values; for filmic, set 'preserve chrominance' to
'no' (or whatever someone may wish to use), but still let filmic
auto-apply all the other settings, some of which are calculated from
exposure settings -- but not if a preset is used).

Kofa

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org



Re: Presets setting too many parameters, sometimes (was: [darktable-user] Activating the pipeline)

2021-05-05 Thread Michael Staats
On 05/05/2021 14:46, KOVÁCS István wrote:
>
> I think these are two different aspects of applying presets.
> The '%' marker influences >>>which images<<< a preset is applied to.
> E.g. if I set focal length to '%', it means it'll match all focal
> lengths. Whereas, if I understand correctly, Michael wants to achieve
> that >>>only certain settings<<< of a preset would be applied (e.g. in
> lens correction, set the module parameter 'corrections' to 'only
> distortion', but leave all other parameters as they are read from the
> camera or at default values; for filmic, set 'preserve chrominance' to
> 'no' (or whatever someone may wish to use), but still let filmic
> auto-apply all the other settings, some of which are calculated from
> exposure settings -- but not if a preset is used).
>

Exactly! Thanks.
Best regards,
Michael


--
Michael Staats
michael.sta...@gmx.de

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org



Re: Presets setting too many parameters, sometimes (was: [darktable-user] Activating the pipeline)

2021-05-05 Thread David Vincent-Jones
I would have thought that presets would be automatically run as a part 
of the import process .. to me that would make sense. Having to manually 
operate a style after the import in order to activate what one already 
determined was wanted, does not appear reasonable.


David

On 2021-05-05 5:59 a.m., Michael Staats wrote:

On 05/05/2021 14:46, KOVÁCS István wrote:

I think these are two different aspects of applying presets.
The '%' marker influences >>>which images<<< a preset is applied to.
E.g. if I set focal length to '%', it means it'll match all focal
lengths. Whereas, if I understand correctly, Michael wants to achieve
that >>>only certain settings<<< of a preset would be applied (e.g. in
lens correction, set the module parameter 'corrections' to 'only
distortion', but leave all other parameters as they are read from the
camera or at default values; for filmic, set 'preserve chrominance' to
'no' (or whatever someone may wish to use), but still let filmic
auto-apply all the other settings, some of which are calculated from
exposure settings -- but not if a preset is used).


Exactly! Thanks.
Best regards,
Michael


--
Michael Staats
michael.sta...@gmx.de

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org




darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: Presets setting too many parameters, sometimes (was: [darktable-user] Activating the pipeline)

2021-05-05 Thread Jean-Luc CECCOLI
> Message du 05/05/21 13:31
> De : "Patrick Shanahan" 

> A : darktable-user@lists.darktable.org
> Copie à : 
> Objet : Re: Presets setting too many parameters, sometimes (was: 
> [darktable-user] Activating the pipeline)
> 
> * Michael Staats  [05-05-21 01:33]:
> > Hi Patrick
> > 
> > On 04/05/2021 17:01, Patrick Shanahan wrote:
> > > * Michael Staats  [05-04-21 08:51]:
> > >> Hi
> > >> FYI: Just opened feature request #8861
> > >>
> > >> "Smart Presets": More flexible presets: only set some parameters of a
> > >> module
> > >
> > > can you not do that already by setting the scope or just "%" which matches
> > > everything?
> > 
> > I'm not sure what you mean by "setting the scope". If you are talking
> > about the matching criteria, where you can set "%" to match everything:
> > Well, this can be used to decide if a preset will be applied, or not.
> > But not which parameter of the module is affected, it's always all
> > parameters, with values that were active when the preset was created.
> > Which is fine for many cases, but not for all.
> > 
> > Ok, coming back to my use-case: For my Sigma 17-70, I could of course
> > create, say, 10 presets in lens correction, each for a different focal
> > length, and match this in the matching criteria. But I'm afraid, this is
> > a bit too tedious.
> 
> so what you desire is possible but not "easy" ...
> 
I think that is not possible at all, unless one creates a preset for each focal 
length - e.g., for a 17-70, it would need 54 presets at least. And 131 for a 
70-200 ! ouch !
I think certain values ought to be flexible, depending on, for instance, the 
focal length.
I do not mean I want this, though. I know it may be very difficult to 
implement, if not impossible, as I read such requessts in threads for other 
photo software.

Rgrds,

J.-Luc

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org



Re: Presets setting too many parameters, sometimes (was: [darktable-user] Activating the pipeline)

2021-05-05 Thread David Vincent-Jones
There is another problem  If apply a style that calls all of my 
presets this works but it duplicates everything in the history and then 
I need to compress the history stack. OK   it's not a big deal but 
it simply is creating a nuisance.


Auto-apply presets should simply 'auto-apply' without requiring the user 
to mess around in this manner.


David

On 2021-05-05 5:59 a.m., Michael Staats wrote:

On 05/05/2021 14:46, KOVÁCS István wrote:

I think these are two different aspects of applying presets.
The '%' marker influences >>>which images<<< a preset is applied to.
E.g. if I set focal length to '%', it means it'll match all focal
lengths. Whereas, if I understand correctly, Michael wants to achieve
that >>>only certain settings<<< of a preset would be applied (e.g. in
lens correction, set the module parameter 'corrections' to 'only
distortion', but leave all other parameters as they are read from the
camera or at default values; for filmic, set 'preserve chrominance' to
'no' (or whatever someone may wish to use), but still let filmic
auto-apply all the other settings, some of which are calculated from
exposure settings -- but not if a preset is used).


Exactly! Thanks.
Best regards,
Michael


--
Michael Staats
michael.sta...@gmx.de

darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org




darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Re: Presets setting too many parameters, sometimes (was: [darktable-user] Activating the pipeline)

2021-05-05 Thread Remco Viëtor
On mercredi 5 mai 2021 19:06:33 CEST Jean-Luc CECCOLI wrote:
> > Message du 05/05/21 13:31
> > De : "Patrick Shanahan"
> > 
> > A : darktable-user@lists.darktable.org
> > Copie à :
> > Objet : Re: Presets setting too many parameters, sometimes (was:
> > [darktable-user] Activating the pipeline)> 
> > * Michael Staats  [05-05-21 01:33]:
> > > Hi Patrick
> > > 
> > > On 04/05/2021 17:01, Patrick Shanahan wrote:
> > > > * Michael Staats  [05-04-21 08:51]:
> > > >> Hi
> > > >> FYI: Just opened feature request #8861
> > > >> 
> > > >> "Smart Presets": More flexible presets: only set some parameters of a
> > > >> module
> > > > 
> > > > can you not do that already by setting the scope or just "%" which
> > > > matches
> > > > everything?
> > > 
> > > I'm not sure what you mean by "setting the scope". If you are talking
> > > about the matching criteria, where you can set "%" to match everything:
> > > Well, this can be used to decide if a preset will be applied, or not.
> > > But not which parameter of the module is affected, it's always all
> > > parameters, with values that were active when the preset was created.
> > > Which is fine for many cases, but not for all.
> > > 
> > > Ok, coming back to my use-case: For my Sigma 17-70, I could of course
> > > create, say, 10 presets in lens correction, each for a different focal
> > > length, and match this in the matching criteria. But I'm afraid, this is
> > > a bit too tedious.
> > 
> > so what you desire is possible but not "easy" ...
> 
> I think that is not possible at all, unless one creates a preset for each
> focal length - e.g., for a 17-70, it would need 54 presets at least. And
> 131 for a 70-200 ! ouch ! I think certain values ought to be flexible,
> depending on, for instance, the focal length. I do not mean I want this,
> though. I know it may be very difficult to implement, if not impossible, as
> I read such requessts in threads for other photo software.
If the problem is lens recognition, perhaps using the ".exiv2" configuration 
file might help to link ambiguous lens IDs to the lens you actually own.
(the ".exiv2" file in your home directory is for Linux, no idea if there's a 
windows equivalent, nor how to use it)

Remco





darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org