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 <malnour...@gmail.com>: > > On Tue, Feb 7, 2017 at 10:20 AM, Thomas Werzmirzowsky <werzi2...@gmx.de> > 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
