So what you're saying is that there are technical reasons, and they
are about how dt, or at least those modules are constructed.

In message <CALXjwtP5yX-24HZM=33qz9hxmlhgohmoxx44rnyitqebik5...@mail.gmail.com> 
on Thu, 1 Aug 2013 10:56:22 +0200, jeremy rosen <[email protected]> 
said:

jeremy.rosen> to put it simply, you cannot not have some sort of exposure/white 
balance on parts of images.
jeremy.rosen> 
jeremy.rosen> you could have a gradiant/mask between two values, but you can 
not have no EV compensation or WB
jeremy.rosen> at all. 
jeremy.rosen> 
jeremy.rosen> arguably it would be interesting to have a way to do that, in 
particular for WB where different
jeremy.rosen> zones of an image can have different color-casts, but that's not 
a simple case of enabling blendif
jeremy.rosen> /masks on the module. it's a redesign...
jeremy.rosen> 
jeremy.rosen> On Thu, Aug 1, 2013 at 10:30 AM, Gonçalo Marrafa 
<[email protected]> wrote:
jeremy.rosen> 
jeremy.rosen> > 
jeremy.rosen> Hi. 
jeremy.rosen> 
jeremy.rosen> > 
jeremy.rosen> I posted this question (twice) on DT's Google+ comunity 
(http://goo.gl/CBvw7y) but got no answer, so i'm trying this mailing list :)
jeremy.rosen> 
jeremy.rosen> > 
jeremy.rosen> > 
jeremy.rosen> > 
jeremy.rosen> > 
jeremy.rosen> 
jeremy.rosen> > 
jeremy.rosen> Why aren't masks/conditional blending available in white balance 
and exposure modules? Is it a technical reason or an implementation decision? 
It would be nice to be able to adjust white balance and/or exposure only on 
parts of the image, like in LR, for example.
jeremy.rosen> > 
jeremy.rosen> > 
jeremy.rosen> > 
jeremy.rosen> > 
jeremy.rosen> 
jeremy.rosen> > 
jeremy.rosen> Thanks in advance.
jeremy.rosen> 
jeremy.rosen> > 
jeremy.rosen> 
jeremy.rosen> > 
jeremy.rosen> Gonçalo Marrafa
jeremy.rosen> > 
jeremy.rosen> 
jeremy.rosen> > 
jeremy.rosen> 
jeremy.rosen> > 
jeremy.rosen> > 
------------------------------------------------------------------------------
jeremy.rosen> > Get your SQL database under version control now!
jeremy.rosen> > Version control is standard for application code, but databases 
havent
jeremy.rosen> > caught up. So what steps can you take to put your SQL databases 
under
jeremy.rosen> > version control? Why should you start doing it? Read more to 
find out.
jeremy.rosen> > 
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
jeremy.rosen> > _______________________________________________
jeremy.rosen> > 
jeremy.rosen> > 
jeremy.rosen> > Darktable-users mailing list
jeremy.rosen> > [email protected]
jeremy.rosen> > https://lists.sourceforge.net/lists/listinfo/darktable-users
jeremy.rosen> 

------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users

Reply via email to