hey,
On Thu, Jul 18, 2013 at 9:52 AM, Marie-Noëlle Augendre <[email protected]
> wrote:
>
>
> 2013/7/18 Torsten Bronger <[email protected]>
>
>> Hallöchen!
>>
>> Marie-Noëlle Augendre writes:
>>
>> > I'm not interested in that.
>> >
>> > I work on an artistic level, and don't want anybody, Canon
>> > engineers or whoever, to dictate the rendering of my pictures.
>>
>> If you don't like the basecurve, fair enough, turn it off.
>
>
> That's what I currently do. But I have to do it for each picture, because
> even if I copy/paste the development of another picture (without a base
> curve), the base curve is applied to the new picture in addition to all the
> other treatments.
> If I could deactivate from the beginning for all the pictures, that would
> be much simpler and quicker.
>
we used to have `user defined defaults' which would just set the initial
parameters, and even allow you to switch the module on or off. that was a
problem when sharing pictures + xmp, because different darktable
installations came with different defaults and thus changed the appearance.
so today you'll need to use auto-applying presets, because these end up in
the history stack and thus in the xmp. you can still decide whether you
want the module switched on or off in that auto-preset, so you could stack
up a disabled setting and would then be able to switch it on with a single
click.
in the case you describe i would do another thing though, and create a
preset for vignetting and define a key accel for it in the preferences
dialog. this way it's only one key stroke, not even mouse click.
hope that helps,
jo
>
>
>
>> But
>> David spoke about something different:
>>
>> The colour matrices -- whether "standard" or "enhanced" -- are
>> supposed to yield correct colours. They are not a matter of taste
>> of some engineers. If they don't work, this must be investigated.
>>
>
> I don't know what correct colours mean, as the choice of the white balance
> change them completely, saturation and contrast have to be defined, etc.
>
>
>>
>> And: I would also like to have investigated the strongly saturating
>> effect of the small convex part of the basecurve. Have you tried to
>> remove the lowest control point? Did it remove the lobster effect?
>>
>
> I have not investigated the base curve as I find it counter productive,
> and I'm afraid I have currently no spare time trying to fix the bad
> consequences of a module I don't want to use in the first place. Sorry.
>
> Marie-Noëlle
>
>
>
>
> --
> <http://fr.ulule.com/aigoual-aubrac/>
>
> *De l'AIgoual à l'Aubrac, un voyage photographique en Cévennes et Lozère*
> Un livre à offrir ou à s'offrir, en souscription jusqu'au 31 août 2013.
> Cliquer sur l'image ci-dessus ou ce lien pour en savoir
> plus<http://fr.ulule.com/aigoual-aubrac/>
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Darktable-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-users
>
>
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
