Re: [Darktable-users] deflicker

2014-03-08 Thread Roman Lebedev
Once again, it can be used on absolutely anything - single images, image sets, complete timelapses. To compute exposure compensation of one image it does not use / nor need to have anything else besides the current image. In the essence it's just better auto-exposure algoritm just like "auto" check

Re: [Darktable-users] deflicker

2014-03-08 Thread Patrick Shanahan
* bartokk [03-08-14 14:41]: > Il 08/mar/2014 19:29 "Patrick Shanahan" > > > Is it an "averaging" of exposure within a set/selection/group? > > Yes. So it should not be used as a singular adjustment but applied to a selected set or group and should only be presented when such exists? Not presen

Re: [Darktable-users] deflicker

2014-03-08 Thread Roman Lebedev
>Deflicker ON appears to be default? No, it is disabled by default. There was a bug in legacy preset update infrastructure, which resulted in Deflicker enabled by default. Fixed in commit 243dfeaa148051db826e71b3c38a4eb5a24ac947 >Does Deflicker need to be applied to an entire set/selection/group?

Re: [Darktable-users] deflicker

2014-03-08 Thread bartokk
Il 08/mar/2014 19:29 "Patrick Shanahan" > Is it an "averaging" of exposure within a set/selection/group? > > -- > (paka)Patrick Shanahan Yes. Mauro from Android Gpg public key: 0x73E5AEA3 -- Subversion Kills Productivit

[Darktable-users] deflicker

2014-03-08 Thread Patrick Shanahan
Please explain deflicker in a little more depth. Deflicker ON appears to be default? Does deflicker need to be applied to an entire set/selection/group? Does it only affect output on exporting and only the selection being exported? Is it an "averaging" of exposure within a set/selection/group?

Re: [Darktable-users] *deflicker* automagically selected ???

2014-03-06 Thread Patrick Shanahan
* Roman Lebedev [03-06-14 12:54]: > Should be fixed by > https://github.com/darktable-org/darktable/commit/243dfeaa148051db826e71b3c38a4eb5a24ac947 > > > On Thu, Mar 6, 2014 at 7:21 PM, Patrick Shanahan wrote: > > > openSUSE Tumbleweed > > darktable-1.5.505_g6b0b8f9 > > > > This mornings updat

Re: [Darktable-users] *deflicker* automagically selected ???

2014-03-06 Thread Roman Lebedev
Should be fixed by https://github.com/darktable-org/darktable/commit/243dfeaa148051db826e71b3c38a4eb5a24ac947 On Thu, Mar 6, 2014 at 7:21 PM, Patrick Shanahan wrote: > openSUSE Tumbleweed > darktable-1.5.505_g6b0b8f9 > > This mornings update to darktable-1.5.505_g6b0b8f9 apparently sets > "defl

[Darktable-users] *deflicker* automagically selected ???

2014-03-06 Thread Patrick Shanahan
openSUSE Tumbleweed darktable-1.5.505_g6b0b8f9 This mornings update to darktable-1.5.505_g6b0b8f9 apparently sets "deflicker" to on. Working on a group of photos previously imported with existing xmp sidecars, deflicker is set to on and exposure is set to +9.97ev. Thumbnails still appear *normal

Re: [Darktable-users] deflicker

2014-03-05 Thread Fraser McCrossan
On 14-03-05 10:08 AM, Pascal Obry wrote: > I have refrained from translating this word in French. Possible > translations would have been "annulation du scintillement" ou > "atténuation du scintillement". Those terms are lot too long for the > IOP. If someone has a better proposal let me know! > We

[Darktable-users] deflicker

2014-03-05 Thread Pascal Obry
I have refrained from translating this word in French. Possible translations would have been "annulation du scintillement" ou "atténuation du scintillement". Those terms are lot too long for the IOP. If someone has a better proposal let me know! Pascal. -- Pascal Obry / Magny Les Hameaux (78