Re: [darktable-dev] DT bad on skin tones?

[dt-list]

dt-l...@stefan-klinger.de (2019-Jun-04, excerpt):
> and not enough good searchable concise test.

"text", not "test".

Case in point: Text is easier to edit/bugfix/adapt later on.


-- 
http://stefan-klinger.deo/X
I prefer receiving plain text messages, not exceeding 32kB. /\/
  \
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] DT bad on skin tones?

[dt-list]

Aurélien Pierre (2019-May-29, excerpt):
> I guess I will have to record video tutorials in English then…

No, please, just write it down.  I hate watching videos until the
presenter finally gets to the point.  There's already too many videos
and not enough good searchable concise test.


-- 
http://stefan-klinger.deo/X
I prefer receiving plain text messages, not exceeding 32kB. /\/
  \
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Camera-specific curves generation process

[Andreas Schneider]

On Monday, 3 June 2019 13:57:18 CEST Florian W wrote:
> Hi there,
> 
> Does anyone know if the procedure to generate the curves for a specific
> camera model is still up to date ?
> 
> I took the instructions from here (5 years old though) :
> https://www.darktable.org/2013/10/about-basecurves/#comment-30544 and in
> the README of $darktable_src/tools/basecurve.
> 
> I tried to generate curves for my Canon 750d with shots unfocused, both
> over and under exposed at the same time as instructed (see the jpg at
> https://ibb.co/C29R6Q9).
> And well... the generated curve is not very useful... see
> https://ibb.co/rG5yvnm
> 
> Does one has to do a lot a sample shots (and maybe more diverse kind of
> shots) to get a correct result ?
> Or maybe someone has successfuly generated its camera's basecurve and can
> provide some guidance with this problem ?


The correct way would be to follow:

https://pixls.us/articles/profiling-a-camera-with-darktable-chart/



Andreas 


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

Re: [darktable-dev] Magnification of modules in Darkroom

[Aurélien Pierre]

The point of collapsing the histogram is to spare some room. Adding a
GUI control to do it is equivalent to using more space to save some
space. How does that solve anything ?

Remember keyboard shortcuts are user-configurable.

Le 31/05/2019 à 04:26, Patrick Shanahan a écrit :
> * David Vincent-Jones  [05-30-19 19:50]:
>> Remembering all of these multi-key shortcuts is a bit of a pain
>> (particularly for us old-timers) would it be practical to incorporate a
>> further option in the current set or provide an on/off icon on a 'histogram'
>> header line.
>>
>> David
>>
>> On 2019-05-30 10:14 a.m., William Ferguson wrote:
>>> 2.7 already has histogram collapsing, CTRL+SHIFT+H
>>>
>>>
>>> On Thu, May 30, 2019 at 12:54 PM Florian W >> > wrote:
>>>
>>> @julian
>>>
>>> Collapsing the histogram is also part of my bucket of features I
>>> would like to implement soon enough.
>>> I see that I'm not the only one often bored by the space it takes,
>>> even on a 24 inches display.
>>>
>>> I think it could be associated with a key shortcut as one still
>>> often have to look at it to control what he's doing.
>>>
>>> And at some other times I would like to be able to enlarge it as
>>> Giuseppe suggests for any module.
>>>
>>> I keep in mind your inputs regarding this when I'll be able to
>>> take some time on it.
>>>
>>> Le jeu. 30 mai 2019 15:18, Julian Rickards
>>> mailto:julian.ricka...@gmail.com>> a
>>> écrit :
>>>
>>> I use an older laptop with limited screen real estate and some
>>> modules are quite large (height is the issue on my laptop) and
>>> any means of improving this would be appreciated. I don't know
>>> if it would be part of the consideration but sometimes
>>> (recognize that I'm not an expert at dt or photography) I'd
>>> like to collapse the histogram to have more room. In my
>>> experience, the histogram is not always necessary for all
>>> steps in the editing process so the ability to collapse or
>>> open it as needed would help with screen real estate.
>>>
>>> On Thu, May 30, 2019 at 4:51 AM Florian W
>>> mailto:flo.wern...@gmail.com>> wrote:
>>>
>>> Hi Giuseppe,
>>>
>>> I also found myself thinking the same in some cases (for
>>> the histogram, for modules involving curves and nodes, for
>>> the fine tuning of a parametric mask...).
>>>
>>> I added this to my bucket list of features I would like to
>>> implement, I see I'm not the only one who miss it.
>>>
>>> Le mer. 29 mai 2019 18:08, Maurizio Paglia
>>> mailto:mpagl...@gmail.com>> a écrit :
>>>
>>> Ciao Giuseppe,
>>> I have the same difficulty.
>>> Please try to look the new dt GUI design because I
>>> think it could solve this problem.
>>> You can test it compiling dt 2.7 from source.
>>>
>>> Thank you,
>>> Maurizio
>>>
>>> Il giorno mer 29 mag 2019 alle ore 17:30
>>> giuseppe.in...@gmail.com
>>> 
>>> >> > ha scritto:
>>>
>>> Hello,
>>> I think it could be useful to have a feature that
>>> allows you to view a development module in a
>>> separate window with larger dimensions than the
>>> one currently planned. There are in fact some
>>> modules, such as the color zone (there may be
>>> other modules), with which it is not easy to
>>> interact precisely because of the limited size of
>>> the window on which to operate. Perhaps a button
>>> on the module's header is sufficient to display
>>> the module in a larger window.
>>>
>>> What do you think about this?
>>>
>>> Regards,
>>> Giuseppe.
>>>
>>> 
>>> ___
>>> 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] separate RGB in Tone Curve

[Aurélien Pierre]

It's coming in v 2.8 next Christmas.

Le 03/06/2019 à 14:32, Wiktor Nowak a écrit :

> When it's posible to have tone curve separated for L, A, B channels why
> it's not possible with RGB? I'm actually more familliar to think in RGB
> therms so it would be convenient to have an option aside that it's
> possible to achieve same results in LAB.
>
> Aside of that, R, G, B channels in parametric mask would be also
> convenient I think.
> ___
> 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] separate RGB in Tone Curve

[Wiktor Nowak]

When it's posible to have tone curve separated for L, A, B channels why
it's not possible with RGB? I'm actually more familliar to think in RGB
therms so it would be convenient to have an option aside that it's
possible to achieve same results in LAB.

Aside of that, R, G, B channels in parametric mask would be also
convenient I think.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Camera-specific curves generation process

[Florian W]

Hi there,

Does anyone know if the procedure to generate the curves for a specific
camera model is still up to date ?

I took the instructions from here (5 years old though) :
https://www.darktable.org/2013/10/about-basecurves/#comment-30544 and in
the README of $darktable_src/tools/basecurve.

I tried to generate curves for my Canon 750d with shots unfocused, both
over and under exposed at the same time as instructed (see the jpg at
https://ibb.co/C29R6Q9).
And well... the generated curve is not very useful... see
https://ibb.co/rG5yvnm

Does one has to do a lot a sample shots (and maybe more diverse kind of
shots) to get a correct result ?
Or maybe someone has successfuly generated its camera's basecurve and can
provide some guidance with this problem ?

Thanks !

Florian Wernert
Software engineer INSA
Master in Neurosciences trainee
https://www.linkedin.com/in/wernertflorian

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

Re: [darktable-dev] Printing: Using ICC profiles for papers

[Florian W]

Maybe (just a guess) you would have better luck with HP printers as they
provide their own proprietary drivers and printer control for Linux in the
hplip suite.



Le dim. 2 juin 2019 21:44, Pascal Obry  a écrit :

>
> Björn,
>
> > So, does this mean that producing high-quality prints on Linux is
> entirely impossible?
>
> Nothing is impossible. Solutions:
>
> - make you own profile
> - ask a pro to do the profile for you
> - use TurboPrint, high quality and properly supported by dt
>
> > In particular, I have two questions regarding the statement:
> >
> > 1. I am not sure wether I understand the explanation correctly. How
> > exactly do the ICC profiles provided by paper manufacturers depend on
> > the printer driver? Does the printer driver affect the printer's
> > color rendition, so that the printer's color space when used with
> > cups differs from the color space when used with the proprietary
> > driver on windows?
>
> No, each driver use it's own algorithm to transform a RGB picture to a
> print using 6, 8, 12 different color on your printer. The driver is a
> software and the transformation done here is different on all OS.
> That's why you have today ICC provided for MacOS and Windows.
>
> > 2. Is there any way to get properly color-managed prints with fine-
> > art papers on Linux (with DT)? Would I have buy a
> > colorimeter/spectrometer and profile it myself?
>
> The easiest solution is TurboPrint. I'm using it and I have implemented
> the support in dt for a good reason :)
>
> --
>   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